Bug 983610
Summary: | Fatal error : Could not bind IPv6 command socket : Cannot assign requested address | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> |
Component: | chrony | Assignee: | Miroslav Lichvar <mlichvar> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | michael.monreal, mlichvar |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | chrony-1.28-1.fc18 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-22 00:30:07 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: |
Description
Kamil Páral
2013-07-11 14:36:34 UTC
From the ip output, it seems the loopback interface doesn't have the ::1/128 address, which chrony tries to bind its command socket to (configured by bindcmdaddress ::1). Removing the directive in the config should fix it, but I'm not sure if we want to that by default. Is it common to not have ::1? Problem solved, I had net.ipv6.conf.all.disable_ipv6 = 1 in /etc/sysctl.conf. NetworkManager is somehow able to override it, so I was able to get IPv6 address for eth0. If I comment out that line, I receive ::1 and chronyd starts properly. Still, I think chronyd should not crash if IPv6 support is disabled. Thanks for the update. I agree it should not be a fatal error. chrony-1.28-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/chrony-1.28-1.fc19 Package chrony-1.28-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing chrony-1.28-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-13151/chrony-1.28-1.fc19 then log in and leave karma (feedback). chrony-1.28-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/chrony-1.28-1.fc18 chrony-1.28-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. chrony-1.28-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. I ran into this when checking my systemd logs. While the error is not fatal anymore it still shows up as "red". I have disabled IPv6 on this system and wonder if there is a way to also disable it for chrony to get rid of this non-fatal error. You can create file /etc/sysconfig/chronyd containing "OPTIONS=-4" to add -4 to the chronyd command line, which will disable IPv6 sockets. |