[Samba] Re: (Samba) Winbind dies
dyioulos at firstbhph.com
Fri Jul 14 18:05:17 GMT 2006
On Thursday July 13 2006 12:39 pm, you wrote:
> Dimitri Yioulos wrote:
> > Serious apologies if this has been discussed before,
> > but my search didn't turn up much:
> > I have samba (kept up-to-date with latest) running on
> > several CentOS 3 and 4 boxes as part of a Win2k3
> > domain. On one particular box, winbind dies on
> > a regular basis (all the other installations run
> > flawlessly). A quick restart, and we're good
> > again. However, as this is a very active server
> > that is accessed 18 hours a day, 7 days a week,
> > I'm called at home during those few hours I spend
> > there to restart winbind on this particular machine.
> The is the second report of winbindd crash in the krb5 libs.
> The other was an FC5 box.
> > INTERNAL ERROR: Signal 6 in pid 23775 (3.0.23)
> > Jul 12 18:26:06 norwell winbindd: BACKTRACE: 28 stack
> > frames: #0 winbindd(log_stack_trace+0x2d) [0x5f5add]
> > #1 winbindd(smb_panic+0x75) [0x5f5985]
> > #2 winbindd [0x5e10d6]
> > #3 /lib/tls/libc.so.6 [0x1b70d8]
> > #4 /lib/tls/libc.so.6 (abort+0x1d5) [0x1b8705]
> > #5 winbindd [0x61c6d2]
> > #6 winbindd [0x61c955]
> > #7 winbindd(cli_krb5_get_ticket+0x242) [0x61ce32]
> > #8 winbindd(spnego_gen_negTokenTarg+0x62) [0x61e9c2]
> We're working on it. If you could get a backtrace
> including debugging symbols, that would help.
> cheers, jerry
I posted a backtrace (at least, I think it was) of the core dump
yesterday. Does that work to troubleshoot this issue?
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the samba