Tumbleweed, AD joined host, winbind will no longer start

English Applications
1

Updated today and winbind no longer will start.

May 28 12:25:12 tw-03 systemd[1]: Starting Samba Winbind Daemon...
░░ Subject: A start job for unit winbind.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit winbind.service has begun execution.
░░ 
░░ The job identifier is 1575.
May 28 12:26:43 tw-03 systemd[1]: winbind.service: start operation timed out. Terminating.
May 28 12:26:43 tw-03 systemd[1]: winbind.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit winbind.service has entered the 'failed' state with result 'timeout'.
May 28 12:26:43 tw-03 systemd[1]: Failed to start Samba Winbind Daemon.
░░ Subject: A start job for unit winbind.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit winbind.service has finished with a failure.
░░ 
░░ The job identifier is 1575 and the job result is failed.
2

Looks like a problem with systemd unit (?). I mean, I can force run it in background and all it well (?)

3

Can you share the output of sudo systemctl cat winbind.service.

4 
# sudo systemctl cat winbind.service
# /usr/lib/systemd/system/winbind.service
[Unit]
Description=Samba Winbind Daemon
Documentation=man:winbindd(8) man:samba(7) man:smb.conf(5)
After=network.target nmb.service
Before=nss-user-lookup.target
Wants=nss-user-lookup.target

[Service]
Type=notify
PIDFile=/run/samba/winbindd.pid
EnvironmentFile=-/etc/sysconfig/samba
Environment=KRB5CCNAME=/run/samba/krb5cc_samba
Environment=KRB5RCACHEDIR=/var/cache/krb5rcache
ExecStart=/usr/sbin/winbindd --foreground --no-process-group $WINBINDOPTIONS
ExecReload=/bin/kill -HUP $MAINPID
LimitCORE=infinity


[Install]
WantedBy=multi-user.target
5

The timeout might be due to network issues or DNS/AD DC lookup failures. Is there any further useful information logged in the journal?

sudo journalctl -u winbind -b

Are the samba-* package versions consistent?

rpm -qa | grep samba

6

Thanks for the dump of the service file, you did write you can “force run it in background and all it well”. Is that also true if you run the command after ExecStart?

7

Yes, I was talking about starting the daemon directly from the command line. I will experiment a bit with the unit file.

8

Are you running on a system using SELinux? Running a command from the cli and running it under a systemd service will run the command in different contexts.

9

I changed the Type from notify to exec. Seems “ok” for now. Maybe the a problem with the notify no longer happening in winbind (?)

10

Adding this Ubuntu post from a long time ago: https://askubuntu.com/questions/1114272/samba-not-starting-from-systemctl-timeout