I've been using Samba4 on Debian/Jessie since it became "stable".
After
the last upgrade however, I got a massive failure.
The first symptom I noticed was that I couldn't grab updates from the
Debian servers. However when clients tried to log in, the real problem
revealed itself. They could only log on using a temporary profile and
couldn't connect to any of the shares or printers.
When I test my implementation of Samba, it fails the basic test:
# smbclient -L localhost -U%
Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED)
The globals section of smb.conf is:
[global]
workgroup = DENTALOFFICE
realm = DENTALOFFICE.ROSSLAND.DENTAL
netbios name = MOLAR
server role = active directory domain controller
dns forwarder = 8.8.8.8
idmap_ldb:use rfc2307 = yes
allow dns updates = nonsecure
which explains why I can't get to the Debian servers. The hand off to
Google's DNS servers never happens.
ps aux | grep nmbd, smbd or samba all show that samba isn't running.
The logs for starting samba show:
[2016/07/04 11:29:48.240042, 0]
../source4/smbd/server.c:370(binary_smbd_main)
samba version 4.2.10-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2014
[2016/07/04 11:29:48.421540, 0]
../source4/smbd/server.c:488(binary_smbd_main)
samba: using 'standard' process model
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
[2016/07/04 11:29:48.446253, 0]
../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'samba' finished starting up and ready to serve
connections
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call
setproctitle_init() or link against libbsd-ctor.
[2016/07/04 11:29:48.460701, 0]
../lib/util/util_runcmd.c:324(samba_runcmd_io_handler)
/usr/sbin/winbindd: Failed to exec child - No such file or directory
[2016/07/04 11:29:48.462580, 0]
../source4/winbind/winbindd.c:49(winbindd_done)
winbindd daemon exited normally
task_server_terminate: [winbindd child process exited]
[2016/07/04 11:29:48.464159, 0]
../source4/smbd/server.c:211(samba_terminate)
samba_terminate: winbindd child process exited
Although the message about the daemon being ready seems to indicate that
samba is running, as I said, ps aux shows that it isn't.
Any ideas how I can get Samba back up? Uninstalling and reinstalling it
didn't work.
On 04/07/16 16:36, Gary Dale wrote:> I've been using Samba4 on Debian/Jessie since it became "stable". > After the last upgrade however, I got a massive failure. > > The first symptom I noticed was that I couldn't grab updates from the > Debian servers. However when clients tried to log in, the real problem > revealed itself. They could only log on using a temporary profile and > couldn't connect to any of the shares or printers. > > When I test my implementation of Samba, it fails the basic test: > > # smbclient -L localhost -U% > Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED) > > The globals section of smb.conf is: > > [global] > workgroup = DENTALOFFICE > realm = DENTALOFFICE.ROSSLAND.DENTAL > netbios name = MOLAR > server role = active directory domain controller > dns forwarder = 8.8.8.8 > idmap_ldb:use rfc2307 = yes > allow dns updates = nonsecure > > which explains why I can't get to the Debian servers. The hand off to > Google's DNS servers never happens. > > ps aux | grep nmbd, smbd or samba all show that samba isn't running. > The logs for starting samba show: > > [2016/07/04 11:29:48.240042, 0] > ../source4/smbd/server.c:370(binary_smbd_main) > samba version 4.2.10-Debian started. > Copyright Andrew Tridgell and the Samba Team 1992-2014 > [2016/07/04 11:29:48.421540, 0] > ../source4/smbd/server.c:488(binary_smbd_main) > samba: using 'standard' process model > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > [2016/07/04 11:29:48.446253, 0] > ../lib/util/become_daemon.c:124(daemon_ready) > STATUS=daemon 'samba' finished starting up and ready to serve > connections > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > [2016/07/04 11:29:48.460701, 0] > ../lib/util/util_runcmd.c:324(samba_runcmd_io_handler) > /usr/sbin/winbindd: Failed to exec child - No such file or directory > [2016/07/04 11:29:48.462580, 0] > ../source4/winbind/winbindd.c:49(winbindd_done) > winbindd daemon exited normally > task_server_terminate: [winbindd child process exited] > [2016/07/04 11:29:48.464159, 0] > ../source4/smbd/server.c:211(samba_terminate) > samba_terminate: winbindd child process exited > > > Although the message about the daemon being ready seems to indicate > that samba is running, as I said, ps aux shows that it isn't. > > Any ideas how I can get Samba back up? Uninstalling and reinstalling > it didn't work. > >What version did you upgrade from and what is the version now ? You could try installing 'winbind', this seems to be your problem '/usr/sbin/winbindd: Failed to exec child - No such file or directory' Earlier versions of Samba4 running as a DC used 'winbind' built into the 'samba' binary, later versions use the separate 'winbindd' binary instead. Rowland
On 04/07/16 11:36 AM, Gary Dale wrote:> I've been using Samba4 on Debian/Jessie since it became "stable". > After the last upgrade however, I got a massive failure. > > The first symptom I noticed was that I couldn't grab updates from the > Debian servers. However when clients tried to log in, the real problem > revealed itself. They could only log on using a temporary profile and > couldn't connect to any of the shares or printers. > > When I test my implementation of Samba, it fails the basic test: > > # smbclient -L localhost -U% > Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED) > > The globals section of smb.conf is: > > [global] > workgroup = DENTALOFFICE > realm = DENTALOFFICE.ROSSLAND.DENTAL > netbios name = MOLAR > server role = active directory domain controller > dns forwarder = 8.8.8.8 > idmap_ldb:use rfc2307 = yes > allow dns updates = nonsecure > > which explains why I can't get to the Debian servers. The hand off to > Google's DNS servers never happens. > > ps aux | grep nmbd, smbd or samba all show that samba isn't running. > The logs for starting samba show: > > [2016/07/04 11:29:48.240042, 0] > ../source4/smbd/server.c:370(binary_smbd_main) > samba version 4.2.10-Debian started. > Copyright Andrew Tridgell and the Samba Team 1992-2014 > [2016/07/04 11:29:48.421540, 0] > ../source4/smbd/server.c:488(binary_smbd_main) > samba: using 'standard' process model > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > [2016/07/04 11:29:48.446253, 0] > ../lib/util/become_daemon.c:124(daemon_ready) > STATUS=daemon 'samba' finished starting up and ready to serve > connections > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > samba: setproctitle not initialized, please either call > setproctitle_init() or link against libbsd-ctor. > [2016/07/04 11:29:48.460701, 0] > ../lib/util/util_runcmd.c:324(samba_runcmd_io_handler) > /usr/sbin/winbindd: Failed to exec child - No such file or directory > [2016/07/04 11:29:48.462580, 0] > ../source4/winbind/winbindd.c:49(winbindd_done) > winbindd daemon exited normally > task_server_terminate: [winbindd child process exited] > [2016/07/04 11:29:48.464159, 0] > ../source4/smbd/server.c:211(samba_terminate) > samba_terminate: winbindd child process exited > > > Although the message about the daemon being ready seems to indicate > that samba is running, as I said, ps aux shows that it isn't. > > Any ideas how I can get Samba back up? Uninstalling and reinstalling > it didn't work. > >Turns out that winbind was a different version than libwinb... Somehow it got dropped from the upgrade. Installing winbind brought in the current version then restarting samba got things going again.
On 04/07/16 12:30 PM, Rowland penny wrote:> On 04/07/16 16:36, Gary Dale wrote: >> I've been using Samba4 on Debian/Jessie since it became "stable". >> After the last upgrade however, I got a massive failure. >> >> The first symptom I noticed was that I couldn't grab updates from the >> Debian servers. However when clients tried to log in, the real >> problem revealed itself. They could only log on using a temporary >> profile and couldn't connect to any of the shares or printers. >> >> When I test my implementation of Samba, it fails the basic test: >> >> # smbclient -L localhost -U% >> Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED) >> >> The globals section of smb.conf is: >> >> [global] >> workgroup = DENTALOFFICE >> realm = DENTALOFFICE.ROSSLAND.DENTAL >> netbios name = MOLAR >> server role = active directory domain controller >> dns forwarder = 8.8.8.8 >> idmap_ldb:use rfc2307 = yes >> allow dns updates = nonsecure >> >> which explains why I can't get to the Debian servers. The hand off to >> Google's DNS servers never happens. >> >> ps aux | grep nmbd, smbd or samba all show that samba isn't running. >> The logs for starting samba show: >> >> [2016/07/04 11:29:48.240042, 0] >> ../source4/smbd/server.c:370(binary_smbd_main) >> samba version 4.2.10-Debian started. >> Copyright Andrew Tridgell and the Samba Team 1992-2014 >> [2016/07/04 11:29:48.421540, 0] >> ../source4/smbd/server.c:488(binary_smbd_main) >> samba: using 'standard' process model >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> [2016/07/04 11:29:48.446253, 0] >> ../lib/util/become_daemon.c:124(daemon_ready) >> STATUS=daemon 'samba' finished starting up and ready to serve >> connections >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> samba: setproctitle not initialized, please either call >> setproctitle_init() or link against libbsd-ctor. >> [2016/07/04 11:29:48.460701, 0] >> ../lib/util/util_runcmd.c:324(samba_runcmd_io_handler) >> /usr/sbin/winbindd: Failed to exec child - No such file or directory >> [2016/07/04 11:29:48.462580, 0] >> ../source4/winbind/winbindd.c:49(winbindd_done) >> winbindd daemon exited normally >> task_server_terminate: [winbindd child process exited] >> [2016/07/04 11:29:48.464159, 0] >> ../source4/smbd/server.c:211(samba_terminate) >> samba_terminate: winbindd child process exited >> >> >> Although the message about the daemon being ready seems to indicate >> that samba is running, as I said, ps aux shows that it isn't. >> >> Any ideas how I can get Samba back up? Uninstalling and reinstalling >> it didn't work. >> >> > > What version did you upgrade from and what is the version now ? > > You could try installing 'winbind', this seems to be your problem > '/usr/sbin/winbindd: Failed to exec child - No such file or directory' > Earlier versions of Samba4 running as a DC used 'winbind' built into > the 'samba' binary, later versions use the separate 'winbindd' binary > instead. > > Rowland > >It turned out that libwbclient was a later version than winbind. Installing winbind fixed the problem. Somehow winbind got left out of the upgrade despite there being a more recent version on Debian's servers.