[Samba] Problems after upgrade to 3.0.21

[Jeremy Allison]

On Tue, Dec 27, 2005 at 11:33:36AM +0000, Michael Keightley wrote:
> 
> We have two sites, one has a Solaris 8 PDC running Samba v3.0.20.
> The other has a SuSE 9.3 PDC running Samba v3.0.20b.
> I upgraded them both to Samba v3.0.21, and had similar problems.  Profiles were
> often not being saved and I was getting an INTERNAL ERROR in the Samba log when
> a user logged in.
> I eventually had to go back to the previous version of Samba.  
> This is the error on our Solaris PDC:
> 
> [2005/12/27 11:12:52, 1] smbd/service.c:make_connection_snum(666)
>   jack (194.80.190.32) connect to service testy initially as user testy (uid=1155, gid=20) (pid 13227)
> [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(36)
>   ===============================================================
> [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(37)
>   INTERNAL ERROR: Signal 10 in pid 13227 (3.0.21)
>   Please read the Trouble-Shooting section of the Samba3-HOWTO
> [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(39)
>   
>   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2005/12/27 11:12:53, 0] lib/fault.c:fault_report(40)
>   ===============================================================
> [2005/12/27 11:12:53, 0] lib/util.c:smb_panic2(1554)
>   PANIC: internal error
> [2005/12/27 11:12:53, 1] smbd/service.c:make_connection_snum(666)
>   jack (194.80.190.32) connect to service netlogon initially as user testy (uid=1155, gid=20) (pid 13231)
> 
> 
> On SuSE Linux the error had more info:
> 
>   ===============================================================
> [2005/12/26 12:03:02, 0] lib/fault.c:fault_report(37)
>   INTERNAL ERROR: Signal 11 in pid 16007 (3.0.21)
>   Please read the Trouble-Shooting section of the Samba3-HOWTO
> [2005/12/26 12:03:02, 0] lib/fault.c:fault_report(39)
>   
>   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2005/12/26 12:03:02, 0] lib/fault.c:fault_report(40)
>   ===============================================================
> [2005/12/26 12:03:02, 0] lib/util.c:smb_panic2(1554)
>   PANIC: internal error
> [2005/12/26 12:03:02, 0] lib/util.c:smb_panic2(1562)
>   BACKTRACE: 28 stack frames:
>    #0 /home/samba_shark/sbin/smbd(smb_panic2+0x193) [0x59c720]
>    #1 /home/samba_shark/sbin/smbd(smb_panic+0xe) [0x59c588]
>    #2 /home/samba_shark/sbin/smbd [0x58aaac]
>    #3 /home/samba_shark/sbin/smbd [0x58ab08]
>    #4 /lib64/tls/libc.so.6 [0x2aaaab3f4f00]
>    #5 /home/samba_shark/sbin/smbd(lookup_printerkey+0x8f) [0x5c0ae7]

Looks like a printer code bug. Can you compile with -g, add the line

panic action = /bin/sleep 999999

to the [global] section of your smb.conf and recreate the crash.
Then attach to the crashed smbd process with gdb and type "bt"
to get a back-trace.

Thanks a lot,

Jeremy.