Univention-maintenance.service did not start after reboot automaticliy

Hello all,
using here UCS 4.4.1

If i restart some server (Memberserver), the Univention-Mainenance.service did not start.

systemctl is-enabled univention-maintenance.service
univention-maintenance.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install is-enabled univention-maintenance
enabled
Aug 03 20:33:08 data systemd[1]: Starting LSB: Univention Updater...
Aug 03 20:33:09 data univention-maintenance[1355]: Checking network for Univention maintenance...ldap[dc1.supertux.lan
Aug 03 20:33:09 data systemd[1]: univention-maintenance.service: Control process exited, code=exited status=1
Aug 03 20:33:09 data systemd[1]: Failed to start LSB: Univention Updater.
Aug 03 20:33:09 data systemd[1]: univention-maintenance.service: Unit entered failed state.
Aug 03 20:33:09 data systemd[1]: univention-maintenance.service: Failed with result 'exit-code'.

If i login @the server i can start the service normaly. Server Uptime in this startime 0 Minutes. Strange.
Can i something do for it?

Best Regards
Boospy

Hi,
i am facing the same issue here on a system.

UCS-Version
4.4-2 errata330 (Blumenthal)
UMC-Version
11.0.4-46A~4.4.0.201910151758

Starting the service manually via ssh works completely fine, until next boot.
thanks for your help
Sascha

Yes. It is not depending on Type of the Server. So same on slave, Master, backup. But not on all boots.

Mastodon