[Samba] How do I troubleshoot this panic?

Trimble, Ronald D Ronald.Trimble at unisys.com
Fri Jul 7 14:08:24 GMT 2006

Maybe I jumped the gun a little too soon Jerry.  After successfully
logging into the server a few times, it has stopped working again.  That
file has been recreated.  

I am using the default SUSE Linux 10.1 install.  Any other ideas?

-----Original Message-----
From: samba-bounces+ronald.trimble=unisys.com at lists.samba.org
[mailto:samba-bounces+ronald.trimble=unisys.com at lists.samba.org] On
Behalf Of Trimble, Ronald D
Sent: Friday, July 07, 2006 9:58 AM
To: Gerald (Jerry) Carter
Cc: samba at lists.samba.org
Subject: RE: [Samba] How do I troubleshoot this panic?

Deleting that file seemed to have done the trick.  What does that file
do?  What made you suspect this?

-----Original Message-----
From: Gerald (Jerry) Carter [mailto:jerry at samba.org] 
Sent: Friday, July 07, 2006 7:47 AM
To: Trimble, Ronald D
Cc: samba at lists.samba.org
Subject: Re: [Samba] How do I troubleshoot this panic?

Hash: SHA1

Trimble, Ronald D wrote:

> I have a server that has a smb_panic every time 
> I start/restart the winbind service.  How do I go about
> fixing this?  Here is the output from the winbind log file.
>   ===============================================================
>   INTERNAL ERROR: Signal 6 in pid 3835 (3.0.22-11-SUSE-CODE10)
>   Please read the Trouble-Shooting section of the Samba3-HOWTO
>   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
>   ===============================================================
>   PANIC: internal error
>   BACKTRACE: 23 stack frames:
>    #0 /usr/sbin/winbindd(smb_panic2+0x8a) [0x800b699a]
>    #1 /usr/sbin/winbindd(smb_panic+0x19) [0x800b6bf9]
>    #2 /usr/sbin/winbindd [0x800a0f52]
>    #3 [0xffffe420]
>    #4 /lib/libc.so.6(abort+0x103) [0xb7d7dea3]
>    #5 /lib/libc.so.6 [0xb7db1f8b]
>    #6 /lib/libc.so.6(__chk_fail+0x41) [0xb7e23b31]
>    #7 /lib/libc.so.6 [0xb7e23533]
>    #8 /lib/libc.so.6(__snprintf_chk+0x37) [0xb7e23417]
>    #9 /usr/sbin/winbindd [0x8004163a]
>    #10 /usr/sbin/winbindd(tdb_traverse+0xf0) [0x800cdc90]
>    #11 /usr/sbin/winbindd(wcache_flush_cache+0xc0) [0x8003e220]

You can recompile with --enable-debug and run "winbindd -d 10 -i"
under gdb.  Looking at the backtrace, I think if you delete
winbindd_cache.tdb, you might be ok.

cheers, jerry
Samba                                    ------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

More information about the samba mailing list