[Samba] samba4.0.16 smbd internal error

[Marc Muehlfeld]

Hello Sascha,

Am 24.03.2014 18:29, schrieb Sascha Willuweit:
>    ===============================================================
> [2014/03/24 13:28:49.787910,  0, pid=13041, effective(3000026, 20),
> real(0, 0)] ../lib/util/fault.c:73(fault_report)
>    INTERNAL ERROR: Signal 11 in pid 13041 (4.0.16)
>    Please read the Trouble-Shooting section of the Samba HOWTO
> [2014/03/24 13:28:49.787957,  0, pid=13041, effective(3000026, 20),
> real(0, 0)] ../lib/util/fault.c:75(fault_report)
>    ===============================================================
> [2014/03/24 13:28:49.787988,  0, pid=13041, effective(3000026, 20),
> real(0, 0)] ../source3/lib/util.c:810(smb_panic_s3)
>    PANIC (pid 13041): internal error
> [2014/03/24 13:28:49.788592,  0, pid=13041, effective(3000026, 20),
> real(0, 0)] ../source3/lib/util.c:921(log_stack_trace)
>    BACKTRACE: 24 stack frames:
>     #0 0x828ed192 <smb_panic_s3+82> at /usr/local/lib/libsmbconf.so.0
>     #1 0x8146290b <smb_panic+315> at /usr/local/lib/libsamba-util.so.0
>     #2 0x814627b7 <fault_setup+343> at /usr/local/lib/libsamba-util.so.0
>     #3 0x83ed640b <_swapcontext+347> at /lib/libthr.so.3
>     #4 0x83ed5ff3 <sigaction+835> at /lib/libthr.so.3
>     #5 0x7ffffffff193
>     #6 0x83cc1293 <talloc_named_const+19> at /usr/local/lib/libtalloc.so.2
>     #7 0x840f54ea <tevent_common_add_timer+106> at
> /usr/local/lib/libtevent.so.0
>     #8 0x840f54a6 <tevent_common_add_timer+38> at
> /usr/local/lib/libtevent.so.0
>     #9 0x81798576 <smbd_smb2_request_pending_queue+2166> at
> /usr/local/lib/samba/libsmbd_base.so
>     #10 0x817a9320 <smbd_smb2_request_process_notify+816> at
> /usr/local/lib/samba/libsmbd_base.so
>     #11 0x81799e47 <smbd_smb2_request_dispatch+3127> at
> /usr/local/lib/samba/libsmbd_base.so
>     #12 0x8179b89d <smbd_smb2_send_oplock_break+3309> at
> /usr/local/lib/samba/libsmbd_base.so
>     #13 0x8179cda8 <smbd_smb2_first_negprot+5192> at
> /usr/local/lib/samba/libsmbd_base.so
>     #14 0x829012cc <run_events_poll+684> at /usr/local/lib/libsmbconf.so.0
>     #15 0x82901b0d <event_add_idle+1309> at /usr/local/lib/libsmbconf.so.0
>     #16 0x840f1602 <_tevent_loop_once+114> at /usr/local/lib/libtevent.so.0
>     #17 0x81786cd1 <smbd_process+1969> at
> /usr/local/lib/samba/libsmbd_base.so
>     #18 0x102b20e <main+9294> at /usr/local/sbin/smbd
>     #19 0x829012cc <run_events_poll+684> at /usr/local/lib/libsmbconf.so.0
>     #20 0x82901b0d <event_add_idle+1309> at /usr/local/lib/libsmbconf.so.0
>     #21 0x840f1602 <_tevent_loop_once+114> at /usr/local/lib/libtevent.so.0
>     #22 0x102a241 <main+5249> at /usr/local/sbin/smbd
>     #23 0x1026d13 <_start+419> at /usr/local/sbin/smbd
> [2014/03/24 13:28:49.789014,  0, pid=13041, effective(0, 0), real(0, 0)]
> ../source3/lib/dumpcore.c:317(dump_core)
>    dumping core in /var/coredumps


Such crashes should never happen. Do you know what caused that?

Can you file a bug report with level 10 debug logs and backtrace?
https://www.samba.org/~asn/reporting_samba_bugs.txt


Regards,
Marc