Re[2]: [Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)
Hello, 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 startup... 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 log.smbd: [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 1): 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, Marcinmailto:[EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re[2]: [Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)
Hello, Sunday, November 25, 2007, 12:25:27 AM, you wrote: DV [EMAIL PROTECTED] wrote: I have a problem with samba 3.0.26a (from ports) on FreeBSD (amd64, SMP, 6.2 RELEASE). My log.smbd looks like below: [...] [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... DV What os the unexpected system shutdown? Power failure? Reset button DV after system freeze? The power failure. [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) DV The filesystem didn't flush it's buffers on shutdown. Unexpectedly, DV files are missing and/or corrupted that should be there on startup. Probably corrupted, becouse I checked: the files exist... And after start samba works properly until next unexpected system restart DV You need to fix this and ensure you're using a journaled file system DV with whatever option is available for the safest, most conservative DV journaling mode. The problem started after 3.0.26a upgrade. I had 3.0.32c run without any problems. Without deleting /var/db/samba, than the samba will start and procedure described on the start of this message will be repeated 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.html My system works with ayhlion 64 x2, but I had similar problem on single processor configuration: pentium 4 and duron too. The problem apears not only after power failure, but also after samba upgrade from ports - make deinstall reinstall. /var/db/samba need to be deleted before reinstall becase samba 3.0.26a has the problem with start with tdb files form 3.0.23c. -- Best regards, Marcin K. mailto:[EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)
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.html My system works with ayhlion 64 x2, but I had similar problem on single processor configuration: pentium 4 and duron too. The problem apears not only after power failure, but also after samba upgrade from ports - make deinstall reinstall. /var/db/samba need to be deleted before reinstall becase samba 3.0.26a has the problem with start with tdb files form 3.0.23c. Better file a bug report then. https://bugzilla.samba.org/enter_bug.cgi Regards, Doug -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [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.html This 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 pgpUHOVqv12lL.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[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. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] INTERNAL ERROR: Signal 11 in pid xxxx (3.0.26a)
[EMAIL PROTECTED] 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 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba