Red Hat Bugzilla – Bug 1316687
named's dispatcher for systemd blocks to get NetworkManager to state CONNECTED (boot delay)
Last modified: 2016-05-12 06:39:06 EDT
Description of problem:
During boot process when network interfaces are set up (by NetworkManager) there are started installed dispatchers. For BIND daemon there is a file "/etc/NetworkManager/dispatcher.d/13-named". It contains this command:
/usr/bin/systemctl reload named.service > /dev/null 2>&1 || true
It calls "named.service". But systemd starts "named.service" when "network-online.target" is met. At this time the network is not accessible. So there is 30sec delay and then "NetworkManager-wait-online.service" fail. After that boot process continues.
Version-Release number of selected component (if applicable):
Package "bind" installed.
NetworkManager.service and NetworkManager-dispatcher.service enabled.
Steps to Reproduce:
1. Boot pc
2. Enter command "systemctl" or "journalctl -b"
3. search for NetworkManager-wait-online.service fail
Boot process delay 30 seconds and there is present "NetworkManager-wait-online.service" fail.
In my environment it helps to use "--no-block" option in dispatcher file. Like this:
/usr/bin/systemctl --no-block reload named.service > /dev/null 2>&1 || true
*** This bug has been marked as a duplicate of bug 1277257 ***