Bind9 service don't start after reboot

Hi to everyone,
i did upgrade my UCS server 4.4 to 5.0-1 errata279.

Unfortunately after reboot, i found out that bind9 was not running.
Below the result of cat command on syslog

Apr  6 04:52:12 zbdc01 systemd[1]: Started LSB: Univention Directory Policy.
Apr  6 04:52:13 zbdc01 systemd[1]: bind9.service: Control process exited, code=exited, status=124/n/a
Apr  6 04:52:14 zbdc01 freeradius[637]: tls: Using cached TLS configuration from previous invocation
Apr  6 04:52:14 zbdc01 freeradius[637]: rlm_detail (auth_log): 'User-Password' suppressed, will not appear in detail output
Apr  6 04:52:15 zbdc01 freeradius[637]: rlm_ldap: libldap vendor: OpenLDAP, version: 20447
Apr  6 04:52:15 zbdc01 freeradius[637]: rlm_ldap (ldap): Initialising connection pool
Apr  6 04:52:15 zbdc01 freeradius[637]: rlm_cache (cache_eap): Driver rlm_cache_rbtree (module rlm_cache_rbtree) loaded and linked
Apr  6 04:52:15 zbdc01 freeradius[637]: rlm_mschap (mschap): authenticating by calling 'ntlm_auth'
Apr  6 04:52:15 zbdc01 freeradius[637]: Ignoring "sql" (see raddb/mods-available/README.rst)
Apr  6 04:52:15 zbdc01 freeradius[637]: radiusd: #### Skipping IP addresses and Ports ####
Apr  6 04:52:15 zbdc01 freeradius[637]: Configuration appears to be OK
Apr  6 04:52:15 zbdc01 freeradius[637]: rlm_ldap (ldap): Removing connection pool
Apr  6 04:52:16 zbdc01 systemd[1]: Started FreeRADIUS multi-protocol policy server.
Apr  6 04:52:21 zbdc01 named[1005]: samba_dlz: started for DN DC=mydomain,DC=it
Apr  6 04:52:21 zbdc01 named[1005]: samba_dlz: starting configure
Apr  6 04:52:22 zbdc01 named[1005]: samba_dlz: trying partition 'CN=MicrosoftDNS,DC=DomainDnsZones,DC=mydomain,DC=it'
Apr  6 04:52:22 zbdc01 named[1005]: samba_dlz: configured writeable zone 'mydomain.it'
Apr  6 04:52:22 zbdc01 named[1005]: samba_dlz: trying partition 'CN=MicrosoftDNS,DC=DomainDnsZones,DC=mydomain,DC=it'
Apr  6 04:52:22 zbdc01 named[1005]: samba_dlz: configured writeable zone '0.1.10.in-addr.arpa'
Apr  6 04:52:22 zbdc01 named[1005]: samba_dlz: trying partition 'CN=MicrosoftDNS,DC=DomainDnsZones,DC=mydomain,DC=it'
Apr  6 04:52:22 zbdc01 named[1005]: samba_dlz: configured writeable zone '0.2.10.in-addr.arpa'
Apr  6 04:52:22 zbdc01 named[1005]: samba_dlz: trying partition 'CN=MicrosoftDNS,DC=ForestDnsZones,DC=mydomain,DC=it'
Apr  6 04:52:22 zbdc01 named[1005]: samba_dlz: configured writeable zone '_msdcs.mydomain.it'
Apr  6 04:52:22 zbdc01 named[1005]: none:106: 'max-cache-size 90%' - setting to 7149MB (out of 7943MB)
Apr  6 04:52:22 zbdc01 named[1005]: loading configuration: shutting down
Apr  6 04:52:22 zbdc01 named[1005]: exiting (due to fatal error)
Apr  6 04:52:22 zbdc01 named[1005]: ../../../bin/named/client.c:3516: unexpected error:
Apr  6 04:52:22 zbdc01 named[1005]: isc_socket_accept() failed: shutting down
Apr  6 04:52:22 zbdc01 named[1005]: ../../../bin/named/client.c:3516: unexpected error:
Apr  6 04:52:22 zbdc01 named[1005]: isc_socket_accept() failed: shutting down
Apr  6 04:52:22 zbdc01 named[1005]: ../../../bin/named/client.c:3516: unexpected error:
Apr  6 04:52:22 zbdc01 named[1005]: isc_socket_accept() failed: shutting down
Apr  6 04:52:23 zbdc01 systemd[1]: bind9.service: Main process exited, code=exited, status=1/FAILURE
Apr  6 04:52:23 zbdc01 systemd[1]: bind9.service: Failed with result 'exit-code'.
Apr  6 04:52:23 zbdc01 systemd[1]: Failed to start BIND Domain Name Server with samba4 backend.

I tried to search in google about this issue “isc_socket_accept() failed: shutting down” and i found this in Bind repository

bind9/CHANGES at main · isc-projects/bind9 · GitHub where they talk about a fix on isc_socket_accept

"

1562. [bug] isc_socket_create() and isc_socket_accept() could
leak memory under error conditions. [RT #10230]

"

If i do start bind9 service manually (in GUI) it starts and works without any issue …
So i did a workaround, implementing a crontab script that check if exists a MainPID of bind9.service, otherwise it starts the service. But what can i do to fix this problem ufficially?

Thanks
Leonardo

We have the same problem: after reboot bind9 does not start automatically on one of two UCS systems. After starting the service manually from GUI it is workuíng fine. The other UCS system (Backup Server, installed identically) does not have the problem.