Re: [Samba] Signal 11 in smbd 3.0.2rc2 on printer operation!
Follow up on this. I have SAMBA_3_0 from CVS, checked out about 4 days
ago (last time we discussed this). I have been able to cause hte
problem, or another similar problem, im not sure, to be reproduced.
What I was doing was adding a new printer, by editing smb.conf, adding
the new printer entry, and then SIGHUPping all smbd processes. After
wards, the new printer began working, but after printing the first page,
all printers immediatly ceased working. The following messages in no
particular order are now appearing in my logs:
tdb(/opt/samba/var/locks/printing/pdfwriter.tdb): tdb_lock failed on
list 4128 ltype=0 (Bad file descriptor)
and
[2004/02/10 13:27:44, 0] tdb/tdbutil.c:tdb_log(724)
tdb(/opt/samba/var/locks/printing/hpljet8100n.tdb): tdb_oob len
842018636 beyond eof at 40960
Perhaps the action of adding a new printer and SIGHUPping smbd is
causing these problems? I will once again attempt to fix this once
people leave the office by clearing all the .tdb files and restarting
samba.
=)
On Thu, 2004-02-05 at 11:29, Jerry Haltom wrote:
> Nope. In fact, I do suspect bad ram. I don't know why it would be
> consistant though. I would think that bad ram would effect more than
> just samba's printing. And you'd think reacreating the process
> (different location in memory) would get around it. The problem is
> pretty consistant, it's happening for every computer in the office now.
>
> On Thu, 2004-02-05 at 10:08, Gerald (Jerry) Carter wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Jerry Haltom wrote:
> > |
> > | Could a corrupt .tdb of any sort be causing this? It
> > | is touching a variable named "pdb" (maybe printer db?),
> > | but I'm not sure what that is.
> >
> > It could I guess, but I agree with Jeremy. That's a
> > strange place to crash. How many machines did you
> > see this on? If only one, have you ruled out bad RAM ?
> >
> > On Wed, 2004-02-04 at 19:08, Jeremy Allison wrote:
> >
> > |>> #7 0x0820b54b in print_queue_status (snum=1, ppqueue=0xb4d0,
> > |>>status=0xb4d4) at printing/printing.c:2283
> > |>> keystr = "STATUS/hpljet8100n\0\0\001\0\0\0 öÿ¿ [EMAIL PROTECTED]<\bò\006
> > [EMAIL
> > PROTECTED]:´\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 = 0xb3ac "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...
> >
> >
> >
> >
> > cheers, jerry
> > -BEGIN PGP SIGNATURE-
> > Version: GnuPG v1.2.1 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFAImqUIR7qMdg1EfYRAikcAJ43erXruQhRuLE7arSDsDUROwnVuQCgyLwU
> > 8T0AGaPERFSb0WPYVczJEKE=
> > =G3Fk
> > -END PGP SIGNATURE-
--
Jerry Haltom <[EMAIL PROTECTED]>
Feedback Plus, Inc.
signature.asc
Description: This is a digitally signed message part
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Signal 11 in smbd 3.0.2rc2 on printer operation!
On Thu, Feb 05, 2004 at 11:29:16AM -0600, Jerry Haltom wrote: > Nope. In fact, I do suspect bad ram. I don't know why it would be > consistant though. I would think that bad ram would effect more than > just samba's printing. And you'd think reacreating the process > (different location in memory) would get around it. The problem is > pretty consistant, it's happening for every computer in the office now. A corrupt tdb wouldn't cause a failure in the place you sent in. I'd use memcheck to look for bad ram. Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Signal 11 in smbd 3.0.2rc2 on printer operation!
Nope. In fact, I do suspect bad ram. I don't know why it would be
consistant though. I would think that bad ram would effect more than
just samba's printing. And you'd think reacreating the process
(different location in memory) would get around it. The problem is
pretty consistant, it's happening for every computer in the office now.
On Thu, 2004-02-05 at 10:08, Gerald (Jerry) Carter wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Jerry Haltom wrote:
> |
> | Could a corrupt .tdb of any sort be causing this? It
> | is touching a variable named "pdb" (maybe printer db?),
> | but I'm not sure what that is.
>
> It could I guess, but I agree with Jeremy. That's a
> strange place to crash. How many machines did you
> see this on? If only one, have you ruled out bad RAM ?
>
> On Wed, 2004-02-04 at 19:08, Jeremy Allison wrote:
>
> |>> #7 0x0820b54b in print_queue_status (snum=1, ppqueue=0xb4d0,
> |>>status=0xb4d4) at printing/printing.c:2283
> |>> keystr = "STATUS/hpljet8100n\0\0\001\0\0\0 öÿ¿ [EMAIL PROTECTED]<\bò\006
> [EMAIL
> PROTECTED]:´\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 = 0xb3ac "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...
>
>
>
>
> cheers, jerry
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.1 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFAImqUIR7qMdg1EfYRAikcAJ43erXruQhRuLE7arSDsDUROwnVuQCgyLwU
> 8T0AGaPERFSb0WPYVczJEKE=
> =G3Fk
> -END PGP SIGNATURE-
--
Jerry Haltom <[EMAIL PROTECTED]>
Feedback Plus, Inc.
signature.asc
Description: This is a digitally signed message part
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Signal 11 in smbd 3.0.2rc2 on printer operation!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jerry Haltom wrote:
|
| Could a corrupt .tdb of any sort be causing this? It
| is touching a variable named "pdb" (maybe printer db?),
| but I'm not sure what that is.
It could I guess, but I agree with Jeremy. That's a
strange place to crash. How many machines did you
see this on? If only one, have you ruled out bad RAM ?
On Wed, 2004-02-04 at 19:08, Jeremy Allison wrote:
|>> #7 0x0820b54b in print_queue_status (snum=1, ppqueue=0xb4d0,
|>>status=0xb4d4) at printing/printing.c:2283
|>> keystr = "STATUS/hpljet8100n\0\0\001\0\0\0 öÿ¿ [EMAIL PROTECTED]<\bò\006
[EMAIL
PROTECTED]:´\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 = 0xb3ac "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...
cheers, jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAImqUIR7qMdg1EfYRAikcAJ43erXruQhRuLE7arSDsDUROwnVuQCgyLwU
8T0AGaPERFSb0WPYVczJEKE=
=G3Fk
-END PGP SIGNATURE-
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Signal 11 in smbd 3.0.2rc2 on printer operation!
I don't know enough about what is going on to know if what I'm saying
makes any sense. :) But I'm working on it.
Could a corrupt .tdb of any sort be causing this? It is touching a
variable named "pdb" (maybe printer db?), but I'm not sure what that is.
Since I had the problem I have deleted all of my tbds and recreated
necessary data. However, I did it as part of a few troubleshooting
steps, and didn't check 100% to make sure my changes fixed it.
It appears to be fixed on the two systems I can access from home to test
from, however, our office has 25 more systems, which I can't get from
home to test with. I will follow up on this if the problem is resolved.
If somebody could confirm a corrupted tdb could be responsible for this,
I won't pursue it any further unless it resurfaces. Thanks!
On Wed, 2004-02-04 at 19:08, Jeremy Allison wrote:
> 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, 0xb628, 0xbfffefd4, 0x81d1757,
> > 0xb51c, 0x4e4ec24c, 0xb55c, 0x8299000, 0x0, 0x400fa582, 0x82f6c4b,
> > 0x83d4ae3, 0xbfffef3c, 0x81dd474, 0x83d4ad8, 0x82f6c40, 0x0, 0x0, 0x0, 0x0,
> > 0xb36c, 0x821a08b, 0x83d4ad8, 0x82f6c40, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
> > 0x0, 0x0, 0xb598, 0x81d4704, 0x1c, 0x84038d4, 0x68, 0x0, 0x83d4c40, 0x0,
> > 0xbfffefcc, 0x81eafe1, 0x400c9319, 0x401c7e48, 0xb0fc, 0x401c7e48,
> > 0xb628, 0x0, 0xbd94, 0x4011e1d6, 0x401c7e48, 0x401c56a0, 0x0, 0x0,
> > 0x8200b20, 0x400}
> > 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=0xb4d0,
> > status=0xb4d4) at printing/printing.c:2283
> > keystr = "STATUS/hpljet8100n\0\0\001\0\0\0 öÿ¿ [EMAIL PROTECTED]<\bò\006
> > [EMAIL
> > PROTECTED]:´\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 = 0xb3ac "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.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Signal 11 in smbd 3.0.2rc2 on printer operation!
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, 0xb628, 0xbfffefd4, 0x81d1757,
> 0xb51c, 0x4e4ec24c, 0xb55c, 0x8299000, 0x0, 0x400fa582, 0x82f6c4b,
> 0x83d4ae3, 0xbfffef3c, 0x81dd474, 0x83d4ad8, 0x82f6c40, 0x0, 0x0, 0x0, 0x0,
> 0xb36c, 0x821a08b, 0x83d4ad8, 0x82f6c40, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0,
> 0x0, 0x0, 0xb598, 0x81d4704, 0x1c, 0x84038d4, 0x68, 0x0, 0x83d4c40, 0x0,
> 0xbfffefcc, 0x81eafe1, 0x400c9319, 0x401c7e48, 0xb0fc, 0x401c7e48,
> 0xb628, 0x0, 0xbd94, 0x4011e1d6, 0x401c7e48, 0x401c56a0, 0x0, 0x0,
> 0x8200b20, 0x400}
> 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=0xb4d0,
> status=0xb4d4) at printing/printing.c:2283
> keystr = "STATUS/hpljet8100n\0\0\001\0\0\0 öÿ¿ [EMAIL PROTECTED]<\bò\006
> [EMAIL
> PROTECTED]:´\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 = 0xb3ac "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.
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
