[Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)

Marcin Kucharczyk marcinkk at enter.net.pl
Sat Dec 1 18:46:35 GMT 2007


Sunday, November 25, 2007, 2:48:23 PM, Volker Lendecke wrote:

VL> This particular bug report is highly unlikely to be a Samba
VL> problem. Also, I have a hard time to believe that you have
VL> to really deinstall Samba after a system crash. It *is*
VL> definitely possible to restart Samba from whatever state the
VL> system is in, possibly by removing tdb files. Removing and
VL> recompiling the daemons is definitely unnecessary. You might
VL> want to see what this removing/reinstalling really does.

Ok, I made few more test. Looks like reinstall is not neccessary. I
CAN'T delete /var/db/samba/ directory, because samba doesen't want to
start. But I CAN delete contents of the directory and start samba
again. Not the best conclusions after first samba 3.0.26a crash and
problems with the system :(

Like you wrote on the list: the problem is caused by damaged
filesytem or damaged tdb files after system crash [unexpected shutdown
because of power failure]. But next samba makes the crash and
unexpected system utilization :(

Partial resolution of the problem: additional lines in samba startup
script which clears contents of the /var/db/samba/ directory on

Additional questions: What functions does Samba use to open tdb files?
Some internal functions or external program? I've upgraded all ports
when upgrading samba from 3.0.23c to 3.0.26a, so maybe some external
libraries cause problems?

Now I reverted samba on my server to version 3.0.24. Next I simulated
power failure (just unplugged my PC ...). After restart I found in

[2007/11/30 08:50:59, 0] tdb/tdbutil.c:tdb_log(783)
  tdb(/var/db/samba/gencache.tdb): tdb_reopen: open failed (No such file or directory)
[2007/11/30 08:50:59, 0] smbd/server.c:open_sockets_smbd(480)
  tdb_reopen_all failed.
[2007/11/30 08:50:59, 0] lib/util.c:smb_panic(1599)
  PANIC (pid 12222): tdb_reopen_all failed.
[2007/11/30 08:50:59, 0] lib/util.c:log_stack_trace(1756)
  unable to produce a stack trace on this platform
[2007/11/30 08:50:59, 0] lib/fault.c:dump_core(173)
  dumping core in /var/log/samba/cores/smbd
[2007/11/30 08:50:59, 0] tdb/tdbutil.c:tdb_log(783)

But the samba crash didn't make my system unstable. No a lot of run
smbd processes with about 100% processor use, like withe the newer
version. The command:

/usr/local/etc/rc.d/samba restart

was enough to clear the problem with 3.0.24. After restart log is
clear and samba works ok.


Once again log from 3.0.26a:

[2007/11/24 17:12:25, 0] lib/util_tdb.c:tdb_log(662)
  tdb(/var/db/samba/gencache.tdb): tdb_reopen: open failed (No such file or directory)
[2007/11/24 17:12:25, 0] smbd/server.c:open_sockets_smbd(572)
  tdb_reopen_all failed.
[2007/11/24 17:12:25, 0] lib/util.c:smb_panic(1632)
  PANIC (pid 5657): tdb_reopen_all failed.
[2007/11/24 17:12:25, 0] lib/fault.c:fault_report(41)
[2007/11/24 17:12:25, 0] lib/fault.c:fault_report(42)
  INTERNAL ERROR: Signal 11 in pid 5657 (3.0.26a)
  Please read the Trouble-Shooting section of the Samba3-HOWTO
[2007/11/24 17:12:25, 0] lib/fault.c:fault_report(44)

  From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2007/11/24 17:12:25, 0] lib/fault.c:fault_report(45)
[2007/11/24 17:12:25, 0] lib/util.c:smb_panic(1632)
  PANIC (pid 5657): internal error

File tdb/tdbutil.c was changed to lib/util_tdb.c. Only name was
changed or whole function was rewriten?

Best regards,
 Marcin                            mailto:marcinkk at enter.net.pl

More information about the samba mailing list