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

[Robie Basak]

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
Server Team, 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

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