Bug 1128432
| Summary: | Chronyd fails to start at boot with single NTP server configured | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John <johncwoods> | ||||
| Component: | chrony | Assignee: | Miroslav Lichvar <mlichvar> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 20 | CC: | mlichvar | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-11 07:12:38 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 1124059 *** |
Created attachment 925501 [details] text file containing relevant journal messages Description of problem: Chronyd service fails with "Could not connect NTP socket to 10.0.1.2:123 : Network is unreachable" message. The local server name configured in /etc/chrony.conf is being resolved to an IP addr (10.0.1.2 ) by the "dnsmasq" server located on the same box as the local "chrony" time server. Chronyd can be successfully started via "systemctl restart chronyd" after boot is complete. Version-Release number of selected component (if applicable): fedora = 3.15.8-200.fc20.x86_64 chrony = chrony.x86_64 1.30-1.fc20 How reproducible: always Steps to Reproduce: 1.configure single local time server in /etc/chrony.conf 2./etc/chrony.conf entry = "server lname.ldomain iburst" 3.chronyd fails to start at boot Actual results: chronyd issues "Could not connect NTP socket to 10.0.1.2:123 : Network is unreachable" to journal. Chronyd can be started after boot from commandline with "systemctl restart chronyd" Expected results: Additional info: