Samba "INTERNAL ERROR: Signal 6"

[Angusby2]

I am running Samba 3.02a on Slackware 9.1. All was well for a few months until 4 days ago Samba started having a Panic. No new software has been installed in the past 3 weeks, server runs 24/7. I am rather new to Linux but do have a bit of UNIX admin. I have search the net to no avail for anything on this error. Could anyone in this form give any suggestions on what when wrong and how to fix it? I have set log level to debug 3, Config and log file below.

SAMBA lib/smbd.conf
----------------------
# Samba config file created using SWAT
# from 192.168.1.99 (192.168.1.99)
# Date: 2004/07/05 17:17:09

# Global parameters
[global]
workgroup = HOMENET
server string = Samba Server
log file = /usr/local/samba/var/log.%m
log level = 3
max log size = 512
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = No
:netbios name = spock

[homes]
comment = Home Directories
read only = No
browseable = No

[datastore]
comment = DeskTop File Share
path = /mysqldata/share
valid users = jason, angus50
read only = No

[WebSite]
comment = DeskTop Web Site
path = /var/www/website
valid users = jason, angus50
force user = root
force group = webgroup
read only = No
create mask = 0764


SAMBA var/log.smbd
-------------------------------
[2004/07/11 19:00:28, 0] smbd/server.c:main(747)
smbd version 3.0.2a started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2004/07/11 19:00:28, 2] param/loadparm.c:do_section(3339)
Processing section "[homes]"
[2004/07/11 19:00:28, 2] param/loadparm.c:do_section(3339)
Processing section "[datastore]"
[2004/07/11 19:00:28, 2] param/loadparm.c:do_section(3339)
Processing section "[WebSite]"
[2004/07/11 19:00:28, 3] param/loadparm.c:lp_add_ipc(2349)
adding IPC service
[2004/07/11 19:00:28, 3] param/loadparm.c:lp_add_ipc(2349)
adding IPC service
[2004/07/11 19:00:28, 2] lib/interface.c:add_interface(79)
added interface ip=192.168.1.98 bcast=192.168.1.103 nmask=255.255.255.248
[2004/07/11 19:00:28, 3] smbd/server.c:main(777)
loaded services
[2004/07/11 19:00:28, 3] smbd/server.c:main(792)
Becoming a daemon.
[2004/07/11 19:00:28, 0] lib/util.crocess_exists(1277)
PANIC: assert failed at lib/util.c(1277)
[2004/07/11 19:00:28, 0] lib/util.c:smb_panic(1400)
PANIC: assert failed
[2004/07/11 19:00:28, 0] lib/util.c:smb_panic(140
BACKTRACE: 7 stack frames:
#0 ./smbd(smb_panic+0x181) [0x8184a31]
#1 ./smbd(process_exists+0x6a) [0x8184730]
#2 ./smbd(pidfile_pid+0x8c) [0x8176c40]
#3 ./smbd(pidfile_create+0x35) [0x8176cc9]
#4 ./smbd(main+0x465) [0x81d0fbe]
#5 /lib/libc.so.6(__libc_start_main+0xc6) [0x401d4d06]
#6 ./smbd(yp_get_default_domain+0x8d) [0x8072451]
[2004/07/11 19:00:28, 0] lib/fault.c:fault_report(36)
================================================== =============
[2004/07/11 19:00:28, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 6 in pid 1640 (3.0.2a)
Please read the appendix Bugs of the Samba HOWTO collection
[2004/07/11 19:00:28, 0] lib/fault.c:fault_report(39)
================================================== =============
[2004/07/11 19:00:28, 0] lib/util.c:smb_panic(1400)
PANIC: internal error
[2004/07/11 19:00:28, 0] lib/util.c:smb_panic(140
BACKTRACE: 12 stack frames:
#0 ./smbd(smb_panic+0x181) [0x8184a31]
#1 ./smbd [0x81751ea]
#2 ./smbd [0x817523f]
#3 /lib/libc.so.6 [0x401e8988]
#4 /lib/libc.so.6(abort+0x1a7) [0x401ea127]
#5 ./smbd(readdirname+0) [0x8184ae4]
#6 ./smbd(process_exists+0x6a) [0x8184730]
#7 ./smbd(pidfile_pid+0x8c) [0x8176c40]
#8 ./smbd(pidfile_create+0x35) [0x8176cc9]
#9 ./smbd(main+0x465) [0x81d0fbe]
#10 /lib/libc.so.6(__libc_start_main+0xc6) [0x401d4d06]
#11 ./smbd(yp_get_default_domain+0x8d) [0x8072451]

Thanks in advance
Bill

[Mystic_Slayer]

try to use "testparm smb.conf"

if the smb file is bad then testparm will give you a notice about it.

If it hasn't gave an error, then compile a new version of samba. 3.0.4 or later? Don't know which one is the latest stable version

[Angusby2]

Yes I have run "testparm smb.conf" without error, I stripped the config down to a minimum, again with no success. I guess my next step is to upgrade as you suggest.

Thanks
Bill

[Mystic_Slayer]

Sure, no problem.