-------CUT-------- [root@artio ~]# systemctl status chronyd.service chronyd.service - NTP client/server Loaded: loaded (/lib/systemd/system/chronyd.service; enabled) Active: failed since Thu, 09 Feb 2012 11:22:12 +0100; 15s ago Process: 3539 ExecStartPost=/usr/libexec/chrony-helper add-dhclient-servers (code=exited, status=1/FAILURE) Process: 3536 ExecStart=/usr/sbin/chronyd -u chrony $OPTIONS (code=exited, status=0/SUCCESS) Process: 3530 ExecStartPre=/usr/libexec/chrony-helper generate-commandkey (code=exited, status=0/SUCCESS) Main PID: 3538 (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/chronyd.service -------CUT-------- starting the server manually succeeds: -------CUT-------- [root@artio ~]# chronyd -u chrony [root@artio ~]# echo $? 0 -------CUT-------- I neither get a SELinux exception as in bug 787477 nor do I have the same servers in /etc/chrony.conf as in /var/lib/dhclient/chrony.servers.*, as described in bug 787042. My chrony.conf is as it was shipped and our DHCP server sends NTP information pointing to our internal time server: -------CUT-------- [root@artio ~]# ls -l /var/lib/dhclient/chrony.servers.* -rw-r--r--. 1 root root 19 Feb 9 2012 /var/lib/dhclient/chrony.servers.eth0 -rw-r--r--. 1 root root 19 Feb 9 2012 /var/lib/dhclient/chrony.servers.wlan0 [root@artio ~]# cat /var/lib/dhclient/chrony.servers.* 172.20.10.4 iburst 172.20.10.4 iburst -------CUT-------- I've also tried with only one interface active (either wlan0 or eth0), but that did not make a difference.
Ok, I found the problem, against my previous assumption it is indeed related to bug 787042. The problem is that my two interfaces eth0 and wlan0 point to the same NTP server. Deleting one file, eg /var/lib/dhclient/chrony.servers.wlan0 allows me to start chronyd via systemctl: ------CUT------ root@artio ~]# rm /var/lib/dhclient/chrony.servers.wlan0 [root@artio ~]# systemctl start chronyd.servic ------CUT------ So the workaround from bug 787042 will probably also work for me, OTOH this is quite a major issue because it it probably "not too uncommon" having more than one interface, at least with laptops.
Yes, it's the same problem as in bug 787042. Adding a server which was already added (either from chrony.conf or DHCP) fails, the script exits with a non-zero exit code and the service is halted. *** This bug has been marked as a duplicate of bug 787042 ***