Bug 145444
Summary: | start of daemons freeses when booting with connection to network | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Hantke-Haring <h.hantke-haring> | ||||||||
Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||||||
Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | medium | ||||||||||
Version: | 3 | CC: | rvokal | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | i686 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2005-02-02 19:45:23 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Hantke-Haring
2005-01-18 16:07:10 UTC
If you strace one of them, where are they hanging? Is your DNS setup correct? 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. Hi Bill, 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 search sozialwerk-st-georg.de nameserver 192.168.200.245 nameserver 192.168.10.245 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 allow ping. 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 software related. |