Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Jan 2017 19:12:48 +0000
From:      Gerard Seibert <carmel_ny@outlook.com>
To:        FreeBSD Ports <freebsd-ports@freebsd.org>, "timur@FreeBSD.org" <timur@FreeBSD.org>
Subject:   samba43 failing to start
Message-ID:  <CY4PR20MB13971B819DB30C2B272D594380660@CY4PR20MB1397.namprd20.prod.outlook.com>

next in thread | raw e-mail | index | archive | help
After failing to update samba43, samba is now refusing to start. These
are the messages logged:

/var/log/samba4 $ more log.nmbd
[2017/01/11 14:03:21.873888,
0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=3Ddaemon 'nmbd'
finished starting up and ready to serve connections [2017/01/11
14:03:21.874960,  0] ../lib/util/fault.c:78(fault_report)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[2017/01/11 14:03:21.875426,  0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 38314 (4.3.11) Please read the
Trouble-Shooting section of the Samba HOWTO [2017/01/11
14:03:21.875728,  0] ../lib/util/fault.c:81(fault_report)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[2017/01/11 14:03:21.875846,
0] ../source3/lib/util.c:789(smb_panic_s3) PANIC (pid 38314): internal
error [2017/01/11 14:03:21.877403,
0] ../source3/lib/util.c:900(log_stack_trace) BACKTRACE: 7 stack
frames: #0 0x802348a6e <log_stack_trace+0x1e>
at /usr/local/lib/libsmbconf.so.0 #1 0x802348868 <smb_panic_s3+0x98>
at /usr/local/lib/libsmbconf.so.0 #2 0x8018d1d57 <smb_panic+0x27>
at /usr/local/lib/libsamba-util.so.0 #3 0x8018d2300 <string_sub_once>
at /usr/local/lib/libsamba-util.so.0 #4 0x8018d1d23 <fault_setup+0x73>
at /usr/local/lib/libsamba-util.so.0 #5 0x80149ddcf
<pthread_sigmask+0x4ff> at /lib/libthr.so.3 #6 0x80149d3af
<pthread_getspecific+0xdbf> at /lib/libthr.so.3 [2017/01/11
14:03:21.877911,  0] ../source3/lib/dumpcore.c:298(dump_core) unable to
change to %N.core refusing to dump core ...skipping...
[2017/01/11 14:03:21.873888,
0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=3Ddaemon 'nmbd'
finished starting up and ready to serve connections [2017/01/11
14:03:21.874960,  0] ../lib/util/fault.c:78(fault_report)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[2017/01/11 14:03:21.875426,  0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 38314 (4.3.11) Please read the
Trouble-Shooting section of the Samba HOWTO [2017/01/11
14:03:21.875728,  0] ../lib/util/fault.c:81(fault_report)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
[2017/01/11 14:03:21.875846,
0] ../source3/lib/util.c:789(smb_panic_s3) PANIC (pid 38314): internal
error [2017/01/11 14:03:21.877403,
0] ../source3/lib/util.c:900(log_stack_trace) BACKTRACE: 7 stack
frames: #0 0x802348a6e <log_stack_trace+0x1e>
at /usr/local/lib/libsmbconf.so.0 #1 0x802348868 <smb_panic_s3+0x98>
at /usr/local/lib/libsmbconf.so.0 #2 0x8018d1d57 <smb_panic+0x27>
at /usr/local/lib/libsamba-util.so.0 #3 0x8018d2300 <string_sub_once>
at /usr/local/lib/libsamba-util.so.0 #4 0x8018d1d23 <fault_setup+0x73>
at /usr/local/lib/libsamba-util.so.0 #5 0x80149ddcf
<pthread_sigmask+0x4ff> at /lib/libthr.so.3 #6 0x80149d3af
<pthread_getspecific+0xdbf> at /lib/libthr.so.3 [2017/01/11
14:03:21.877911,  0] ../source3/lib/dumpcore.c:298(dump_core) unable to
change to %N.core refusing to dump core

/var/log/samba4 $ more log.smbd
[2017/01/11 14:03:22.018101,
0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=3Ddaemon 'smbd'
finished starting up and ready to serve connections

Since samba43 worked fine before, and since the update failed, I do not
understand why this is happening or how to correct it.

--=20
Carmel



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CY4PR20MB13971B819DB30C2B272D594380660>