On Fri, 7 Jun 2024 08:50:11 +0200
"Stefan G. Weichinger via samba" <samba at lists.samba.org>
wrote:
>
> on the problematic DC "systemctl status" doesn't even show
> "samba-ad-dc".
>
> Although:
>
> # systemctl status samba-ad-dc.service
> ? samba-ad-dc.service - LSB: Samba daemons for the AD DC
> Loaded: loaded (/etc/init.d/samba-ad-dc; generated)
> Active: active (exited) since Fri 2024-06-07 08:45:53 CEST;
> 3min 9s ago
> Docs: man:systemd-sysv-generator(8)
> Process: 233044 ExecStart=/etc/init.d/samba-ad-dc start
> (code=exited, status=0/SUCCESS)
> CPU: 1ms
>
> Jun 07 08:45:53 pre01svdeb02 systemd[1]: Starting samba-ad-dc.service
> - LSB: Samba daemons for the AD DC...
> Jun 07 08:45:53 pre01svdeb02 systemd[1]: Started samba-ad-dc.service
> - LSB: Samba daemons for the AD DC.
>
>
>
Hi Stefan, I wasn't aware that 4.20.1 had hit backports, so I just
updated one of my DCs and it just worked, no errors and 'wbinfo -g'
works.
I did get this message before the upgrade:
apt-listchanges: News
---------------------
samba (2:4.20.1+dfsg-2) unstable; urgency=medium
Active Directory Domain Controller (AD-DC) functionality has been
split out of samba-the-file-server package into its own separate
package name samba-ad-dc. This includes the samba binary and a few
support executables. Please install samba-ad-dc package separately
if you need AD-DC functionality on your system.
-- Michael Tokarev <mjt at tls.msk.ru> Sun, 26 May 2024 13:44:07 +0300
Perhaps you haven't got the samba-ad-dc package installed, but it looks
like you have, very strange.
Rowland