If you’ve been watching your logs, you’ve probably noticed messages like this: In this post: FreeBSD 14.0 ntpd .2.8p16-a (included with the base OS) There are several FreeBSD PR lodged, the most relevant (to me) is ntpd: leap-seconds.list should not run inside jails, and IETF is no longer hosting it. The fix I am using: […]
After upgrading all my servers to FreeBSD 10.3 last weekend, I started to see these messages in the logs: Aug 3 21:15:19 slocum ntpd[29456]: leapsecond file (‘/var/db/ntpd.leap-seconds.list’): expired less than 64 days ago I found this post which suggested running service ntpd fetch but that did not fix it. While debugging the issue, I added
leapsecond file (‘/var/db/ntpd.leap-seconds.list’): expired less than N days ago Read More »
As I was setting up the new varm server, one of the Nagios checks I included was check_ntp_time. It comes standard with nagios-plugins. The check was reporting NTP CRITICAL: Offset unknown. Running the check from the command line showed: [dan@webserver:/usr/local/libexec/nagios] $ ./check_ntp_time -4 -H varm NTP CRITICAL: Offset unknown| Running the check with a timeout
Nagios check_ntp_time failed with ntpd on FreeBSD 10.2 Read More »