Bug 1228875 - chronyd can fail when prefer suboption is used
Summary: chronyd can fail when prefer suboption is used
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: chrony
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-06 02:17 UTC by kealthou
Modified: 2015-06-27 22:32 UTC (History)
1 user (show)

Fixed In Version: chrony-2.1.1-1.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-27 22:32:16 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description kealthou 2015-06-06 02:17:36 UTC
Description of problem:
Chronyd crashes when multiple sources are available and chronyd selects a server with a prefer suboption as the synchronisation source, I think.


Version-Release number of selected component (if applicable):
chrony-2.0-1.fc22.i686

How reproducible:
always

Steps to Reproduce:
1. Make sure there is at least one pool/server in /etc/chrony.conf.
2. Append a server entry to /etc/chrony.conf, and set prefer to it.
3. sudo systemctl (re)start chronyd
4. Wait for chronyd to select the server with prefer as the synchronisation source.

Actual results:
It crashes.

Expected results:
It doesn't crash.

Additional info:
$ journalctl -b -u chronyd
 6月 05 22:41:46 localhost.localdomain systemd[1]: Starting NTP client/server...
 6月 05 22:41:46 localhost.localdomain chronyd[28782]: chronyd version 2.0 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +DEBUG +ASYNCDNS +IPV6 +SECHASH)
 6月 05 22:41:46 localhost.localdomain chronyd[28782]: Frequency 10.215 +/- 5.031 ppm read from /var/lib/chrony/drift
 6月 05 22:41:46 localhost.localdomain systemd[1]: Started NTP client/server.
 6月 05 22:41:52 localhost.localdomain chronyd[28782]: Selected source 202.224.32.4
 6月 05 22:41:53 localhost.localdomain systemd[1]: chronyd.service: main process exited, code=killed, status=6/ABRT
 6月 05 22:41:53 localhost.localdomain systemd[1]: Unit chronyd.service entered failed state.
 6月 05 22:41:53 localhost.localdomain systemd[1]: chronyd.service failed.

Comment 1 Miroslav Lichvar 2015-06-08 10:39:49 UTC
Thanks for the report.

It should be fixed in upstream git now.

http://git.tuxfamily.org/chrony/chrony.git/commit/?id=4253075a97141edfa62043ab71bd0673587e6629

Comment 2 Fedora Update System 2015-06-22 15:04:00 UTC
chrony-2.1-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/chrony-2.1-1.fc22

Comment 3 Fedora Update System 2015-06-24 16:02:39 UTC
Package chrony-2.1.1-1.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing chrony-2.1.1-1.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-10615/chrony-2.1.1-1.fc22
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2015-06-27 22:32:16 UTC
chrony-2.1.1-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.


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