Hi Guys,
Samba AD DC Service stops or die
openSUSE Tumbleweed.
samba-ad-dc.service was working fine for over a year.
Run update on Monday the 9th and now:
systemctl status samba-ad-dc.service
samba-ad-dc.service - Samba Active Directory Domain Controller
Loaded: loaded (/usr/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2020-03-11 10:05:33 PDT; 5h 39min ago
Process: 26191 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
Process: 26205 ExecStart=/usr/sbin/samba -D (code=exited, status=0/SUCCESS)
Main PID: 26206 (code=exited, status=1/FAILURE)
Mar 11 10:05:33 hype mitkdc[26224]: [2020/03/11 10:05:33.423228, 0] …/…/source4/kdc/kdc-service-mit.c:344(mitkdc_server_done)
Mar 11 10:05:33 hype mitkdc[26224]: The MIT KDC daemon died with exit status 6
Mar 11 10:05:33 hype mitkdc[26224]: [2020/03/11 10:05:33.423362, 0] …/…/source4/smbd/service_task.c:36(task_server_terminate)
Mar 11 10:05:33 hype mitkdc[26224]: task_server_terminate: task_server_terminate: [mitkdc child process exited]
Mar 11 10:05:33 hype samba[26206]: [2020/03/11 10:05:33.424755, 0] …/…/source4/smbd/server.c:370(samba_terminate)
Mar 11 10:05:33 hype samba[26206]: samba_terminate: samba_terminate of samba 26206: mitkdc child process exited
Mar 11 10:05:33 hype systemd[1]: samba-ad-dc.service: Main process exited, code=exited, status=1/FAILURE
Mar 11 10:05:33 hype winbindd[26263]: [2020/03/11 10:05:33.438597, 0] …/…/source3/winbindd/winbindd.c:242(winbindd_sig_term_handler)
Mar 11 10:05:33 hype winbindd[26263]: Got sig[15] terminate (is_parent=0)
Mar 11 10:05:33 hype systemd[1]: samba-ad-dc.service: Failed with result ‘exit-code’.
There was an update for Samba this morning which I applied hoping.
systemctl status samba-ad-dc.service returns the same.
https://forums.opensuse.org/showthread.php/539366-Samba-AD-DC-won-t-start-Looks-like-KDC-is-crashing
Which ended with, “I submitted a bug: https://bugzilla.opensuse.org/show_bug.cgi?id=1165766”
What changed?
Is there a workaround until this is fixed?
Thanks
Bob