Hi All, I hope someone can help me with this problem. I recently moved my Windows Print server to Linux (Red Hat 9.0, Samba 3.0.2) due to stability problems, however since i had a constant smbd panics I reverted back to my Windows 2000 server much to the disappointment of my manager and director. Having posted to this list someone suggested an upgrade to 3.0.3pre2 which solved their issues, I have now tried this and the problem would appear to keep returning. I have the server configured, and running in a test environment and all is well, I started loading my print drivers on, and checking my syslog revealed that the smbd was yet again panicing and bombing out with the following message:- Apr 20 15:21:02 gandalf2 smbd[6891]: [2004/04/20 15:21:02, 0] lib/fault.c:fault_report(36) Apr 20 15:21:02 gandalf2 smbd[6891]: =============================================================== Apr 20 15:21:02 gandalf2 smbd[6891]: [2004/04/20 15:21:02, 0] lib/fault.c:fault_report(37) Apr 20 15:21:02 gandalf2 smbd[6891]: INTERNAL ERROR: Signal 11 in pid 6891 (3.0.3pre2) Apr 20 15:21:02 gandalf2 smbd[6891]: Please read the appendix Bugs of the Samba HOWTO collection Apr 20 15:21:02 gandalf2 smbd[6891]: [2004/04/20 15:21:02, 0] lib/fault.c:fault_report(39) Apr 20 15:21:02 gandalf2 smbd[6891]: =============================================================== Apr 20 15:21:02 gandalf2 smbd[6891]: [2004/04/20 15:21:02, 0] lib/util.c:smb_panic2(1398) Apr 20 15:21:02 gandalf2 smbd[6891]: PANIC: internal error Apr 20 15:21:02 gandalf2 smbd[6891]: [2004/04/20 15:21:02, 0] lib/util.c:smb_panic2(1406) Apr 20 15:21:02 gandalf2 smbd[6891]: BACKTRACE: 27 stack frames: Apr 20 15:21:02 gandalf2 smbd[6891]: #0 smbd(smb_panic2+0x128) [0x81cb288] Apr 20 15:21:02 gandalf2 smbd[6891]: #1 smbd(smb_panic+0x19) [0x81cb159] Apr 20 15:21:02 gandalf2 smbd[6891]: #2 smbd [0x81b96f2] Apr 20 15:21:02 gandalf2 smbd[6891]: #3 /lib/tls/libc.so.6 [0x420275c8] Apr 20 15:21:02 gandalf2 smbd[6891]: #4 /lib/tls/libc.so.6(malloc+0x8b) [0x4207335b] Apr 20 15:21:02 gandalf2 smbd[6891]: #5 smbd(tdb_unpack+0x13b) [0x81e0b8b] Apr 20 15:21:02 gandalf2 smbd[6891]: #6 smbd [0x81f10ce] Apr 20 15:21:02 gandalf2 smbd[6891]: #7 smbd [0x81f1cd6] Apr 20 15:21:02 gandalf2 smbd[6891]: #8 smbd(get_a_printer+0x126) [0x81f3026] Apr 20 15:21:02 gandalf2 smbd[6891]: #9 smbd(_spoolss_getprinterdataex+0x1be) [0x8131dce] Apr 20 15:21:02 gandalf2 smbd[6891]: #10 smbd [0x811de3b] Apr 20 15:21:02 gandalf2 smbd[6891]: #11 smbd(api_rpcTNP+0x159) [0x814eba9] Apr 20 15:21:02 gandalf2 smbd[6891]: #12 smbd(api_pipe_request+0xaf) [0x814e96f] Apr 20 15:21:02 gandalf2 smbd[6891]: #13 smbd [0x8148056] Apr 20 15:21:02 gandalf2 smbd[6891]: #14 smbd [0x81483a9] Apr 20 15:21:02 gandalf2 smbd[6891]: #15 smbd [0x81485eb] Apr 20 15:21:02 gandalf2 smbd[6891]: #16 smbd [0x81487ec] Apr 20 15:21:02 gandalf2 smbd[6891]: #17 smbd(write_to_pipe+0xf2) [0x8148742] Apr 20 15:21:02 gandalf2 smbd[6891]: #18 smbd [0x808a58e] Apr 20 15:21:02 gandalf2 smbd[6891]: #19 smbd(reply_trans+0x54b) [0x808af5b] Apr 20 15:21:02 gandalf2 smbd[6891]: #20 smbd [0x80cb4ac] Apr 20 15:21:02 gandalf2 smbd[6891]: #21 smbd [0x80cb679] Apr 20 15:21:02 gandalf2 smbd[6891]: #22 smbd(process_smb+0x8f) [0x80cb88f] Apr 20 15:21:02 gandalf2 smbd[6891]: #23 smbd(smbd_process+0x167) [0x80cc4d7] Apr 20 15:21:02 gandalf2 smbd[6891]: #24 smbd(main+0x4d9) [0x82384a9] Apr 20 15:21:02 gandalf2 smbd[6891]: #25 /lib/tls/libc.so.6(__libc_start_main+0xe4) [0x42015574] Apr 20 15:21:02 gandalf2 smbd[6891]: #26 smbd(chroot+0x31) [0x8077521] Apr 20 15:21:02 gandalf2 smbd[6891]: Apr 20 15:21:02 gandalf2 smbd[6916]: [2004/04/20 15:21:02, 0] smbd/connection.c:register_message_flags(220) Apr 20 15:21:02 gandalf2 smbd[6916]: register_message_flags: tdb_fetch failed I understand that 3.0.3pre2 is a development version but I would appreciate some feed back on this issue, any suggestions to what may be causing it and any ideas as to how I can solve it. Thanks All Jez
> Apr 20 15:21:02 gandalf2 smbd[6891]: BACKTRACE: 27 stack frames: > Apr 20 15:21:02 gandalf2 smbd[6891]: #0 smbd(smb_panic2+0x128) > [0x81cb288] > Apr 20 15:21:02 gandalf2 smbd[6891]: #1 smbd(smb_panic+0x19) > [0x81cb159] > Apr 20 15:21:02 gandalf2 smbd[6891]: #2 smbd [0x81b96f2] > Apr 20 15:21:02 gandalf2 smbd[6891]: #3 /lib/tls/libc.so.6[0x420275c8]> Apr 20 15:21:02 gandalf2 smbd[6891]: #4/lib/tls/libc.so.6(malloc+0x8b)> [0x4207335b] > Apr 20 15:21:02 gandalf2 smbd[6891]: #5 smbd(tdb_unpack+0x13b) > [0x81e0b8b] > Apr 20 15:21:02 gandalf2 smbd[6891]: #6 smbd [0x81f10ce] > Apr 20 15:21:02 gandalf2 smbd[6891]: #7 smbd [0x81f1cd6] > Apr 20 15:21:02 gandalf2 smbd[6891]: #8 smbd(get_a_printer+0x126)Are there any messages earlier, like "Removing file and stopping this process" ? ~ Daniel ----------------------------------------------------------------------- This message is the property of Time Inc. or its affiliates. It may be legally privileged and/or confidential and is intended only for the use of the addressee(s). No addressee should forward, print, copy, or otherwise reproduce this message in any manner that would allow it to be viewed by any individual not originally listed as a recipient. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. Thank you.
Jeramy Eling wrote:> [2004/04/20 15:21:02, 0] lib/util.c:smb_panic2(1406) > BACKTRACE: 27 stack frames: > #0 smbd(smb_panic2+0x128) [0x81cb288] > #1 smbd(smb_panic+0x19) [0x81cb159] > #2 smbd [0x81b96f2] > #3 /lib/tls/libc.so.6 [0x420275c8] > #4 /lib/tls/libc.so.6(malloc+0x8b) [0x4207335b]^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^> #5 smbd(tdb_unpack+0x13b) [0x81e0b8b] > #6 smbd [0x81f10ce] > #7 smbd [0x81f1cd6] > #8 smbd(get_a_printer+0x126) [0x81f3026] > #9 smbd(_spoolss_getprinterdataex+0x1be) [0x8131dce]This points towards a heap corruption bug. Doesn't ring a bell. Cna you reproduce this at will ? If so what do I need to do ? 3.0.3rc1 will be out later today we hope. And while I can't say that for sure that this bug is addressed, you should test. We will also be spending a good bit of time stressing this release under valgrind before we hit 3.0.3. -- cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc "...a hundred billion castaways looking for a home." ----------- Sting
I have now upgraded to 3.0.3RC1 and the panic still occurs. It would appear to happen only when I install HP print drivers though, I have installed brother and Epson drivers without any issues at all. When I ran the server on 2.2.8 for initial testing it was stable, but due to the restriction in the maximum printer name length I had to jump to version 3. I would welcome any other suggestions from anyone, before I confine myself back to my windows server for now. Jez -----Original Message----- From: Gerald (Jerry) Carter [mailto:jerry@samba.org] Sent: 20 April 2004 21:36 To: Jeramy Eling Cc: samba@lists.samba.org Subject: Re: [Samba] Panic in Samba 3.0.3Pre2 Jeramy Eling wrote:> [2004/04/20 15:21:02, 0] lib/util.c:smb_panic2(1406) > BACKTRACE: 27 stack frames: > #0 smbd(smb_panic2+0x128) [0x81cb288] > #1 smbd(smb_panic+0x19) [0x81cb159] > #2 smbd [0x81b96f2] > #3 /lib/tls/libc.so.6 [0x420275c8] > #4 /lib/tls/libc.so.6(malloc+0x8b) [0x4207335b]^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^> #5 smbd(tdb_unpack+0x13b) [0x81e0b8b] > #6 smbd [0x81f10ce] > #7 smbd [0x81f1cd6] > #8 smbd(get_a_printer+0x126) [0x81f3026] > #9 smbd(_spoolss_getprinterdataex+0x1be) [0x8131dce]This points towards a heap corruption bug. Doesn't ring a bell. Cna you reproduce this at will ? If so what do I need to do ? 3.0.3rc1 will be out later today we hope. And while I can't say that for sure that this bug is addressed, you should test. We will also be spending a good bit of time stressing this release under valgrind before we hit 3.0.3. -- cheers, jerry ---------------------------------------------------------------------- Hewlett-Packard ------------------------- http://www.hp.com SAMBA Team ---------------------- http://www.samba.org GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc "...a hundred billion castaways looking for a home." ----------- Sting