[Samba] locking smbd
Sascha Willuweit
sascha.willuweit at me.com
Wed Feb 12 03:07:52 MST 2014
dear all,
i'm running samba4 (4.0.x) on FreeBSD 9.2 and stuck at leas once a week with the following smbd fault (taken fom /var/log/messages):
Feb 12 10:37:56 mercury smbd[5960]: [2014/02/12 10:37:56.344706, 0, pid=5960, effective(3000028, 20), real(0, 0)] ../lib/util/fault.c:72(fault_report)
Feb 12 10:37:56 mercury smbd[5960]: ===============================================================
Feb 12 10:37:56 mercury smbd[5960]: [2014/02/12 10:37:56.344789, 0, pid=5960, effective(3000028, 20), real(0, 0)] ../lib/util/fault.c:73(fault_report)
Feb 12 10:37:56 mercury smbd[5960]: INTERNAL ERROR: Signal 11 in pid 5960 (4.0.14)
Feb 12 10:37:56 mercury smbd[5960]: Please read the Trouble-Shooting section of the Samba HOWTO
Feb 12 10:37:56 mercury smbd[5960]: [2014/02/12 10:37:56.344839, 0, pid=5960, effective(3000028, 20), real(0, 0)] ../lib/util/fault.c:75(fault_report)
Feb 12 10:37:56 mercury smbd[5960]: ===============================================================
Feb 12 10:37:56 mercury smbd[5960]: [2014/02/12 10:37:56.344878, 0, pid=5960, effective(3000028, 20), real(0, 0)] ../source3/lib/util.c:810(smb_panic_s3)
Feb 12 10:37:56 mercury smbd[5960]: PANIC (pid 5960): internal error
Feb 12 10:37:56 mercury smbd[5960]: [2014/02/12 10:37:56.345361, 0, pid=5960, effective(3000028, 20), real(0, 0)] ../source3/lib/util.c:921(log_stack_trace)
Feb 12 10:37:56 mercury smbd[5960]: BACKTRACE: 24 stack frames:
Feb 12 10:37:56 mercury smbd[5960]: #0 0x82945ecd <smb_panic_s3+45> at /usr/local/lib/libsmbconf.so.0
Feb 12 10:37:56 mercury smbd[5960]: #1 0x81462a3c <smb_panic+44> at /usr/local/lib/libsamba-util.so.0
Feb 12 10:37:56 mercury smbd[5960]: #2 0x81462c51 <smb_panic+577> at /usr/local/lib/libsamba-util.so.0
Feb 12 10:37:56 mercury smbd[5960]: #3 0x83f8e349 <pthread_sigmask+889> at /lib/libthr.so.3
Feb 12 10:37:56 mercury smbd[5960]: #4 0x83f8e579 <pthread_sigmask+1449> at /lib/libthr.so.3
Feb 12 10:37:56 mercury smbd[5960]: #5 0x7ffffffff003
Feb 12 10:37:56 mercury smbd[5960]: #6 0x83d7c354 <talloc_named_const+116> at /usr/local/lib/libtalloc.so.2
Feb 12 10:37:56 mercury smbd[5960]: #7 0x841acdaf <tevent_timeval_add+415> at /usr/local/lib/libtevent.so.0
Feb 12 10:37:56 mercury smbd[5960]: #8 0x841acfae <tevent_common_add_timer+46> at /usr/local/lib/libtevent.so.0
Feb 12 10:37:56 mercury smbd[5960]: #9 0x817ade0b <smbd_smb2_request_pending_queue+1355> at /usr/local/lib/samba/libsmbd_base.so
Feb 12 10:37:56 mercury smbd[5960]: #10 0x817bb776 <smbd_smb2_request_process_notify+822> at /usr/local/lib/samba/libsmbd_base.so
Feb 12 10:37:56 mercury smbd[5960]: #11 0x817aaf7d <smbd_smb2_request_dispatch+2285> at /usr/local/lib/samba/libsmbd_base.so
Feb 12 10:37:56 mercury smbd[5960]: #12 0x817abf56 <smbd_smb2_request_dispatch+6342> at /usr/local/lib/samba/libsmbd_base.so
Feb 12 10:37:56 mercury smbd[5960]: #13 0x817ac1b6 <smbd_smb2_request_dispatch+6950> at /usr/local/lib/samba/libsmbd_base.so
Feb 12 10:37:56 mercury smbd[5960]: #14 0x8295a6f8 <run_events_poll+632> at /usr/local/lib/libsmbconf.so.0
Feb 12 10:37:56 mercury smbd[5960]: #15 0x8295ab31 <event_add_to_poll_args+929> at /usr/local/lib/libsmbconf.so.0
Feb 12 10:37:56 mercury smbd[5960]: #16 0x841a8d41 <_tevent_loop_once+145> at /usr/local/lib/libtevent.so.0
Feb 12 10:37:56 mercury smbd[5960]: #17 0x81796c83 <smbd_process+2723> at /usr/local/lib/samba/libsmbd_base.so
Feb 12 10:37:56 mercury smbd[5960]: #18 0x10298d2 <start_lsasd+8914> at /usr/local/sbin/smbd
Feb 12 10:37:56 mercury smbd[5960]: #19 0x8295a6f8 <run_events_poll+632> at /usr/local/lib/libsmbconf.so.0
Feb 12 10:37:56 mercury smbd[5960]: #21 0x841a8d41 <_tevent_loop_once+145> at /usr/local/lib/libtevent.so.0
Feb 12 10:37:56 mercury smbd[5960]: [2014/02/12 10:37:56.345911, 0, pid=5960, effective(0, 0), real(0, 0)] ../source3/lib/dumpcore.c:317(dump_core)
Feb 12 10:37:56 mercury smbd[5960]: dumping core in /var/coredumps
Feb 12 10:37:56 mercury smbd[5960]:
Can someone please guide me how to troubleshoot this one? I really appreciate any advise.
Thanks,
Sascha
More information about the samba
mailing list