Leap second 2016
As you guys probably know, on December 31 a leap second will occur.
I am well aware of the need to update the kernel, NTP and tzdata packages.
My question is: if my servers were prepared for the 2015 leap second, meaning I updated the kernel, tzdata and ntp packages to my servers so they won't be affected in 2015, do I need to update the packages again to overcome this year's leap second? Or are the 2015 "safe" kernel, tzdata and ntp packages still safe for this leap second?
Responses
You can find all the details in this article.
You have to upgrade the tzdata package to a version higher than tzdata-2016f-1 - the latest version as of now is : tzdata-j-1.
Having the latest available stable kernel installed is more than recommended. Please check whether the chrony daemon is running : systemctl status chronyd - in case that the daemon is not running (it should be enabled by default), execute these commands :
sudo setenforce 0sudo systemctl enable chronydsudo setenforce 1
Possible, but I think it also might have been the version of the SELinux policy module when I ran the virtual machine on my fedora 25 host system with KVM / virt-manager. I experienced something like this in other cases and once a new SELinux policy version was released, the same thing worked without any interactions.
Chrony is only recommended for systems that are regularly suspended, not servers that permanently on. Having chronyd running is not a prerequisite to overcoming the leap second challenges if you are running ntpd.
From the documentation:
Chrony should be considered for all systems which are frequently suspended or otherwise intermittently disconnected and reconnected to a network. Mobile and virtual systems for example.
The NTP daemon (ntpd) should be considered for systems which are normally kept permanently on.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
