On some servers of a customer the bind9 is not willing to start after the update to UCS5. After boot a manual start via systemctl start bind9.service is working. If the timeout of /usr/lib/univention-bind/samba4 wait-for-startup) /usr/bin/timeout 30 /bin/sh -c \ "until rndc -p 953 status | grep --quiet 'server is up and running'; do sleep 1; done" ;; is increased from 30 to 60 seconds the bind service is also starting during boot. We have a UCR for backend-ldap please introduce this timeout UCR also for samba backend.
See Bug #54108 comment 6: - For "dns/backend=ldap" there is UCRV "dns/timeout-start"
I'm also affected by this and it seems there are also some forum reports * https://help.univention.com/t/bind9-service-dont-start-after-reboot/19748 * https://help.univention.com/t/bind9-fails-to-start-automatically/20758 It seems to be caused by some timeout on starting bind or race-condition between bind and samba4. My attached logs also indicate this. I get this error when booting my VM-host and all guests firing up in parallel. It looks like the IO becomes to slow for the individual system as a consequence.
Created attachment 11223 [details] bootup logfile of comment-2