FS#33596 - [samba] nmbd and winbindd services timeout during startup
Attached to Project:
Arch Linux
Opened by Neil Darlow (neildarlow) - Sunday, 27 January 2013, 16:10 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 31 January 2013, 08:06 GMT
Opened by Neil Darlow (neildarlow) - Sunday, 27 January 2013, 16:10 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 31 January 2013, 08:06 GMT
|
Details
Description:
I use smbd/winbindd to provide centralised authentication and uid/gid mapping for several KVM guests. Following an upgrade of samba/libwbclient from 3.6.10 to 3.6.11 this all stopped working. Examining the processes with systemctl status I found that nmbd and winbindd are failing to start due to timeout and they enter a failed state. Additional info: * samba-3.6.11-1 Steps to reproduce: 1) Upgrade working samba-3.6.10 installation to samba-3.6.11 and reboot 2) Notice that systemctl status {nmbd,winbindd} report timeout and entering failed state 3) nmbd and winbindd processes do not exist |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Thursday, 31 January 2013, 08:06 GMT
Reason for closing: Fixed
Additional comments about closing: 3.6.12-1
Thursday, 31 January 2013, 08:06 GMT
Reason for closing: Fixed
Additional comments about closing: 3.6.12-1
/lib64/ld-linux-x86-64.so.2 (0x00007fee91fbb000)
Does it require a rebuild following the recent glibc update?
# Old
ExecStart=/usr/sbin/nmbd -F
# New
ExecStart=/usr/sbin/nmbd -D
I had a look at the Fedora unit file for confirmation and saw that they have no switches at all (by default).
Only thing that worked for me was to downgrade.
Thanks,
Leonid.