Feature #2642: Change ntpd config so it doesn't silently exit if time is substantially off - pfSense - pfSense bugtracker

Actions

Copy link

Feature #2642

closed

Change ntpd config so it doesn't silently exit if time is substantially off

Added by Dim Hatz about 12 years ago. Updated almost 12 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

NTPD

Target version:

2.1

Start date:

09/23/2012

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Description

pfsense 2.1-BETA0 w/ ntpd 4.2.6p5 in a VBox VM: If host system is "suspended" overnight, the clock of the FreeBSD/pfsense VM will be off by several hours when the host system wakes up again the next morning. In this configuration pfsense's ntpd process silently exits (note: no message in /var/log/ntpd.log) leaving time wrong.

This is documented ntpd's behavior of "once the clock has been set, an error greater than 1000 s will cause ntpd to exit"

It seems the way to solve this is to add "tinker panic 0" at the top of ntpd.conf

Forum thread: http://forum.pfsense.org/index.php/topic,53906.msg288485.html