[SOLVED] Samba 4.5.0 upgrade broke samba

[nickarchpi2]

I upgraded samba-4.4.5-2-armv7h.pkg.tar.xz to samba-4.5.0-1-armv7h.pkg.tar.xz
and smbclient-4.4.5-2-armv7h.pkg.tar.xz to smbclient-4.5.0-1-armv7h.pkg.tar.xz

It has caused samba to fail to load with the following errors in log files.

$this->bbcode_second_pass_code('', '$ journalctl -p 3 -xb
Sep 10 12:43:17 arch kernel: smsc95xx 1-1.1:1.0 eth0: kevent 4 may have been dropped
Sep 10 12:43:17 arch kernel: smsc95xx 1-1.1:1.0 eth0: kevent 4 may have been dropped
Sep 10 12:43:17 arch kernel: smsc95xx 1-1.1:1.0 eth0: kevent 4 may have been dropped
Sep 10 12:43:17 arch smbd[299]: [2016/09/10 12:43:17.777501, 0] ../lib/util/fault.c:78(fault_report)
Sep 10 12:43:17 arch smbd[299]: ===============================================================
Sep 10 12:43:17 arch smbd[299]: [2016/09/10 12:43:17.818751, 0] ../lib/util/fault.c:79(fault_report)
Sep 10 12:43:17 arch smbd[299]: INTERNAL ERROR: Signal 11 in pid 299 (4.5.0)
Sep 10 12:43:17 arch smbd[299]: Please read the Trouble-Shooting section of the Samba HOWTO
Sep 10 12:43:17 arch smbd[299]: [2016/09/10 12:43:17.819058, 0] ../lib/util/fault.c:81(fault_report)
Sep 10 12:43:17 arch smbd[299]: ===============================================================
Sep 10 12:43:17 arch smbd[299]: [2016/09/10 12:43:17.819222, 0] ../source3/lib/util.c:791(smb_panic_s3)
Sep 10 12:43:17 arch smbd[299]: PANIC (pid 299): internal error
Sep 10 12:43:17 arch smbd[299]: [2016/09/10 12:43:17.820040, 0] ../source3/lib/util.c:902(log_stack_trace)
Sep 10 12:43:17 arch smbd[299]: BACKTRACE: 0 stack frames:
Sep 10 12:43:17 arch smbd[299]: [2016/09/10 12:43:17.820372, 0] ../source3/lib/dumpcore.c:303(dump_core)
Sep 10 12:43:17 arch smbd[299]: dumping core in /var/log/samba/cores/smbd
Sep 10 12:43:17 arch smbd[299]:
Sep 10 12:43:17 arch smbd[298]: [2016/09/10 12:43:17.846080, 0] ../lib/util/fault.c:78(fault_report)
Sep 10 12:43:17 arch smbd[298]: ===============================================================
Sep 10 12:43:17 arch smbd[298]: [2016/09/10 12:43:17.846684, 0] ../lib/util/fault.c:79(fault_report)
Sep 10 12:43:17 arch smbd[298]: INTERNAL ERROR: Signal 11 in pid 298 (4.5.0)
Sep 10 12:43:17 arch smbd[298]: Please read the Trouble-Shooting section of the Samba HOWTO
Sep 10 12:43:17 arch smbd[298]: [2016/09/10 12:43:17.847007, 0] ../lib/util/fault.c:81(fault_report)
Sep 10 12:43:17 arch smbd[298]: ===============================================================
Sep 10 12:43:17 arch smbd[298]: [2016/09/10 12:43:17.847170, 0] ../source3/lib/util.c:791(smb_panic_s3)
Sep 10 12:43:17 arch smbd[298]: PANIC (pid 298): internal error
Sep 10 12:43:17 arch smbd[298]: [2016/09/10 12:43:17.848061, 0] ../source3/lib/util.c:902(log_stack_trace)
Sep 10 12:43:17 arch smbd[298]: BACKTRACE: 0 stack frames:
Sep 10 12:43:17 arch smbd[298]: [2016/09/10 12:43:17.848429, 0] ../source3/lib/dumpcore.c:303(dump_core)
Sep 10 12:43:17 arch smbd[298]: dumping core in /var/log/samba/cores/smbd
Sep 10 12:43:17 arch smbd[298]:
Sep 10 12:43:18 arch smbd[296]: [2016/09/10 12:43:18.105648, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Sep 10 12:43:18 arch smbd[296]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Sep 10 12:43:18 arch smbd[296]: [2016/09/10 12:43:18.174735, 0] ../lib/util/fault.c:78(fault_report)
Sep 10 12:43:18 arch smbd[296]: ===============================================================
Sep 10 12:43:18 arch smbd[296]: [2016/09/10 12:43:18.175231, 0] ../lib/util/fault.c:79(fault_report)
Sep 10 12:43:18 arch smbd[296]: INTERNAL ERROR: Signal 11 in pid 296 (4.5.0)
Sep 10 12:43:18 arch smbd[296]: Please read the Trouble-Shooting section of the Samba HOWTO
Sep 10 12:43:18 arch smbd[296]: [2016/09/10 12:43:18.175512, 0] ../lib/util/fault.c:81(fault_report)
Sep 10 12:43:18 arch smbd[296]: ===============================================================
Sep 10 12:43:18 arch smbd[296]: [2016/09/10 12:43:18.175699, 0] ../source3/lib/util.c:791(smb_panic_s3)
Sep 10 12:43:18 arch smbd[296]: PANIC (pid 296): internal error
Sep 10 12:43:18 arch smbd[296]: [2016/09/10 12:43:18.176307, 0] ../source3/lib/util.c:902(log_stack_trace)
Sep 10 12:43:18 arch smbd[296]: BACKTRACE: 0 stack frames:
Sep 10 12:43:18 arch smbd[296]: [2016/09/10 12:43:18.176731, 0] ../source3/lib/dumpcore.c:303(dump_core)
Sep 10 12:43:18 arch smbd[296]: dumping core in /var/log/samba/cores/smbd
Sep 10 12:43:18 arch smbd[296]:
Sep 10 12:43:18 arch smbd[313]: [2016/09/10 12:43:18.241520, 0] ../lib/util/fault.c:78(fault_report)
Sep 10 12:43:18 arch smbd[313]: ===============================================================
Sep 10 12:43:18 arch smbd[313]: [2016/09/10 12:43:18.247130, 0] ../lib/util/fault.c:79(fault_report)
Sep 10 12:43:18 arch smbd[313]: INTERNAL ERROR: Signal 11 in pid 313 (4.5.0)
Sep 10 12:43:18 arch smbd[313]: Please read the Trouble-Shooting section of the Samba HOWTO
Sep 10 12:43:18 arch smbd[313]: [2016/09/10 12:43:18.250747, 0] ../lib/util/fault.c:81(fault_report)
Sep 10 12:43:18 arch smbd[313]: ===============================================================
Sep 10 12:43:18 arch smbd[313]: [2016/09/10 12:43:18.251313, 0] ../source3/lib/util.c:791(smb_panic_s3)
Sep 10 12:43:18 arch smbd[313]: PANIC (pid 313): internal error
Sep 10 12:43:18 arch smbd[313]: [2016/09/10 12:43:18.252364, 0] ../source3/lib/util.c:902(log_stack_trace)
Sep 10 12:43:18 arch smbd[313]: BACKTRACE: 0 stack frames:
Sep 10 12:43:18 arch smbd[313]: [2016/09/10 12:43:18.252809, 0] ../source3/lib/dumpcore.c:303(dump_core)
Sep 10 12:43:18 arch smbd[313]: dumping core in /var/log/samba/cores/smbd
Sep 10 12:43:18 arch smbd[313]:
Sep 10 12:43:19 arch systemd[1]: Timed out waiting for device dev-sda.device.
Sep 10 12:43:20 arch systemd-coredump[316]: Process 296 (smbd) of user 0 dumped core.
Sep 10 12:43:20 arch systemd-coredump[310]: Process 298 (smbd-notifyd) of user 0 dumped core.
Sep 10 12:43:20 arch systemd-coredump[309]: Process 299 (cleanupd) of user 0 dumped core.
Sep 10 12:43:20 arch systemd-coredump[321]: Process 313 (lpqd) of user 0 dumped core.')

$this->bbcode_second_pass_code('', '$ systemctl status samba.service
● samba.service - Samba AD Daemon
Loaded: loaded (/usr/lib/systemd/system/samba.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sat 2016-09-10 12:54:48 BST; 24s ago
Process: 489 ExecStart=/usr/bin/samba $SAMBAOPTIONS (code=exited, status=0/SUCCESS)
Main PID: 491 (code=exited, status=1/FAILURE)

Sep 10 12:54:48 arch systemd[1]: Started Samba AD Daemon.
Sep 10 12:54:48 arch samba[491]: [2016/09/10 12:54:48.847753, 0] ../source4/smbd/server.c:466(binary_smbd_main)
Sep 10 12:54:48 arch samba[491]: At this time the 'samba' binary should only be used for either:
Sep 10 12:54:48 arch samba[491]: 'server role = active directory domain controller' or to access the ntvfs file server with 'server services = +smb' or the
Sep 10 12:54:48 arch samba[491]: You should start smbd/nmbd/winbindd instead for domain member and standalone file server tasks
Sep 10 12:54:48 arch samba[491]: [2016/09/10 12:54:48.848839, 0] ../lib/util/become_daemon.c:111(exit_daemon)
Sep 10 12:54:48 arch samba[491]: STATUS=daemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for details, error code 22
Sep 10 12:54:48 arch systemd[1]: samba.service: Main process exited, code=exited, status=1/FAILURE
Sep 10 12:54:48 arch systemd[1]: samba.service: Unit entered failed state.
Sep 10 12:54:48 arch systemd[1]: samba.service: Failed with result 'exit-code'.')

I have ran the following to downgrade from the pacman cache
$this->bbcode_second_pass_code('', '$ sudo pacman -U samba-4.4.5-2-armv7h.pkg.tar.xz smbclient-4.4.5-2-armv7h.pkg.tar.xz')

samba still fails.

I have also ran
$this->bbcode_second_pass_code('', '$ sudo pacman -Rs samba')
followed by
$this->bbcode_second_pass_code('', '$ sudo pacman -S samba')
to reinstall the package and deps but still not luck.

Any ideas what is causing the issue?

[WarheadsSE]

Unless you are actually trying to run a AD service, you should be directly starting smbd & nmbd instead of samba, unless you follow the configuration guidelines for samba, as also pointed out in the logs.

Try starting smbd directly, and once you have that functional, nmbd if you so desire.

[nickarchpi2]

That was an error on my part. I have disabled samba and enabled smbd.service now

I am still having issues, samba was working fine until I upgraded. Here are the logs since enabling only smbd.conf

$this->bbcode_second_pass_code('', '$ journalctl -p 3 -xb
Sep 10 15:30:54 arch smbd[463]: [2016/09/10 15:30:54.185304, 0] ../lib/util/fault.c:78(fault_report)
Sep 10 15:30:54 arch smbd[463]: ===============================================================
Sep 10 15:30:54 arch smbd[463]: [2016/09/10 15:30:54.195133, 0] ../lib/util/fault.c:79(fault_report)
Sep 10 15:30:54 arch smbd[463]: INTERNAL ERROR: Signal 11 in pid 463 (4.5.0)
Sep 10 15:30:54 arch smbd[463]: Please read the Trouble-Shooting section of the Samba HOWTO
Sep 10 15:30:54 arch smbd[463]: [2016/09/10 15:30:54.195485, 0] ../lib/util/fault.c:81(fault_report)
Sep 10 15:30:54 arch smbd[463]: ===============================================================
Sep 10 15:30:54 arch smbd[463]: [2016/09/10 15:30:54.195652, 0] ../source3/lib/util.c:791(smb_panic_s3)
Sep 10 15:30:54 arch smbd[463]: PANIC (pid 463): internal error
Sep 10 15:30:54 arch smbd[463]: [2016/09/10 15:30:54.196447, 0] ../source3/lib/util.c:902(log_stack_trace)
Sep 10 15:30:54 arch smbd[463]: BACKTRACE: 0 stack frames:
Sep 10 15:30:54 arch smbd[463]: [2016/09/10 15:30:54.196786, 0] ../source3/lib/dumpcore.c:303(dump_core)
Sep 10 15:30:54 arch smbd[463]: dumping core in /var/log/samba/cores/smbd
Sep 10 15:30:54 arch smbd[463]:
Sep 10 15:30:54 arch smbd[462]: [2016/09/10 15:30:54.199581, 0] ../lib/util/fault.c:78(fault_report)
Sep 10 15:30:54 arch smbd[462]: ===============================================================
Sep 10 15:30:54 arch smbd[462]: [2016/09/10 15:30:54.200068, 0] ../lib/util/fault.c:79(fault_report)
Sep 10 15:30:54 arch smbd[462]: INTERNAL ERROR: Signal 11 in pid 462 (4.5.0)
Sep 10 15:30:54 arch smbd[462]: Please read the Trouble-Shooting section of the Samba HOWTO
Sep 10 15:30:54 arch smbd[462]: [2016/09/10 15:30:54.200281, 0] ../lib/util/fault.c:81(fault_report)
Sep 10 15:30:54 arch smbd[462]: ===============================================================
Sep 10 15:30:54 arch smbd[462]: [2016/09/10 15:30:54.200456, 0] ../source3/lib/util.c:791(smb_panic_s3)
Sep 10 15:30:54 arch smbd[462]: PANIC (pid 462): internal error
Sep 10 15:30:54 arch smbd[462]: [2016/09/10 15:30:54.201177, 0] ../source3/lib/util.c:902(log_stack_trace)
Sep 10 15:30:54 arch smbd[462]: BACKTRACE: 0 stack frames:
Sep 10 15:30:54 arch smbd[462]: [2016/09/10 15:30:54.201475, 0] ../source3/lib/dumpcore.c:303(dump_core)
Sep 10 15:30:54 arch smbd[462]: dumping core in /var/log/samba/cores/smbd
Sep 10 15:30:54 arch smbd[462]:
Sep 10 15:30:54 arch smbd[461]: [2016/09/10 15:30:54.359879, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Sep 10 15:30:54 arch smbd[461]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Sep 10 15:30:54 arch smbd[461]: [2016/09/10 15:30:54.423680, 0] ../lib/util/fault.c:78(fault_report)
Sep 10 15:30:54 arch smbd[471]: [2016/09/10 15:30:54.426678, 0] ../lib/util/fault.c:78(fault_report)
Sep 10 15:30:54 arch smbd[461]: ===============================================================
Sep 10 15:30:54 arch smbd[461]: [2016/09/10 15:30:54.427539, 0] ../lib/util/fault.c:79(fault_report)
Sep 10 15:30:54 arch smbd[461]: INTERNAL ERROR: Signal 11 in pid 461 (4.5.0)
Sep 10 15:30:54 arch smbd[461]: Please read the Trouble-Shooting section of the Samba HOWTO
Sep 10 15:30:54 arch smbd[461]: [2016/09/10 15:30:54.428007, 0] ../lib/util/fault.c:81(fault_report)
Sep 10 15:30:54 arch smbd[461]: ===============================================================
Sep 10 15:30:54 arch smbd[461]: [2016/09/10 15:30:54.428287, 0] ../source3/lib/util.c:791(smb_panic_s3)
Sep 10 15:30:54 arch smbd[461]: PANIC (pid 461): internal error
Sep 10 15:30:54 arch smbd[461]: [2016/09/10 15:30:54.429073, 0] ../source3/lib/util.c:902(log_stack_trace)
Sep 10 15:30:54 arch smbd[461]: BACKTRACE: 0 stack frames:
Sep 10 15:30:54 arch smbd[461]: [2016/09/10 15:30:54.429556, 0] ../source3/lib/dumpcore.c:303(dump_core)
Sep 10 15:30:54 arch smbd[461]: dumping core in /var/log/samba/cores/smbd')

$this->bbcode_second_pass_code('', '$ systemctl status smbd.service
● smbd.service - Samba SMB/CIFS server
Loaded: loaded (/usr/lib/systemd/system/smbd.service; disabled; vendor preset: disabled)
Active: failed (Result: core-dump) since Sat 2016-09-10 15:30:54 BST; 3min 17s ago
Process: 459 ExecStart=/usr/bin/smbd -D (code=exited, status=0/SUCCESS)
Main PID: 461 (code=dumped, signal=ABRT)

Sep 10 15:30:54 arch smbd[471]: [2016/09/10 15:30:54.448261, 0] ../source3/lib/util.c:791(smb_panic_s3)
Sep 10 15:30:54 arch smbd[471]: PANIC (pid 471): internal error
Sep 10 15:30:54 arch smbd[471]: [2016/09/10 15:30:54.449624, 0] ../source3/lib/util.c:902(log_stack_trace)
Sep 10 15:30:54 arch smbd[471]: BACKTRACE: 0 stack frames:
Sep 10 15:30:54 arch smbd[471]: [2016/09/10 15:30:54.450564, 0] ../source3/lib/dumpcore.c:303(dump_core)
Sep 10 15:30:54 arch smbd[471]: dumping core in /var/log/samba/cores/smbd
Sep 10 15:30:54 arch smbd[471]:
Sep 10 15:30:54 arch systemd[1]: smbd.service: Main process exited, code=dumped, status=6/ABRT
Sep 10 15:30:54 arch systemd[1]: smbd.service: Unit entered failed state.
Sep 10 15:30:54 arch systemd[1]: smbd.service: Failed with result 'core-dump'.')

[Nesn]

tevent 0.9.30 is the culprit.

[moonman]

Known problem upstream: https://bugs.archlinux.org/task/50728
Downgrade to tevent 0.9.29
$this->bbcode_second_pass_code('', 'https://olegtown.pw/archlinuxarm-archive/packages/t/tevent/tevent-0.9.29-1-armv7h.pkg.tar.xz')

[nickarchpi2]

Thanks,

I've decided to use NFS instead of Samba as it seems to work better for serving media to Kodi and is also recommended by the Kodi team over samba.

[moonman]

This bug has now been fixed upstream so just update your system with pacman -Suuyy to allow downgrading packages. Samba works fine in Kodi too.