FS#50728 - [samba] 4.5.0-1 - smbd unable to start

Attached to Project: Arch Linux
Opened by Leryan (Leryan) - Saturday, 10 September 2016, 13:22 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 11 September 2016, 18:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 14
Private No

Details

Description:

Unable to start smbd after recent upgrade to samba 4.5.0.

Steps to reproduce:

* Start smbd with the default configuration file

sept. 10 13:17:23 vm-archlinux smbd[6745]: [2016/09/10 13:17:23.014531, 0] ../lib/util/fault.c:78(fault_report)
sept. 10 13:17:23 vm-archlinux smbd[6745]: ===============================================================
sept. 10 13:17:23 vm-archlinux smbd[6745]: [2016/09/10 13:17:23.014563, 0] ../lib/util/fault.c:79(fault_report)
sept. 10 13:17:23 vm-archlinux smbd[6745]: INTERNAL ERROR: Signal 11 in pid 6745 (4.5.0)
sept. 10 13:17:23 vm-archlinux smbd[6745]: Please read the Trouble-Shooting section of the Samba HOWTO
sept. 10 13:17:23 vm-archlinux smbd[6745]: [2016/09/10 13:17:23.014575, 0] ../lib/util/fault.c:81(fault_report)
sept. 10 13:17:23 vm-archlinux smbd[6745]: ===============================================================
sept. 10 13:17:23 vm-archlinux smbd[6745]: [2016/09/10 13:17:23.014582, 0] ../source3/lib/util.c:791(smb_panic_s3)
sept. 10 13:17:23 vm-archlinux smbd[6745]: PANIC (pid 6745): internal error
sept. 10 13:17:23 vm-archlinux smbd[6745]: [2016/09/10 13:17:23.015052, 0] ../source3/lib/util.c:902(log_stack_trace
)
sept. 10 13:17:23 vm-archlinux smbd[6745]: BACKTRACE: 14 stack frames:
sept. 10 13:17:23 vm-archlinux smbd[6745]: #0 /usr/lib/libsmbconf.so.0(log_stack_trace+0x1c) [0x7f27a549ff2c]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #1 /usr/lib/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f27a54a0000]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #2 /usr/lib/libsamba-util.so.0(smb_panic+0x2f) [0x7f27a798486f]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #3 /usr/lib/libsamba-util.so.0(+0x1ba86) [0x7f27a7984a86]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #4 /usr/lib/libpthread.so.0(+0x11080) [0x7f27a7bef080]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #5 /usr/lib/libtevent.so.0(tevent_debug+0x56) [0x7f27a3ee8426]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #6 /usr/lib/libtevent.so.0(tevent_common_loop_timer_delay+0xba) [0x7f27
a3eec9fa]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #7 /usr/lib/libsmbconf.so.0(run_events_poll+0x1a9) [0x7f27a54b7969]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #8 /usr/lib/libsmbconf.so.0(+0x36b07) [0x7f27a54b7b07]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #9 /usr/lib/libtevent.so.0(_tevent_loop_once+0x9d) [0x7f27a3ee7fdd]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #10 /usr/lib/libtevent.so.0(tevent_req_poll+0x23) [0x7f27a3ee9343]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #11 /usr/bin/smbd(main+0x873) [0x55c19f08c6e3]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #12 /usr/lib/libc.so.6(__libc_start_main+0xf1) [0x7f27a3b65291]
sept. 10 13:17:23 vm-archlinux smbd[6745]: #13 /usr/bin/smbd(_start+0x2a) [0x55c19f08d75a]
sept. 10 13:17:23 vm-archlinux smbd[6745]: [2016/09/10 13:17:23.015117, 0] ../source3/lib/dumpcore.c:303(dump_core)
sept. 10 13:17:23 vm-archlinux smbd[6745]: dumping core in /var/log/samba/cores/smbd
sept. 10 13:17:23 vm-archlinux smbd[6745]:
sept. 10 13:17:23 vm-archlinux smbd[6746]: [2016/09/10 13:17:23.015298, 0] ../lib/util/fault.c:78(fault_report)
sept. 10 13:17:23 vm-archlinux smbd[6746]: ===============================================================
sept. 10 13:17:23 vm-archlinux smbd[6746]: [2016/09/10 13:17:23.015377, 0] ../lib/util/fault.c:79(fault_report)
sept. 10 13:17:23 vm-archlinux smbd[6746]: INTERNAL ERROR: Signal 11 in pid 6746 (4.5.0)
sept. 10 13:17:23 vm-archlinux smbd[6746]: Please read the Trouble-Shooting section of the Samba HOWTO
sept. 10 13:17:23 vm-archlinux smbd[6746]: [2016/09/10 13:17:23.015390, 0] ../lib/util/fault.c:81(fault_report)
sept. 10 13:17:23 vm-archlinux smbd[6746]: ===============================================================
sept. 10 13:17:23 vm-archlinux smbd[6746]: [2016/09/10 13:17:23.015397, 0] ../source3/lib/util.c:791(smb_panic_s3)
sept. 10 13:17:23 vm-archlinux smbd[6746]: PANIC (pid 6746): internal error
sept. 10 13:17:23 vm-archlinux smbd[6746]: [2016/09/10 13:17:23.016909, 0] ../source3/lib/util.c:902(log_stack_trace
)
sept. 10 13:17:23 vm-archlinux smbd[6746]: BACKTRACE: 5 stack frames:
sept. 10 13:17:23 vm-archlinux smbd[6746]: #0 /usr/lib/libsmbconf.so.0(log_stack_trace+0x1c) [0x7f27a549ff2c]
sept. 10 13:17:23 vm-archlinux smbd[6746]: #1 /usr/lib/libsmbconf.so.0(smb_panic_s3+0x20) [0x7f27a54a0000]
sept. 10 13:17:23 vm-archlinux smbd[6746]: #2 /usr/lib/libsamba-util.so.0(smb_panic+0x2f) [0x7f27a798486f]
sept. 10 13:17:23 vm-archlinux smbd[6746]: #3 /usr/lib/libsamba-util.so.0(+0x1ba86) [0x7f27a7984a86]
sept. 10 13:17:23 vm-archlinux smbd[6746]: #4 /usr/lib/libpthread.so.0(+0x11080) [0x7f27a7bef080]
sept. 10 13:17:23 vm-archlinux smbd[6746]: [2016/09/10 13:17:23.016952, 0] ../source3/lib/dumpcore.c:303(dump_core)
sept. 10 13:17:23 vm-archlinux smbd[6746]: dumping core in /var/log/samba/cores/smbd
sept. 10 13:17:23 vm-archlinux smbd[6746]:
sept. 10 13:17:23 vm-archlinux smbd[6744]: [2016/09/10 13:17:23.016969, 0] ../lib/util/become_daemon.c:124(daemon_re
ady)
sept. 10 13:17:23 vm-archlinux smbd[6744]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
sept. 10 13:17:23 vm-archlinux smbd[6750]: [2016/09/10 13:17:23.018384, 0] ../source3/printing/print_standard.c:69(s
td_pcap_cache_reload)
sept. 10 13:17:23 vm-archlinux smbd[6750]: Unable to open printcap file /etc/printcap for read!
sept. 10 13:17:23 vm-archlinux smbd[6744]: [2016/09/10 13:17:23.034728, 0] ../lib/util/fault.c:78(fault_report)
sept. 10 13:17:23 vm-archlinux smbd[6744]: ===============================================================
sept. 10 13:17:23 vm-archlinux smbd[6744]: [2016/09/10 13:17:23.034792, 0] ../lib/util/fault.c:79(fault_report)
sept. 10 13:17:23 vm-archlinux smbd[6744]: INTERNAL ERROR: Signal 11 in pid 6744 (4.5.0)
sept. 10 13:17:23 vm-archlinux smbd[6744]: Please read the Trouble-Shooting section of the Samba HOWTO
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 11 September 2016, 18:51 GMT
Reason for closing:  Fixed
Comment by Leryan (Leryan) - Saturday, 10 September 2016, 13:25 GMT
I failed the log, here is a correct one:

