That is correct. Most of the time this isn't an issue because the new ldb modules, linking to the new symbol versions, overwrite the old files on 'make install'. However we chose to remove some obsolete ldb modules in the 4.12 cycle and so the old modules remain, triggering these warnings. We notice the old modules because we try to load all the modules during startup of ldb to see if they wish to provide hooks for the command line handling in the ldb* tools. (But this happens for all ldb consumers, including samba-tool). Andrew Bartlett On Wed, 2020-04-15 at 18:18 +0100, Alex MacCuish via samba wrote:> This happened to me as well. I use the default /usr/local/samba. I > moved > that to samba-old, make install'ed, then copied etc, private and > var/locks/sysvol and ran the dns upgrade script. The problem is some > libraries being moved, renamed etc. > > On 15/04/2020 18:03, David Coelho via samba wrote: > > Hi everyone, > > > > I have just updated samba from 4.11.6 to 4.12.0, compiled by the > > sources. > > Everything was fine and AD server is ok , but when I call samba- > > tool this > > error always appear: > > > > ldb: unable to dlopen /usr/lib64/samba/ldb/local_password.so : > > /usr/lib64/samba/libsamdb-common-samba4.so: version `SAMBA_4.11.6' > > not > > found (required by /usr/lib64/samba/ldb/local_password.so) > > ldb: unable to dlopen /usr/lib64/samba/ldb/simple_dn.so : > > /usr/lib64/samba/libdsdb-module-samba4.so: version `SAMBA_4.11.6' > > not found > > (required by /usr/lib64/samba/ldb/simple_dn.so) > > ldb: unable to dlopen /usr/lib64/samba/ldb/simple_ldap_map.so : > > /usr/lib64/samba/libsamdb-common-samba4.so: version `SAMBA_4.11.6' > > not > > found (required by /usr/lib64/samba/ldb/simple_ldap_map.so) > > > > Can someone help me ? > > > > > > > > *David Coelho dos Santos* > >-- Andrew Bartlett https://samba.org/~abartlet/ Authentication Developer, Samba Team https://samba.org Samba Developer, Catalyst IT https://catalyst.net.nz/services/samba
Thanks all for reply. I moved my old samba folder and did again: configure (with options) - make - make install. It was resolved ! *David Coelho dos Santos* Em qua., 15 de abr. de 2020 ?s 17:32, Andrew Bartlett via samba < samba at lists.samba.org> escreveu:> That is correct. Most of the time this isn't an issue because the new > ldb modules, linking to the new symbol versions, overwrite the old > files on 'make install'. > > However we chose to remove some obsolete ldb modules in the 4.12 cycle > and so the old modules remain, triggering these warnings. > > We notice the old modules because we try to load all the modules during > startup of ldb to see if they wish to provide hooks for the command > line handling in the ldb* tools. (But this happens for all ldb > consumers, including samba-tool). > > Andrew Bartlett > > On Wed, 2020-04-15 at 18:18 +0100, Alex MacCuish via samba wrote: > > This happened to me as well. I use the default /usr/local/samba. I > > moved > > that to samba-old, make install'ed, then copied etc, private and > > var/locks/sysvol and ran the dns upgrade script. The problem is some > > libraries being moved, renamed etc. > > > > On 15/04/2020 18:03, David Coelho via samba wrote: > > > Hi everyone, > > > > > > I have just updated samba from 4.11.6 to 4.12.0, compiled by the > > > sources. > > > Everything was fine and AD server is ok , but when I call samba- > > > tool this > > > error always appear: > > > > > > ldb: unable to dlopen /usr/lib64/samba/ldb/local_password.so : > > > /usr/lib64/samba/libsamdb-common-samba4.so: version `SAMBA_4.11.6' > > > not > > > found (required by /usr/lib64/samba/ldb/local_password.so) > > > ldb: unable to dlopen /usr/lib64/samba/ldb/simple_dn.so : > > > /usr/lib64/samba/libdsdb-module-samba4.so: version `SAMBA_4.11.6' > > > not found > > > (required by /usr/lib64/samba/ldb/simple_dn.so) > > > ldb: unable to dlopen /usr/lib64/samba/ldb/simple_ldap_map.so : > > > /usr/lib64/samba/libsamdb-common-samba4.so: version `SAMBA_4.11.6' > > > not > > > found (required by /usr/lib64/samba/ldb/simple_ldap_map.so) > > > > > > Can someone help me ? > > > > > > > > > > > > *David Coelho dos Santos* > > > > > -- > Andrew Bartlett https://samba.org/~abartlet/ > Authentication Developer, Samba Team https://samba.org > Samba Developer, Catalyst IT > https://catalyst.net.nz/services/samba > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >
On 15/04/2020 21:29, Andrew Bartlett via samba wrote:> That is correct. Most of the time this isn't an issue because the new > ldb modules, linking to the new symbol versions, overwrite the old > files on 'make install'. > > However we chose to remove some obsolete ldb modules in the 4.12 cycle > and so the old modules remain, triggering these warnings. > > We notice the old modules because we try to load all the modules during > startup of ldb to see if they wish to provide hooks for the command > line handling in the ldb* tools. (But this happens for all ldb > consumers, including samba-tool). > > Andrew Bartlett >Andrew, if we are going to do things like this, don't you think it would be a good idea to document it in the release notes ? Rowland
On Thu, 2020-04-16 at 07:34 +0100, Rowland penny wrote:> On 15/04/2020 21:29, Andrew Bartlett via samba wrote: > > That is correct. Most of the time this isn't an issue because the > > new > > ldb modules, linking to the new symbol versions, overwrite the old > > files on 'make install'. > > > > However we chose to remove some obsolete ldb modules in the 4.12 > > cycle > > and so the old modules remain, triggering these warnings. > > > > We notice the old modules because we try to load all the modules > > during > > startup of ldb to see if they wish to provide hooks for the command > > line handling in the ldb* tools. (But this happens for all ldb > > consumers, including samba-tool). > > > > Andrew Bartlett > > > > Andrew, if we are going to do things like this, don't you think it > would > be a good idea to document it in the release notes ?We could. This isn't the first time we have removed modules, and we haven't ever promised that you can install Samba on top of an existing installation, but you would be correct to say it has often worked. Andrew Bartlett -- Andrew Bartlett https://samba.org/~abartlet/ Authentication Developer, Samba Team https://samba.org Samba Developer, Catalyst IT https://catalyst.net.nz/services/samba