"bind interfaces only" requires a manual change to /etc/init/smbd.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba (Ubuntu) |
Triaged
|
Low
|
Unassigned |
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.
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.
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.
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.
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.
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.
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.
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_
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.
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.
Aug 10 14:40:32 shadow-server smbd[713]: dumping core in /var/log/
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~
ProcVersionSign
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
SambaServerRegr
SourcePackage: samba
Changed in samba (Ubuntu): | |
importance: | Undecided → Medium |
Changed in samba (Ubuntu): | |
status: | Confirmed → Triaged |
Is this the same as bug #771305, manifesting differently in lucid?