[Samba] Samba 3.2.7 server loses printer - driver assignment - aditional info

[Remy Zandwijk]

Jeremy Allison wrote:
> On Tue, Jan 20, 2009 at 05:07:33PM +0100, Remy Zandwijk wrote:
>>> Our Samba/CUPS based printserver loses the info of which driver belongs 
>>> to a certain printer. The server is running Samba 3.2.7 on Solaris 9.
>> The workstation from which printerdrivers are uploaded runs from a VMware 
>> server VM (XP) which is reverted to the last snapshot every time, to have 
>> a clean machine. The smb log shows:
>>
>> [2009/01/20 16:30:50,  0] lib/fault.c:(40)
>>   ===============================================================
>> [2009/01/20 16:30:50,  0] lib/fault.c:(41)
>>   INTERNAL ERROR: Signal 10 in pid 20404 (3.2.7)
>>   Please read the Trouble-Shooting section of the Samba3-HOWTO
>> [2009/01/20 16:30:50,  0] lib/fault.c:(43)
>>
>>   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
>> [2009/01/20 16:30:50,  0] lib/fault.c:(44)
>>   ===============================================================
>> [2009/01/20 16:30:50,  0] lib/util.c:(1663)
>>   PANIC (pid 20404): internal error
>> [2009/01/20 16:30:50,  0] lib/util.c:(1817)
>>   unable to produce a stack trace on this platform
>> [2009/01/20 16:30:50,  0] lib/fault.c:(201)
>>   dumping core in /var/log/samba/cores/smbd
>>
>>
>> I guess this is bad....Unfortunately, there is no core dump in that directory.
>>
>> Any comments?
> 
> Can you compile with -g and then add the following to
> your smb.conf [global] section please ?
> 
> panic action = "/bin/sleep 99999"
> 
> when you reproduce the crash smbd should be stuck
> waiting for the sleep process to finish. Attach to
> the parent of the sleep process (the crashed smbd)
> with gdb and get a backtrace (the "bt" command).
> 
> This should tell us more about where the problem
> happens.

Hi Jeremy ;-)

I'll compile a -g install tonight and put the panic action into smb.conf. 
Hopefully we can cat it to crash.

-Remy