[2016/09/10 13:23:41.905376, 0] ../lib/util/fault.c:78(fault_report)
===============================================================
[2016/09/10 13:23:41.905408, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 6813 (4.5.0)
Please read the Trouble-Shooting section of the Samba HOWTO
[2016/09/10 13:23:41.905419, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2016/09/10 13:23:41.905427, 0] ../source3/lib/util.c:791(smb_panic_s3)
PANIC (pid 6813): internal error
[2016/09/10 13:23:41.905496, 0] ../lib/util/fault.c:78(fault_report)
===============================================================
[2016/09/10 13:23:41.905533, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 6814 (4.5.0)
Please read the Trouble-Shooting section of the Samba HOWTO
[2016/09/10 13:23:41.905545, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2016/09/10 13:23:41.905552, 0] ../source3/lib/util.c:791(smb_panic_s3)
PANIC (pid 6814): internal error
[2016/09/10 13:23:41.905799, 0] ../source3/lib/util.c:902(log_stack_trace)
BACKTRACE: 14 stack frames:
#0 /usr/lib/libsmbconf.so.0(log_stack_trace+0x1c) [0x7fc4ea0def2c]
#1 /usr/lib/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fc4ea0df000]
#2 /usr/lib/libsamba-util.so.0(smb_panic+0x2f) [0x7fc4ec5c386f]
#3 /usr/lib/libsamba-util.so.0(+0x1ba86) [0x7fc4ec5c3a86]
#4 /usr/lib/libpthread.so.0(+0x11080) [0x7fc4ec82e080]
#5 /usr/lib/libtevent.so.0(tevent_debug+0x56) [0x7fc4e8b27426]
#6 /usr/lib/libtevent.so.0(tevent_common_loop_timer_delay+0xba) [0x7fc4e8b2b9fa]
#7 /usr/lib/libsmbconf.so.0(run_events_poll+0x1a9) [0x7fc4ea0f6969]
#8 /usr/lib/libsmbconf.so.0(+0x36b07) [0x7fc4ea0f6b07]
#9 /usr/lib/libtevent.so.0(_tevent_loop_once+0x9d) [0x7fc4e8b26fdd]
#10 /usr/lib/libtevent.so.0(tevent_req_poll+0x23) [0x7fc4e8b28343]
#11 /usr/bin/smbd(main+0x873) [0x560e29e076e3]
#12 /usr/lib/libc.so.6(__libc_start_main+0xf1) [0x7fc4e87a4291]
#13 /usr/bin/smbd(_start+0x2a) [0x560e29e0875a]
[2016/09/10 13:23:41.905859, 0] ../source3/lib/util.c:902(log_stack_trace)
BACKTRACE: 5 stack frames:
[2016/09/10 13:23:41.905871, 0] ../source3/lib/dumpcore.c:303(dump_core)
#0 /usr/lib/libsmbconf.so.0(log_stack_trace+0x1c) [0x7fc4ea0def2c]
dumping core in /var/log/samba/cores/smbd
#1 /usr/lib/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fc4ea0df000]
#2 /usr/lib/libsamba-util.so.0(smb_panic+0x2f) [0x7fc4ec5c386f]
#3 /usr/lib/libsamba-util.so.0(+0x1ba86) [0x7fc4ec5c3a86]
#4 /usr/lib/libpthread.so.0(+0x11080) [0x7fc4ec82e080]
[2016/09/10 13:23:41.905898, 0] ../source3/lib/dumpcore.c:303(dump_core)
dumping core in /var/log/samba/cores/smbd
[2016/09/10 13:23:41.909689, 0] ../lib/util/become_daemon.c:124(daemon_ready)
STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2016/09/10 13:23:41.910466, 0] ../source3/printing/print_standard.c:69(std_pcap_cache_reload)
Unable to open printcap file /etc/printcap for read!
[2016/09/10 13:23:41.913756, 0] ../lib/util/fault.c:78(fault_report)
===============================================================
[2016/09/10 13:23:41.913986, 0] ../lib/util/fault.c:79(fault_report)
INTERNAL ERROR: Signal 11 in pid 6812 (4.5.0)
Please read the Trouble-Shooting section of the Samba HOWTO
[2016/09/10 13:23:41.914193, 0] ../lib/util/fault.c:81(fault_report)
===============================================================
[2016/09/10 13:23:41.914327, 0] ../source3/lib/util.c:791(smb_panic_s3)
PANIC (pid 6812): internal error
[2016/09/10 13:23:41.914672, 0] ../source3/lib/util.c:902(log_stack_trace)
BACKTRACE: 19 stack frames:
#0 /usr/lib/libsmbconf.so.0(log_stack_trace+0x1c) [0x7fc4ea0def2c]
#1 /usr/lib/libsmbconf.so.0(smb_panic_s3+0x20) [0x7fc4ea0df000]
#2 /usr/lib/libsamba-util.so.0(smb_panic+0x2f) [0x7fc4ec5c386f]
#3 /usr/lib/libsamba-util.so.0(+0x1ba86) [0x7fc4ec5c3a86]
#4 /usr/lib/libpthread.so.0(+0x11080) [0x7fc4ec82e080]
#5 /usr/lib/libtevent.so.0(tevent_timeval_compare+0) [0x7fc4e8b2b5b0]
#6 /usr/lib/libtevent.so.0(+0x9761) [0x7fc4e8b2b761]
#7 /usr/lib/libtevent.so.0(tevent_common_add_timer+0x13) [0x7fc4e8b2b913]
#8 /usr/lib/libtevent.so.0(tevent_req_set_endtime+0x60) [0x7fc4e8b28410]
#9 /usr/lib/libtevent.so.0(tevent_wakeup_send+0x55) [0x7fc4e8b2bcb5]
#10 /usr/bin/smbd(+0x8f49) [0x560e29e09f49]
#11 /usr/lib/libtevent.so.0(tevent_common_check_signal+0x278) [0x7fc4e8b2af68]
#12 /usr/lib/libsmbconf.so.0(run_events_poll+0x24) [0x7fc4ea0f67e4]
#13 /usr/lib/libsmbconf.so.0(+0x36ba7) [0x7fc4ea0f6ba7]
#14 /usr/lib/libtevent.so.0(_tevent_loop_once+0x9d) [0x7fc4e8b26fdd]
#15 /usr/lib/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x7fc4e8b2720b]
#16 /usr/bin/smbd(main+0x15fa) [0x560e29e0846a]
#17 /usr/lib/libc.so.6(__libc_start_main+0xf1) [0x7fc4e87a4291]
#18 /usr/bin/smbd(_start+0x2a) [0x560e29e0875a]
[2016/09/10 13:23:41.916149, 0] ../source3/lib/dumpcore.c:303(dump_core)
dumping core in /var/log/samba/cores/smbd
Comment by Admoni Rotem (rotema8) - Saturday, 10 September 2016, 13:37 GMT
workaround downgrade tevnet
https://bbs.archlinux.org/viewtopic.php?id=216957
Comment by Bronek Kozicki (bronek) - Saturday, 10 September 2016, 20:32 GMT
I noticed the same in samba 4.4.5 package (not upgraded to 4.5.0 at the time). This happened after upgrade to tevent 0.9.30-1 , and was fixed when I downgraded to 0.9.29-1.

Comment by Leryan (Leryan) - Sunday, 11 September 2016, 11:21 GMT
Ok thanks, it works.

But, tevent is used only bay Samba, why the heck was it upgraded to a non compatible version?
Comment by emak (emak) - Sunday, 11 September 2016, 16:49 GMT
Thanks - having also the core dump problem and downgrading tevent (0.9.30-1 => 0.9.29-1) resolved the issue.
Comment by Tobias Powalowski (tpowa) - Sunday, 11 September 2016, 18:51 GMT
Tevent downgraded in extra to 0.9.29-2, all should be fine now.

Loading...