Univention Bugzilla – Bug 45065
DHCP daemon is not always started after rebooting a UCS 4.2 system
Last modified: 2017-07-26 14:39:47 CEST
univention-dhcp does not start when the DNS server is not yet available. In that case the /etc/init.d/univention-dhcp # test_config() fails to resolve the LDAP server and aborts switching RUNSV to running. This is logged in /var/log/univention/dhcp.log: > ... POLICY ( ERROR ) : Failed to get namingContexts: Can't contact LDAP server I'm able to re-product this by adding a "sleep 10" to "/etc/runit/univention-bind-samba4/run" before BIND9 is started. It does not trigger always. +++ This bug was initially created as a clone of Bug #43688 +++
r81356 | Bug #45065 dhcp: Always start DHCP runsv service Package: univention-dhcp Version: 11.0.0-9A~4.2.0.201707251103 Branch: ucs_4.2-0 Scope: errata4.2-1 r81357 | Bug #45065 dhcp: Always start DHCP runsv service YAML univention-dhcp.yaml
YAML: OK Tests: OK Code review: OK
<http://errata.software-univention.de/ucs/4.2/101.html>