This is a small thing : chrony seemed to have lost track of time, the fix was simple - and had to do with SELINUX.

### Losing Track of Time

The clock on my machine seemed unusually ‘off’. My first comparison was to my mobile phone

• an easy check, since mobiles are typically synced against the mobile-provider / cell towers.

Checking as to the state of play on the machine itself :

### Where are the sources?

The default Fedora /etc/chrony.conf contains a valid ‘pool’ configuration :

so why are no sources picked up? Checking /var/log/messages shows :

This tells us that chronyd is being denied something by SELINUX (something that I felt sure I had turned to permissive mode, since it’s often a source of hard-to-fathom errors).

### Bug in chronyd?

At first blush, this seemed like an error with chronyd, since the rest of the system was working fine.

However, SELINUX is doing a typical mis-direct here : The problem actually lay with the /etc/resolv.conf file itself - it had somehow become mislabled.

Solved.