Bug 145444 - start of daemons freeses when booting with connection to network
Summary: start of daemons freeses when booting with connection to network
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts   
(Show other bugs)
Version: 3
Hardware: i686 Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2005-01-18 16:07 UTC by Hantke-Haring
Modified: 2014-03-17 02:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-02-02 19:45:23 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
strace logfile of blocked "service named stop" (10.83 KB, text/plain)
2005-01-19 08:27 UTC, Hantke-Haring
no flags Details
frozen "strace -f service named start" (388.75 KB, text/plain)
2005-01-24 11:17 UTC, Hantke-Haring
no flags Details
/var/log/messages of "frozen" service named start (10.18 KB, text/plain)
2005-01-25 10:33 UTC, Hantke-Haring
no flags Details

Description Hantke-Haring 2005-01-18 16:07:10 UTC
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)
system freeses.
-> 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):

How reproducible:

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

Additional info:

I changed network-cables and uses eth1 instead of eth0, but it takes
no effect

Comment 1 Bill Nottingham 2005-01-18 19:14:08 UTC
If you strace one of them, where are they hanging? Is your DNS setup

Comment 2 Hantke-Haring 2005-01-19 08:27:01 UTC
Created attachment 109959 [details]
strace logfile of blocked "service named stop"

Comment 3 Hantke-Haring 2005-01-19 08:37:08 UTC
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.

Comment 4 Bill Nottingham 2005-01-19 17:32:01 UTC
You need 'strace -f' to actually get the execution of the daemon and
not just the shell script, sorry.

Comment 5 Hantke-Haring 2005-01-24 11:17:44 UTC
Created attachment 110114 [details]
frozen "strace -f service named start"

# service named stop -> with exitstatus OK
# strace -f service named start -> this logfile

Comment 6 Bill Nottingham 2005-01-25 05:55:45 UTC
What's in the log file from named in this case?

It sounds like your resolver (or similar) config is not correct.

Comment 7 Hantke-Haring 2005-01-25 10:32:07 UTC
Hi Bill,

the configuration of the resolver seems to be correct: is the IP of the server we talk about.

# cat /etc/resolv.conf
search sozialwerk-st-georg.de

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" 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

Comment 8 Hantke-Haring 2005-01-25 10:33:38 UTC
Created attachment 110188 [details]
/var/log/messages of "frozen" service named start

Comment 9 Bill Nottingham 2005-01-25 15:22:11 UTC
Is your first nameserver reachable (via a route or whatever) at the
time the services are starting?

Comment 10 Hantke-Haring 2005-02-02 09:02:43 UTC
This server ( is the first (master) nameserver.
The other one ( is the second (slave) nameserver.

Between these two machines is a firewall which allows DNS but does not
allow ping.

When replacing "nameserver" by "nameserver" 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.

Comment 11 Bill Nottingham 2005-02-02 19:45:23 UTC
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
software related.

Note You need to log in before you can comment on or make changes to this bug.