Samba36 core dumping
Dave
freebsd01 at dgmm.net
Mon Feb 6 02:44:02 UTC 2017
Anyone else had this samba core dump error and fixed it?
I just did a rebuild of samba36 and all the related build/run depends ports followed by a service samba restart
If it's just me with the problem is there enough below to point me in the right direction to fix it?
uname -a
FreeBSD server.asgard.uk 10.3-RELEASE-p11 FreeBSD 10.3-RELEASE-p11 #0: Mon Oct 24 18:49:24 UTC 2016 root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
server:/var/log/samba %tail -F log.smbd
[2017/02/06 02:12:55.416399, 0] lib/fault.c:51(fault_report)
===============================================================
[2017/02/06 02:12:55.416493, 0] lib/fault.c:52(fault_report)
INTERNAL ERROR: Signal 10 in pid 13545 (3.6.25)
Please read the Trouble-Shooting section of the Samba3-HOWTO
[2017/02/06 02:12:55.416546, 0] lib/fault.c:54(fault_report)
From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
[2017/02/06 02:12:55.416716, 0] lib/fault.c:55(fault_report)
===============================================================
[2017/02/06 02:12:55.416826, 0] lib/util.c:1117(smb_panic)
PANIC (pid 13545): internal error
[2017/02/06 02:12:55.434707, 0] lib/util.c:1221(log_stack_trace)
BACKTRACE: 5 stack frames:
#0 0x14087a8 <log_stack_trace+0x28> at /usr/local/sbin/smbd
#1 0x14080b2 <smb_panic+0x52> at /usr/local/sbin/smbd
#2 0x13f9050 <fault_setup+0x190> at /usr/local/sbin/smbd
#3 0x802de0b4a <pthread_sigmask+0x51a> at /lib/libthr.so.3
#4 0x802de022c <pthread_getspecific+0xe1c> at /lib/libthr.so.3
[2017/02/06 02:12:55.434948, 0] lib/fault.c:416(dump_core)
dumping core in /var/log/samba/cores/smbd
More information about the freebsd-questions
mailing list