marcinkk@enter.net.pl
2007-Nov-24 19:50 UTC
[Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)
Hello, I have a problem with samba 3.0.26a (from ports) on FreeBSD (amd64, SMP, 6.2 RELEASE). My log.smbd looks like below: --- samba starts normally: [2007/11/24 16:55:22, 0] smbd/server.c:main(944) smbd version 3.0.26a started. Copyright Andrew Tridgell and the Samba Team 1992-2007 --- but an error is reported: [2007/11/24 16:55:22, 0] /usr/ports/net/samba3/work/samba-3.0.26a/source/lib/pidfile.c:pidfile_create(112) ERROR: smbd is already running. File /var/run/smbd.pid exists and process id 1961 is running. --- /var/run/smbd.pid exists, becase the error is created after unexpected system shutdown... --- next I can see in log.smbd: [2007/11/24 16:59:53, 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 16:59:53, 0] smbd/server.c:open_sockets_smbd(572) tdb_reopen_all failed. [2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632) PANIC (pid 2621): tdb_reopen_all failed. [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(41) ==============================================================[2007/11/24 16:59:53, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 2621 (3.0.26a) Please read the Trouble-Shooting section of the Samba3-HOWTO [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(45) ==============================================================[2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632) PANIC (pid 2621): internal error [2007/11/24 16:59:53, 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 16:59:53, 0] smbd/server.c:open_sockets_smbd(572) tdb_reopen_all failed. [2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632) PANIC (pid 2622): tdb_reopen_all failed. [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(41) ==============================================================[2007/11/24 16:59:53, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 2622 (3.0.26a) Please read the Trouble-Shooting section of the Samba3-HOWTO [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(44) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(45) --- the error is repeated about 100 times ... and it is still repeated. Next I can see in the top a lot of run smbd processes. System load grows and smbd makes it unresponsible. Connection with ssh is impossible, I can only use (with problems) console. Command "killall -9 smbd" helps, system goes back to normal work. I can run samba again but I must use the following procedure: - cd /usr/ports/net/samba3 - make deinstall Samba is now deinstalled. Next I must delete the directory /var/db/samba an I can do: - make reinstall And after start samba works properly until next unexpected system restart :( If I do only: - make deinstall reinstall Without deleting /var/db/samba, than the samba will start and procedure described on the start of this message will be repeated :( It is problem with FreeBSD on amd64? Or the problem with samba 3.0.26a? I reverted to samba 3.0.24 to check if the problem back... Regards, Marcin K.
Doug VanLeuven
2007-Nov-24 23:30 UTC
[Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)
marcinkk@enter.net.pl wrote:> Hello, > > I have a problem with samba 3.0.26a (from ports) on FreeBSD (amd64, > SMP, 6.2 RELEASE). My log.smbd looks like below: > > --- samba starts normally: > > [2007/11/24 16:55:22, 0] smbd/server.c:main(944) > smbd version 3.0.26a started. > Copyright Andrew Tridgell and the Samba Team 1992-2007 > > --- but an error is reported: > > [2007/11/24 16:55:22, 0] > /usr/ports/net/samba3/work/samba-3.0.26a/source/lib/pidfile.c:pidfile_create(112) > > ERROR: smbd is already running. File /var/run/smbd.pid exists and > process id 1961 is running. > > --- /var/run/smbd.pid exists, becase the error is created after > unexpected system shutdown...What os the unexpected system shutdown? Power failure? Reset button after system freeze?> > --- next I can see in log.smbd: > > [2007/11/24 16:59:53, 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 16:59:53, 0] smbd/server.c:open_sockets_smbd(572) > tdb_reopen_all failed. > [2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632) > PANIC (pid 2621): tdb_reopen_all failed. > [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(41)The filesystem didn't flush it's buffers on shutdown. Unexpectedly, files are missing and/or corrupted that should be there on startup.> > ==============================================================> [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(42) > INTERNAL ERROR: Signal 11 in pid 2621 (3.0.26a) > Please read the Trouble-Shooting section of the Samba3-HOWTO > [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(44) > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(45) > ==============================================================> [2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632) > PANIC (pid 2621): internal error > [2007/11/24 16:59:53, 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 16:59:53, 0] smbd/server.c:open_sockets_smbd(572) > tdb_reopen_all failed. > [2007/11/24 16:59:53, 0] lib/util.c:smb_panic(1632) > PANIC (pid 2622): tdb_reopen_all failed. > [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(41) > ==============================================================> [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(42) > INTERNAL ERROR: Signal 11 in pid 2622 (3.0.26a) > Please read the Trouble-Shooting section of the Samba3-HOWTO > [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(44) > > From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf > [2007/11/24 16:59:53, 0] lib/fault.c:fault_report(45) > > --- the error is repeated about 100 times ... and it is still repeated. > > Next I can see in the top a lot of run smbd processes. System load > grows and smbd makes it unresponsible. Connection with ssh is > impossible, I can only use (with problems) console. Command "killall > -9 smbd" helps, system goes back to normal work. > > I can run samba again but I must use the following procedure: > > - cd /usr/ports/net/samba3 > - make deinstall > > Samba is now deinstalled. Next I must delete the directory > /var/db/samba an I can do: > > - make reinstall > > And after start samba works properly until next unexpected system > restart :(You need to fix this and ensure you're using a journaled file system with whatever option is available for the safest, most conservative journaling mode.> > If I do only: > > - make deinstall reinstall > > Without deleting /var/db/samba, than the samba will start and > procedure described on the start of this message will be repeated :(You should be able to delete /var/db/samba (plus maybe the pid file) and restart samba. Samba will create any tdb files it needs like the initial startup.> > It is problem with FreeBSD on amd64? Or the problem with samba > 3.0.26a? I reverted to samba 3.0.24 to check if the problem back...Regards, Doug
Volker Lendecke
2007-Nov-25 13:45 UTC
[Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)
On Sun, Nov 25, 2007 at 05:29:52AM -0800, Doug VanLeuven wrote:> Marcin Kucharczyk wrote: > >DV> You should be able to delete /var/db/samba (plus maybe the pid file) > >and > >DV> restart samba. Samba will create any tdb files it needs like the > >DV> initial startup. > > > >Tried ... reinstall was required > > > >Some mor information: > > > >It looks like the same or similar problem: > > http://lists.samba.org/archive/samba/2007-August/134620.htmlThis particular bug report is highly unlikely to be a Samba problem. Also, I have a hard time to believe that you have to really deinstall Samba after a system crash. It *is* definitely possible to restart Samba from whatever state the system is in, possibly by removing tdb files. Removing and recompiling the daemons is definitely unnecessary. You might want to see what this removing/reinstalling really does. Volker -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.samba.org/archive/samba/attachments/20071125/aa1068cc/attachment.bin