[Bug 823878] Re: smbd failed to start after system restart

Thu Oct 6 14:29:30 UTC 2011

Vasya,

If you manually change /etc/samba/smb.conf to have smbd bind to a
specific interface, you also need to edit /etc/init/smbd.conf to make
sure the smbd is started only after that particular interface is up, in
the style "start on (local-filesystems and net-device-up IFACE=eth0)"
(as described in
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/771305/comments/17).

Ideally upstart would pick up on this automatically, but we also have to
cater for environments where a network might not come up until much
later if at all, and local access to smbd over loopback should still be
available in that case (see
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/771305/comments/10).

It is unfortunate that a sysadmin would have to know to do this when
adding interfaces/bind interfaces only to smbd, so I'm leaving this bug
open in case someone can come up with a way of solving this problem
without issues in both cases. I'm setting Importance to Low as this
workaround is available and the problem only occurs when the sysadmin
changes smb.conf by hand.

** Summary changed:

- smbd failed to start after system restart
+ "bind interfaces only" requires a manual change to /etc/init/smbd.conf

** Changed in: samba (Ubuntu)
   Importance: Medium => Low

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/823878

Title:
  "bind interfaces only" requires a manual change to /etc/init/smbd.conf

Status in “samba” package in Ubuntu:
  New

Bug description:
  Sometimes smbd daemon failes to start after system restart. As a
  result, fileserver is not accessible after power failure and requires
  someone to fix that manually, which sometimes is very hard to do.
  Today this happened again and here's what was in logs:

  ===
  Aug 10 14:40:32 shadow-server smbd[713]: [2011/08/10 14:40:32,  0] lib/interface.c:550(load_interfaces)
  Aug 10 14:40:32 shadow-server smbd[713]:   WARNING: no network interfaces found
  Aug 10 14:40:32 shadow-server smbd[713]: [2011/08/10 14:40:32,  0] smbd/server.c:1115(main)
  Aug 10 14:40:32 shadow-server smbd[713]:   standard input is not a socket, assuming -D option
  Aug 10 14:40:32 shadow-server smbd[713]: [2011/08/10 14:40:32,  0] smbd/server.c:616(open_sockets_smbd)
  Aug 10 14:40:32 shadow-server smbd[713]:   open_sockets_smbd: No sockets available to bind to.
  Aug 10 14:40:32 shadow-server smbd[713]: [2011/08/10 14:40:32,  0] smbd/server.c:837(exit_server_common)
  Aug 10 14:40:32 shadow-server smbd[713]:   ===============================================================
  Aug 10 14:40:32 shadow-server smbd[713]: [2011/08/10 14:40:32,  0] smbd/server.c:839(exit_server_common)
  Aug 10 14:40:32 shadow-server smbd[713]:   Abnormal server exit: open_sockets_smbd() failed
  Aug 10 14:40:32 shadow-server smbd[713]: [2011/08/10 14:40:32,  0] smbd/server.c:840(exit_server_common)
  Aug 10 14:40:32 shadow-server smbd[713]:   ===============================================================
  Aug 10 14:40:32 shadow-server smbd[713]: [2011/08/10 14:40:32,  0] lib/util.c:1584(log_stack_trace)
  Aug 10 14:40:32 shadow-server smbd[713]:   BACKTRACE: 6 stack frames:
  Aug 10 14:40:32 shadow-server smbd[713]:    #0 smbd(log_stack_trace+0x1a) [0x7f898f57295a]
  Aug 10 14:40:32 shadow-server smbd[713]:    #1 smbd(+0x5a9f90) [0x7f898f801f90]
  Aug 10 14:40:32 shadow-server smbd[713]:    #2 smbd(+0x5aa161) [0x7f898f802161]
  Aug 10 14:40:32 shadow-server smbd[713]:    #3 smbd(main+0x90d) [0x7f898f802ebd]
  Aug 10 14:40:32 shadow-server smbd[713]:    #4 /lib/libc.so.6(__libc_start_main+0xfd) [0x7f898bcffc4d]
  Aug 10 14:40:32 shadow-server smbd[713]:    #5 smbd(+0xc0a49) [0x7f898f318a49]
  Aug 10 14:40:32 shadow-server smbd[713]: [2011/08/10 14:40:32,  0] lib/fault.c:326(dump_core)
  Aug 10 14:40:32 shadow-server smbd[713]:   dumping core in /var/log/samba/cores/smbd
  Aug 10 14:40:32 shadow-server smbd[713]:
  Aug 10 14:40:33 shadow-server init: smbd main process (713) killed by ABRT signal
  Aug 10 14:40:33 shadow-server init: smbd main process ended, respawning

  *** repeated the same several times ***

  Aug 10 14:40:33 shadow-server init: smbd main process (902) killed by ABRT signal
  Aug 10 14:40:33 shadow-server init: smbd respawning too fast, stopped
  ===

  It's a server, network is configured via DHCP, there is no Network
  Manager installed, and according to log, it was configured just a
  second after smbd failed to start:

  Aug 10 14:40:34 shadow-server dhclient: bound to 192.168.0.156 --
  renewal in 40397 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: samba 2:3.4.7~dfsg-1ubuntu3.7
  ProcVersionSignature: Ubuntu 2.6.32-33.72-server 2.6.32.41+drm33.18
  Uname: Linux 2.6.32-33-server x86_64
  Architecture: amd64
  Date: Wed Aug 10 15:44:21 2011
  InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SambaServerRegression: No
  SourcePackage: samba

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/823878/+subscriptions