[Samba] Samba 3.0.21 + PANIC: internal error + lib/fault.c

Jeremy Allison jra at samba.org
Thu Dec 22 18:18:05 GMT 2005


On Thu, Dec 22, 2005 at 05:05:47PM +0100, Ralf Gross wrote:
> Hi,
> 
> yesterday I compiled an installed samba 3.0.21 on a solaris 8 box (gcc
> 3.4.2). Since then I frequently see this error message in the log.
> 
> 
> [2005/12/22 15:55:39, 0] lib/fault.c:fault_report(36)
>   ===============================================================
> [2005/12/22 15:55:39, 0] lib/fault.c:fault_report(37)
>   INTERNAL ERROR: Signal 10 in pid 27816 (3.0.21)
>   Please read the Trouble-Shooting section of the Samba3-HOWTO
> [2005/12/22 15:55:39, 0] lib/fault.c:fault_report(39)
>   
>   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
> [2005/12/22 15:55:39, 0] lib/fault.c:fault_report(40)
>   ===============================================================
> [2005/12/22 15:55:39, 0] lib/util.c:smb_panic2(1554)
>   PANIC: internal error
> [2005/12/22 15:55:43, 0] modules/vfs_extd_audit.c:audit_unlink(273)
>   vfs_extd_audit: unlink work/Zeiten/Zeiten_03_03.xls~RF1b9fdb8.TMP  
> [2005/12/22 15:55:43, 0] modules/vfs_extd_audit.c:audit_unlink(273)
>   vfs_extd_audit: unlink work/Zeiten/Zeiten_03_03.xls  
> 
> I compiled samba with the following configure settings:
> ./configure --with-acl-support --prefix=/usr/local/samba3021
> --with-quotas --with-included-popt --without-ldap --with-vfs
> 
> I already disabled the 'vfs objects' option for each share, because
> this was the only thing I changed in addition to move from 3.0.20b to
> 3.0.21. This didn't helt. There is no core file in any samba related
> directory (/usr/local/samba, /var/log/samba).

Try adding -g and do a full recompile - this will ensure the smbd binary
has symbols embedded in it. Then add the line :

panic action = /bin/sleep 999999

to the [global] section of your smb.conf and restart smbd. When 
the panic occurs you will have a frozen smbd process as the parent
as a sleep process. Start gdb :

gdb /usr/local/samba/sbin/smbd

and then attach to the frozen smbd process via :

attach <pid>

Then type "bt" to get the backtrace that will show us where the problem
lies.

Thanks,

	Jeremy.


More information about the samba mailing list