I went through the upgrade process describe here
https://wiki.samba.org/index.php/Updating_Samba
after grabbing the samba 4.1.13 source I configured, make and make
installed the new source over the top of my existing 4.1.9 code.
I expected that the install would copy over the top of existing python and
binaries but this seems to not be the case. My first clue was running
bin/samba-tool dbcheck
This yielded the exception
bin/samba-tool dbcheck
Traceback (most recent call last):
File "bin/samba-tool", line 33, in <module>
from samba.netcmd.main import cmd_sambatool
File
"/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/main.py",
line 24, in <module>
from samba.netcmd.delegation import cmd_delegation
File
"/usr/local/samba/lib/python2.7/site-packages/samba/netcmd/delegation.py",
line 23, in <module>
from samba import provision
File
"/usr/local/samba/lib/python2.7/site-packages/samba/provision/__init__.py",
line 46, in <module>
from samba.samba3 import smbd, passdb
File
"/usr/local/samba/lib/python2.7/site-packages/samba/samba3/__init__.py",
line 28, in <module>
import ntdb
ImportError: /usr/local/samba/lib/private/libccan.so: version `SAMBA_4.1.9'
not found (required by /usr/local/samba/lib/private/libntdb.so.0)
So now we know the libntdb.so.0 was not replaced by the make install.
Running sbin/samba
starts the samba daemon but it doesn't seem to start it completely, nor
does it crash and die. The last thing shown in var/log.samba is this:
tail var/log.samba
[2014/12/24 00:26:45.104709, 3]
../source4/auth/ntlm/auth.c:673(auth_register)
AUTH backend 'unix' registered
[2014/12/24 00:26:45.104860, 3]
../source4/param/share.c:124(share_register)
SHARE backend [classic] registered.
[2014/12/24 00:26:45.104939, 3]
../source4/param/share.c:124(share_register)
SHARE backend [ldb] registered.
So clearly, something is messed up.
Is there some clean command in the make install step that I can use ? Or is
there some listing of files that I should clean before make install ?
--
David Bear
mobile: (602) 903-6476
Hello David, Am 24.12.2014 um 08:52 schrieb David Bear:> I went through the upgrade process describe here > https://wiki.samba.org/index.php/Updating_Samba > > after grabbing the samba 4.1.13 source I configured, make and make > installed the new source over the top of my existing 4.1.9 code. > > I expected that the install would copy over the top of existing python and > binaries but this seems to not be the case. My first clue was runningDid you used exactly the same ./configure options, like in the 4.1.9 build? Then Samba and its libraries will be installed into the same directories, like it was before and replaces everything. It looks like, some parameters were different and you're still trying to start the old binary. Can you start # /usr/local/samba/bin/samba directly (bypass your $PATH variable). Or where ever you have it installed.> Is there some clean command in the make install step that I can use ? Or is > there some listing of files that I should clean before make install ?There's a "make uninstall". I never used it. After a backup, you can try it and then install the old version over or reinstall 4.1.13 with the same ./configure options, like 4.1.9 had. Regards, Marc
On Wed, Dec 24, 2014 at 2:23 AM, Marc Muehlfeld <mmuehlfeld at samba.org> wrote:> Hello David, > > Am 24.12.2014 um 08:52 schrieb David Bear: > > I went through the upgrade process describe here > > https://wiki.samba.org/index.php/Updating_Samba > > Did you used exactly the same ./configure options, like in the 4.1.9 > build? Then Samba and its libraries will be installed into the same > directories, like it was before and replaces everything. >Yes. I kept the configure simple (configure --prefix=/usr/local/samba)> > It looks like, some parameters were different and you're still trying to > start the old binary. >I checked my build notes -- they are the same.> > Can you start > # /usr/local/samba/bin/samba > directly (bypass your $PATH variable). Or where ever you have it installed. > > Yes, samba did eventually fully start. I don't know how long it took tofully launch all daemons, but I checked today and things were running., Here is the a weirld message. running bin/smbstatus from my samba install I get the following: lp_load_ex: refreshing parameters Initialising global parameters params.c:pm_process() - Processing configuration file "/usr/local/samba/etc/smb.conf" Processing section "[global]" Samba version 4.1.14 PID Username Group Machine ------------------------------------------------------------------- Service pid machine Connected at ------------------------------------------------------- Registered MSG_REQ_POOL_USAGE Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED No locked files But, doing bin/smbclient -L localhost I get bin/smbclient -L localhost Enter root's password: Anonymous login successful Domain=[AD] OS=[Unix] Server=[Samba 4.1.14] Sharename Type Comment --------- ---- ------- netlogon Disk sysvol Disk IPC$ IPC IPC Service (Samba 4.1.14) Anonymous login successful Domain=[AD] OS=[Unix] Server=[Samba 4.1.14] Server Comment --------- ------- A0373 A0373 HAM1 Samba 4.1.9 Workgroup Master --------- ------- AD HAM1 BEARFAM.ORG TYNDALE HERITAGE A0206 WORKGROUP PARADON1 NOTE: the machine I am doing this on is HAM1. So why would HAM1 report itself in smbstatus as 4.1.14 -- but on the comment line from smbclient report 4.1.9 ? I have looked in the smb.conf file and I do NOT have that anywhere. Finally, I noticed that there are LOTS of left over libraries in /usr/local/samba/lib -- from the time when I compiled samba back in June. But there are also NEW libraries in lib from when I compiled on Dec 24. So It appears the make install step does NOT clobber everything it should . - -- David Bear mobile: (602) 903-6476