Public bug reported:
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
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lucid
--
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:
smbd failed to start after system restart
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/823878/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
