This message has started appearing in the journal log from ntpd
.
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): will expire in less than one day
What is it and how is it fixed please?
This message has started appearing in the journal log from ntpd
.
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): will expire in less than one day
What is it and how is it fixed please?
The
/usr/share/zoneinfo/leap-seconds.list
file contains a list of all past and announced future leap seconds; see The Internet Time Service and Leap Seconds in NIST Internet Time Service (ITS).ntpd
uses this file to determine when to insert a leap second.leap-seconds.list
contains a Expire date in NTP timestamp which is used byntpd
to:leap-seconds.list
is about to expire.leap-seconds.list
has expired; for an example see [ntpd] leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): expired error message #11327.I don't think an expired
leap-seconds.list
will causentpd
to fail, as long as there is no future leap second which occurs before an update to theleap-seconds.list
used byntpd
.By an update to the
tzdata
package. The current available version of that package on Ubuntu 24.04.1 LTS is2024a-3ubuntu1.1
in which the/usr/share/zoneinfo/leap-seconds.list
file contains:Looking on an AlmaLinux 8.10 system:
tzdata-2024b-4.el8.noarch
. I.e. the2024b
time zone data rather than the2024a
time zone data used by Ubuntu 24.04.1 LTS./usr/share/zoneinfo/leap-seconds.list
on AlmaLinux has contains the following later expiry date:Comparing the
leap-seconds.list
from the2024a
time zone data (installed on Ubuntu) and2024b
time zone data (installed on AlmaLinux) shows no difference in theLIST OF LEAP SECONDS
part of the file. I.e. the list of leap seconds used byntpd
on Ubuntu should be valid until the end of June 2025.Before then, Ubuntu should hopefully have have released a
2024b
version of thetzdata
package.Looking on launchpad there are the following which have a status of "Fix Committed", importance "high" and last update on 2024-12-16:
Hopefully this means an update to the Ubuntu
tzdata
packages for different releases to fix the issue are imminent.