NTPD Service

[tom__w]

I have a backup FreeNAS box that I am using strictly for DR. I copy snapshots to it every hour.

I noticed over the past 1+ weeks that the time keeps shifting on this box. I investigated and one suggestion was to run: "service NTPD start"

I do that and the clock synchronizes fine. The problem is I go back a few days later and it's shifting again? Suggestions?

Below is a copy past of the time corrections after 'service NTPD start'

Mar 9 15:32:15 Backup_FreeNAS_2950 ntpd[59783]: time correction of 12899 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
Mar 10 16:07:24 Backup_FreeNAS_2950 manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v
Mar 10 16:07:24 Backup_FreeNAS_2950 last message repeated 2 times
Mar 10 16:09:36 Backup_FreeNAS_2950 ntpd[36334]: ntpd 4.2.4p5-a (1)
Mar 10 19:44:43 Backup_FreeNAS_2950 ntpd[36335]: time reset +12899.116861 s
Mar 17 08:26:57 Backup_FreeNAS_2950 ntpd[36335]: time correction of 3300 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time.
Mar 17 18:38:00 Backup_FreeNAS_2950 manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list -v
Mar 17 18:38:00 Backup_FreeNAS_2950 last message repeated 2 times
Mar 17 18:40:50 Backup_FreeNAS_2950 ntpd[71859]: ntpd 4.2.4p5-a (1)
Mar 17 19:35:59 Backup_FreeNAS_2950 ntpd[71860]: time reset +3299.791528 s

 

[Yatti420]

What FreeNAS version? I've noticed time shift aswell on older versions.. My system powers off weekdays.. Haven't been watching for it lately.. DST just came around not sure if that affects it..

 

[tom__w]

I am on 9.1.0

I do not shut down my machines.

As I mentioned: "service ntpd start" fixes the time on the backup FreeNAS. When I do the same on the production FreeNAS, the message says ntpd has already started. Its time is perfect.

Strange...