[Samba] Signal 11 in smbd 3.0.2rc2 on printer operation!
Jeremy Allison
jra at samba.org
Thu Feb 5 01:08:38 GMT 2004
On Wed, Feb 04, 2004 at 05:35:11PM -0600, Jerry Haltom wrote:
> Our computers in our office ceased being able to print to a shared cups
> printer today. Could not find the cause. Seems the smbd processes are
> dying. Below is the stack trace produced by gdb bt full.
>
>
>
> The Samba 'panic action' script, /usr/share/samba/panic-action,
> was called for pid 5839 (/usr/opt/samba-3.0.2rc2/sbin/smbd).
>
> 0x40150a59 in wait4 () from /lib/libc.so.6
> #0 0x40150a59 in wait4 () from /lib/libc.so.6
> No symbol table info available.
> #1 0x401c7e48 in __check_rhosts_file () from /lib/libc.so.6
> No symbol table info available.
> #2 0x400f57c5 in system () from /lib/libc.so.6
> No symbol table info available.
> #3 0x081e7625 in smb_panic (why=0x82af4fe "internal error") at lib/util.c:1391
> cmd = 0x83ec268 "/usr/share/samba/panic-action 5839"
> result = 1074632376
> backtrace_stack = {0x0, 0xbfffeee0, 0xbfffefd4, 0x81d174f, 0x82af3e2,
> 0x82e43e0, 0x0, 0xbfffef08, 0x400c9319, 0xbffff628, 0xbfffefd4, 0x81d1757,
> 0xbffff51c, 0x4e4ec24c, 0xbffff55c, 0x8299000, 0x0, 0x400fa582, 0x82f6c4b,
> 0x83d4ae3, 0xbfffef3c, 0x81dd474, 0x83d4ad8, 0x82f6c40, 0x0, 0x0, 0x0, 0x0,
> 0xbffff36c, 0x821a08b, 0x83d4ad8, 0x82f6c40, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
> 0x0, 0x0, 0xbffff598, 0x81d4704, 0x1c, 0x84038d4, 0x68, 0x0, 0x83d4c40, 0x0,
> 0xbfffefcc, 0x81eafe1, 0x400c9319, 0x401c7e48, 0xbffff0fc, 0x401c7e48,
> 0xbffff628, 0x0, 0xbffffd94, 0x4011e1d6, 0x401c7e48, 0x401c56a0, 0x0, 0x0,
> 0x8200b20, 0x4000000}
> backtrace_size = 138426576
> backtrace_strings = (char **) 0x1c
> #4 0x081d1951 in fault_report (sig=11) at lib/fault.c:41
> counter = 1
> #5 0x081d19ba in sig_fault (sig=11) at lib/fault.c:61
> No locals.
> #6 0x400d96b8 in sigaction () from /lib/libc.so.6
> No symbol table info available.
> #7 0x0820b54b in print_queue_status (snum=1, ppqueue=0xbffff4d0,
> status=0xbffff4d4) at printing/printing.c:2283
> keystr = "STATUS/hpljet8100n\0\0\001\0\0\0 öÿ¿ V\034@øB<\bò\006 \b at L=\b\0\0\0\0\0\0\0\0Â\021}\034_duB\227PñØ.\232:´\0\0\0\0\0\0\0\0Döÿ¿,ôÿ¿Q0\026\b\004\0\0\0Döÿ¿\024\0\0\0\0\0\0\0\001\0\0\0\0\0\0\0\004\0\0\0\0\0\0\0\002\0\0\08U=\bLôÿ¿\0361\026\b\220\026=\bDöÿ¿xôÿ¿\004\0\0\0\0\0\0\0\001\0\0\0|ôÿ¿ð\214!\b\001\0\0\0Döÿ¿xôÿ¿,L\023\b\0\0\0\0\224ýÿ¿\214ôÿ¿Kð\017\b"...
> data = {dptr = 0x0, dsize = 264}
> key = {dptr = 0xbffff3ac "STATUS/hpljet8100n", dsize = 18}
> printername = 0x82f6c40 "hpljet8100n"
> pdb = (struct tdb_print_db *) 0x83d4ac8
> count = 0
This is a strange crash location. It appears to be in the call here :
if (!get_stored_queue_info(pdb, snum, &count, ppqueue)) {
release_print_db(pdb);
return 0;
I don't immediately see any bad pointers etc. in this call...
Jeremy.
More information about the samba
mailing list