Just had another winbind crash - but the panic action did not trigger. No
messages in the logs so it never even attempted the panic shell script.
I'll give it another chance and then try the sleep option.
Same rid 512 (Domain Admins) is repsonsible. Could this be a problem with
the upgrade from 2.2.2 to 2.2.3pre ? The only file I bought across was the
winbindd_idmap.tdb. And I rejoined the domain and secret is good. All
these "could not get domain sid for domain @UK" worry me as I don;t
understand where they are coming from. Winbind functions fine (until it
bombs).
Noel
[2002/01/09 20:09:21, 0]
nsswitch/winbindd_group.c:winbindd_getgrnam_from_group(220)
getgrname_from_group(): could not get domain sid for domain @UK
[2002/01/09 22:10:31, 1] nsswitch/winbindd_group.c:fill_grent_mem(87)
fill_grent_mem(): could not lookup membership for group rid 512 in domain
UK
[2002/01/09 22:10:31, 0] lib/fault.c:fault_report(38)
==============================================================[2002/01/09
22:10:31, 0] lib/fault.c:fault_report(39)
INTERNAL ERROR: Signal 11 in pid 12731 (2.2.3-pre)
Please read the file BUGS.txt in the distribution
[2002/01/09 22:10:31, 0] lib/fault.c:fault_report(41)
==============================================================[2002/01/09
22:10:31, 0] lib/util.c:smb_panic(1068)
PANIC: internal error
-----Original Message-----
From: Tim Potter [mailto:tpot@samba.org]
Sent: 09 January 2002 20:27
To: Noel Kelly
Cc: Jeremy Allison; 'samba@lists.samba.org'
Subject: Re: Another RE: 2.2.3pre winbindd crash
On Wed, Jan 09, 2002 at 08:21:08PM -0000, Noel Kelly wrote:
> I have ended up concocting this - look OK ?
>
> smb.conf = panic action = "/root/panic.sh %d"
>
> /root/panic.sh >
> #!/bin/sh
>
> logger SAMBA PANIC ACTION Starting `date`...
> /usr/bin/X11/xterm -display :2.0 -e gdb /usr/local/samba/bin/winbindd $1
> logger SAMBA PANIC ACTION Stopped `date`
Looks OK - make sure you can display an xterm from root's shell.
I do xhost +localhost and xterm -display localhost:0
Tim.