Red Hat Bugzilla – Bug 145444
start of daemons freeses when booting with connection to network
Last modified: 2014-03-16 22:51:50 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.5)
Description of problem:
-> when booting the system connected to the network, a lot of daemons
like named, dhcpd, mysqld, ... start very slowly or (in worst case)
-> if the system IS NOT connected to the network the start of daemons
at boottime works very well!
-> the same behavior is when system ist running:
e.g. "service named stop" hangs
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. power on system
Actual Results: -> kernel starts
-> daemons start with status "green"
-> e.g. dhcpd needs 15 sec top start
-> e.g. mysqld freeses - system does not come up
Expected Results: "normal" boot with all daemons running
I changed network-cables and uses eth1 instead of eth0, but it takes
If you strace one of them, where are they hanging? Is your DNS setup
Created attachment 109959 [details]
strace logfile of blocked "service named stop"
DNS setup seems to be correct.
I created a attachment of a strace-log of "service named stop"
This is an exampel - the shutdown of dhcpd "service dhcpd stop"
sometime didnÂ´t work either.
You need 'strace -f' to actually get the execution of the daemon and
not just the shell script, sorry.
Created attachment 110114 [details]
frozen "strace -f service named start"
# service named stop -> with exitstatus OK
# strace -f service named start -> this logfile
What's in the log file from named in this case?
It sounds like your resolver (or similar) config is not correct.
the configuration of the resolver seems to be correct:
192.168.200.245 is the IP of the server we talk about.
# cat /etc/resolv.conf
As a new attachment I put the logfile of the "frozen" "service named
start", that I mentioned in comment #5.
to put all "strange things" together:
-> The server boots very well, if the network-cable is *not* connected.
-> The server shows very slow (or frozen) startup of daemons when the
cable is plugged in.
-> Without the line "nameserver 192.168.200.245" in /etc/resolv.conf
the server works very well (this means: it asks the second DNS-server)
-> the named starts without logging any problems in syslog when
starting (see attachment), but it needs several minutes to start
Created attachment 110188 [details]
/var/log/messages of "frozen" service named start
Is your first nameserver reachable (via a route or whatever) at the
time the services are starting?
This server (192.168.200.245) is the first (master) nameserver.
The other one (192.168.10.245) is the second (slave) nameserver.
Between these two machines is a firewall which allows DNS but does not
When replacing "nameserver 192.168.200.245" by "nameserver
192.168.10.245" in /etc/resolv.conf this server seem to work stable.
But: Without connection to network (no cable plugged in) the server
starts without any problems.
Without connection, it won't bring up the network, and all packages
will get dropped immediately.
I'd probably check the firewall logs to make sure packets aren't
getting dropped; it does seem to be configuration related, not