Bug 233853 - 12.0-RC3 ntpd leap second file expired
Summary: 12.0-RC3 ntpd leap second file expired
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: conf (show other bugs)
Version: 12.0-STABLE
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2018-12-07 20:05 UTC by Joe Barbish
Modified: 2020-02-27 13:51 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Joe Barbish 2018-12-07 20:05:31 UTC
ntpd launched from rc.conf during boot get message about 
/var/db/ntpd.lead-seconds.list: loaded, expire=2017-12-28.
Comment 1 Michael Laß 2018-12-12 21:11:52 UTC
Could this have been solved in the final release of 12.0 or be a local problem with your installation? For me, ntpd shows the following during startup on 12.0-RELEASE:

ntpd[802]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): good hash signature
ntpd[802]: leapsecond file ('/var/db/ntpd.leap-seconds.list'): loaded, expire=2019-06-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37
Comment 2 Michael Laß 2019-06-13 18:41:18 UTC
I recently reinstalled my system from the 12.0-RELEASE image. Indeed the provided ntpd.lead-seconds.list is expired. However, you can easily update it using "service ntpd onefetch". Also, this is typically performed automatically once a day by /etc/periodic/daily/480.leapfile-ntpd, so I think it's mostly a cosmetic issue.
Comment 3 Gleb Popov freebsd_committer 2020-02-27 13:51:20 UTC
Closing as Overcome by Events. 12.0 is already released and there are clear instructions how to fix "leapfile expired" errors in ntpd.