OpenNTPD works well few days and then not sync

dominique.fournier

Hi,
The OpenNTP server don't send the good time after few days of work.
I have the message on clients :
$ ntpdate -d 147.173.1.254

 4 May 09:21:40 ntpdate[7239]: ntpdate 4.2.6p3@1.2290 Tue Mar  6 15:36:36 UTC 2012 (1)
Looking for host 147.173.1.254 and service ntp
host found : Rt-CNRS.grenoble.cnrs.fr
transmit(147.173.1.254)
receive(147.173.1.254)
transmit(147.173.1.254)
receive(147.173.1.254)
transmit(147.173.1.254)
receive(147.173.1.254)
transmit(147.173.1.254)
receive(147.173.1.254)
transmit(147.173.1.254)
147.173.1.254: Server dropped: Leap not in sync
server 147.173.1.254, port 123
stratum 3, precision -21, leap 11, trust 000
refid [147.173.1.254], delay 0.02588, dispersion 0.00002
transmitted 4, in filter 4
reference time:    d34e0168.e66ad7ff  Fri, May  4 2012  9:19:04.900
originate timestamp: d34e07bb.40636fff  Fri, May  4 2012  9:46:03.251
transmit timestamp:  d34e020a.f3d9fef5  Fri, May  4 2012  9:21:46.952
filter delay:  0.02591  0.02588  0.02592  0.02592 
         0.00000  0.00000  0.00000  0.00000 
filter offset: 1456.298 1456.298 1456.298 1456.298
         0.000000 0.000000 0.000000 0.000000
delay 0.02588, dispersion 0.00002
offset 1456.298863

 4 May 09:21:48 ntpdate[7239]: no server suitable for synchronization found

I have no logs in ntp.debug or ntp.info on PFSense (147.173.1.254) concerning a problem. There is no log concerning pf.

Here are the servers : europe.pool.ntp.org 134.214.100.6 129.88.30.1

If I restart the service, after few minutes, the clients have the good time.

Version of PFSense : Sun Apr 29 11:33:34 EDT 2012

Do you have any idea ?

jimp

Update to a recent snap, the logs should be fixed, so it would be more informative.

I have seen the same thing before though, after some time my router at home will have some major clock drift (one time it was off by ~1hr) and yet ntpd was running…

dominique.fournier

Right !

I didn't see the error in logs, but I found it this morning :
May 5 11:00:15 pfsense1 ntpd[15954]: recvmsg control format 85.10.240.253: Bad file descriptor
May 5 11:01:00 pfsense1 ntpd[15954]: recvmsg control format 134.214.100.6: Bad file descriptor

Any idea ?

jimp

Not seeing any reference to that error message anywhere meaningful. Are those the only two you see? Are there a lot of those entries?

dominique.fournier

Yes a lot of these.
Just before the errors, I havec the last good line with :
May 5 10:09:16 pfsense1 ntpd[15954]: reply from 85.10.240.253: offset 1019352811.353714 delay 0.029221, next query 32s

The Offset is enormous !

It is maybe why the daemon stops. But : Why is there this offset ? The clock should stay connected !!!

I just look at the offset since this morning, when I restart the service : it is 3s !!!

jimp

Not sure how it would get that far off. You might try changing to a different ntp server or two, perhaps ones more local to you, to rule that out.

dominique.fournier

OK
I just try to remove europe.pool.ntp.org. I will see if the time is ripping.

podperson

Have noticed this as well. I have a local PPS timeserver. The PC's on the same lan have remained synced, PFsense looses sync. Modified ntp.conf to add my local timeserver, started service via shell, command prompt also worked("service ntpd onestart").

The GUI general setup(NTP time server) and service startup do not seem to function properly, though I'm a PFSense noob and could be wrong. I got timeout when trying "ntpq -p" until I started via command prompt.

Will update if this continues to work.

dominique.fournier

Hi ! I run the test of removing europe.pool.ntp.org leaving two time servers. The service stay synchronized and distribute the time correctely for 8h.

Before, I see in logs :
adjusting local clock by -0.028700s
After, no more adjusting local clock, and the offset is impressive : 463s in two days !!!
WHen I restart the service :
May 9 07:00:52 pfsense1 ntpd[13476]: recvmsg control format 129.88.30.1: Bad file descriptor
May 9 07:52:39 pfsense1 ntpd[13476]: recvmsg control format 134.214.100.6: Bad file descriptor
May 9 07:55:15 pfsense1 ntpd[13476]: recvmsg control format 129.88.30.1: Bad file descriptor
May 9 08:29:53 pfsense1 ntpd[60782]: reply from 129.88.30.1: offset 463.080535 delay 0.000335, next query 7s
May 9 08:37:36 pfsense1 ntpd[60477]: no reply received in time, skipping initial time setting
May 9 08:37:36 pfsense1 ntpd[61284]: reply from 129.88.30.1: offset 0.000004 delay 0.000341, next query 5s
May 9 08:37:36 pfsense1 ntpd[61284]: reply from 134.214.100.6: offset 0.001080 delay 0.003766, next query 5s

No logs concerning ntp in the firewall.
Do you have an idea ?

Edit : I just upgrade the PFSense to the last developpment version and the problem persists.
May 9 15:24:33 pfsense1 ntpd[14397]: reply from 129.88.30.1: offset -0.000545 delay 0.000271, next query 1532s
May 9 15:25:34 pfsense1 ntpd[14397]: reply from 134.214.100.6: offset 0.001059 delay 0.004879, next query 1614s

Thanks

Dom

wallabybob

I'm running

2.1-DEVELOPMENT (i386)
built on Wed May 2 08:30:32 EDT 2012
FreeBSD 8.3-RELEASE

on my test pfSense and 2.0.1-RELEASE on my production pfSense. My test pfSense uses my production pfSense as its time server and the production pfSense uses au.pool.ntp.org.

The test pfSense reports an uptime of

10:14AM up 1 day, 12:02, 2 users, load averages: 0.15, 0.21, 0.15

the ntp log file shows (I've removed a number of sections to reduce the repetition)

May 9 11:06:32 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 385261.416476 delay 0.000443, next query 33s
May 9 11:07:05 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 385261.412328 delay 0.000526, next query 31s
May 9 11:07:05 pfsense2 ntpd[52981]: adjusting local clock by -385261.123065s
May 9 11:07:36 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 385261.389138 delay 0.000439, next query 33s
May 9 11:08:09 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 385261.384969 delay 0.000475, next query 31s
May 9 11:08:39 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 385261.386052 delay 0.000483, next query 34s
May 9 11:09:13 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 385261.381733 delay 0.000443, next query 31s
May 9 11:09:45 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 385261.377687 delay 0.000454, next query 33s
May 9 11:10:18 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 385261.373528 delay 0.000484, next query 31s
May 9 11:10:49 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 385261.383924 delay 0.000501, next query 32s
May 9 11:10:49 pfsense2 ntpd[52981]: adjusting local clock by -328575.789223s
May 9 11:11:21 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 328577.182028 delay 0.000448, next query 34s
May 9 11:11:54 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 328577.199720 delay 0.000420, next query 34s
May 9 11:11:54 pfsense2 ntpd[52981]: adjusting local clock by -17707.896128s
May 9 11:12:28 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 17709.642462 delay 0.000483, next query 32s
May 9 11:13:00 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 17709.638407 delay 0.000456, next query 32s
May 9 11:13:33 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 17709.634236 delay 0.000438, next query 32s
May 9 11:14:05 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 17709.630180 delay 0.000458, next query 31s
May 9 11:14:36 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 17709.626279 delay 0.000472, next query 31s
May 9 11:15:06 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 17709.627376 delay 0.000511, next query 30s
May 9 11:15:36 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 17709.623562 delay 0.000477, next query 34s
May 9 11:16:10 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 17709.619269 delay 0.000484, next query 33s
May 9 11:16:10 pfsense2 ntpd[52981]: adjusting local clock by 367554.800348s
May 9 11:16:43 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -367551.798139 delay 0.000464, next query 34s
May 9 11:17:18 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -367551.797403 delay 0.000494, next query 31s
May 9 11:17:49 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -367551.801293 delay 0.000460, next query 31s
May 9 11:17:49 pfsense2 ntpd[52981]: adjusting local clock by 752815.694486s
May 9 11:18:20 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -752813.194296 delay 0.000503, next query 33s

The offsets seem to fluctuate far too wildly. It might be my ignorance about ntp implementation but I didn't expect to see two different processes reporting here.

Other interesting bits from the ntp log file:

May 9 11:58:08 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -4760396.768472 delay 0.000503, next query 31s
May 9 11:58:08 pfsense2 ntpd[52981]: adjusting local clock by 413568.993848s
May 9 11:58:40 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -413570.169917 delay 0.000535, next query 31s
May 9 11:59:11 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -413570.173817 delay 0.000476, next query 33s
May 9 11:59:11 pfsense2 ntpd[52981]: adjusting local clock by -3933257.891345s
May 9 11:59:44 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 3933256.384790 delay 0.000453, next query 34s
May 9 12:00:17 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 3933256.385496 delay 0.000430, next query 34s

which seems like a huge change in offset in just a short interval

May 9 15:07:43 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -177783081.314545 delay 0.000512, next query 34s
May 9 15:08:17 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -177783081.318815 delay 0.000461, next query 34s
May 9 15:08:17 pfsense2 ntpd[52981]: adjusting local clock by 177783073.231963s
May 9 15:08:52 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -177783081.348464 delay 0.000456, next query 32s
May 9 15:09:24 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -177783081.352468 delay 0.000459, next query 31s
May 9 15:09:55 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -177783081.356347 delay 0.000476, next query 32s
May 9 15:10:27 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -177783081.360332 delay 0.000553, next query 31s
May 9 15:10:58 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -177783081.364231 delay 0.000457, next query 31s
May 9 15:11:29 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset -177783081.368102 delay 0.000515, next query 31s
May 9 15:11:29 pfsense2 ntpd[52981]: adjusting local clock by -688505490.388574s
May 9 15:12:00 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 688505481.287379 delay 0.000427, next query 34s
May 9 15:12:35 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 688505481.282980 delay 0.000464, next query 30s
May 9 15:13:05 pfsense2 ntpd[53222]: reply from 192.168.211.173: offset 688505481.279211 delay 0.000520, next query 34s
May 9 15:13:05 pfsense2 ntpd[52981]: adjusting local clock by -1554794052.584493s
May 9 15:13:39 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: No such file or directory
May 9 16:05:51 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 9 16:58:53 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 9 17:50:46 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 9 18:45:30 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 9 19:37:22 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 9 20:30:27 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 9 21:22:46 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 9 22:16:49 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 9 23:11:11 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 00:05:34 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 00:56:11 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 01:46:21 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 02:36:39 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 03:27:54 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 04:18:26 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 05:08:45 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 05:58:52 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 06:53:44 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 07:45:01 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 08:37:22 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 09:30:27 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor

which is the last part of the log file.

Here are the active ntp processes:

$ ps lax | grep ntp
0 52981 1 0 44 0 3424 1472 select Is ?? 0:00.09 ntpd: [priv] (ntpd)
123 53222 52981 0 44 0 3424 1552 select I ?? 0:00.99 ntpd: ntp engine (ntpd)
123 53716 53222 0 76 0 3424 1480 select I ?? 0:00.00 ntpd: dns engine (ntpd)
0 5398 46727 0 44 0 3536 1160 - R+ 0 0:00.01 grep ntp
$

To fix a captive portal issue I'm planning to update to a newer snapshot build within 12 hours. I'll try to capture the ntp logging for the first few hours.

wallabybob

I captured the last part of the ntp log file before installing the new snapshot:

May 10 08:37:22 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 09:30:27 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 10:22:47 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 11:14:20 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 12:05:22 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 13:00:17 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 13:52:31 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 14:45:52 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 15:35:58 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 16:30:28 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 17:24:06 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 18:16:14 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 19:09:02 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 20:02:27 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 20:55:59 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 21:49:43 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor
May 10 22:44:00 pfsense2 ntpd[53222]: recvmsg control format 192.168.211.173: Bad file descriptor

It looks as if ntpd is unlikely to recover from this problem.

Roots0

I'm seeing the same thing:

May 10 05:48:35 gateway ntpd[8512]: adjusting local clock by -7904770.741649s
May 10 05:49:08 gateway ntpd[8640]: reply from 130.88.212.143: offset 7904772.461468 delay 0.029575, next query 33s
May 10 05:49:42 gateway ntpd[8640]: reply from 130.88.212.143: offset 7904772.461196 delay 0.023540, next query 31s
May 10 05:50:13 gateway ntpd[8640]: reply from 130.88.212.143: offset 7904772.463844 delay 0.021637, next query 31s
May 10 05:50:44 gateway ntpd[8640]: reply from 130.88.212.143: offset 7904772.467284 delay 0.025273, next query 32s
May 10 05:50:44 gateway ntpd[8512]: adjusting local clock by -8805166.637369s
May 10 05:51:16 gateway ntpd[8640]: reply from 130.88.212.143: offset 8805169.011660 delay 0.025153, next query 34s
May 10 05:51:50 gateway ntpd[8640]: reply from 130.88.212.143: offset 8805169.013496 delay 0.023513, next query 32s
May 10 05:52:23 gateway ntpd[8640]: reply from 130.88.212.143: offset 8805169.010972 delay 0.021779, next query 31s
May 10 05:52:54 gateway ntpd[8640]: reply from 130.88.212.143: offset 8805169.014191 delay 0.023272, next query 31s
May 10 05:53:25 gateway ntpd[8640]: reply from 130.88.212.143: offset 8805169.017823 delay 0.025015, next query 32s
May 10 05:53:57 gateway ntpd[8640]: reply from 130.88.212.143: offset 8805169.020183 delay 0.024055, next query 31s
May 10 05:54:28 gateway ntpd[8640]: reply from 130.88.212.143: offset 8805169.022668 delay 0.023517, next query 31s
May 10 05:54:28 gateway ntpd[8512]: adjusting local clock by -8296290.396681s
May 10 05:54:59 gateway ntpd[8640]: reply from 130.88.212.143: offset 8296293.905219 delay 0.024344, next query 31s
May 10 05:55:30 gateway ntpd[8640]: reply from 130.88.212.143: offset 8296293.906833 delay 0.022374, next query 34s
May 10 05:56:04 gateway ntpd[8640]: reply from 130.88.212.143: offset 8296293.910683 delay 0.021894, next query 32s
May 10 05:56:36 gateway ntpd[8640]: reply from 130.88.212.143: offset 8296293.914262 delay 0.024828, next query 34s
May 10 05:56:36 gateway ntpd[8512]: adjusting local clock by -5428577.634802s
May 10 05:57:11 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.790894 delay 0.023720, next query 33s
May 10 05:57:43 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.798579 delay 0.024796, next query 34s
May 10 05:58:18 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.796877 delay 0.024651, next query 31s
May 10 05:58:49 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.798752 delay 0.023276, next query 33s
May 10 05:59:22 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.802529 delay 0.023580, next query 34s
May 10 05:59:56 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.804489 delay 0.021434, next query 30s
May 10 06:00:26 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.817238 delay 0.039292, next query 33s
May 10 06:00:26 gateway ntpd[8512]: adjusting local clock by -5428576.476414s
May 10 06:00:59 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.803900 delay 0.024217, next query 31s
May 10 06:01:30 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.807548 delay 0.024543, next query 30s
May 10 06:02:00 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.808380 delay 0.022604, next query 31s
May 10 06:02:32 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.807759 delay 0.024381, next query 34s
May 10 06:03:06 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.811854 delay 0.026996, next query 31s
May 10 06:03:37 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.812745 delay 0.021674, next query 30s
May 10 06:04:07 gateway ntpd[8640]: reply from 130.88.212.143: offset 5428581.814592 delay 0.021130, next query 31s
May 10 06:04:07 gateway ntpd[8512]: adjusting local clock by 2476197.092430s
May 10 06:04:38 gateway ntpd[8640]: reply from 130.88.212.143: offset -2476190.638312 delay 0.028693, next query 30s
May 10 06:05:09 gateway ntpd[8640]: reply from 130.88.212.143: offset -2476190.626512 delay 0.041115, next queCLOG

jimp

I started a redmine ticket here:
http://redmine.pfsense.org/issues/2423

wallabybob

The ntp log some time after reinstall and startup of new snapshot:

May 10 23:09:42 pfsense2 ntpd[50779]: ntp engine ready
May 10 23:09:42 pfsense2 ntpd[50779]: reply from 192.168.211.173: offset 2.543754 delay 0.000905, next query 6s
May 10 23:09:44 pfsense2 ntpd[50498]: set local clock to Thu May 10 23:09:44 EST 2012 (offset 2.543754s)
May 10 23:09:44 pfsense2 ntpd[50498]: no reply received in time, skipping initial time setting
May 10 23:09:44 pfsense2 ntpd[50779]: ntp engine exiting
May 10 23:09:44 pfsense2 ntpd[51062]: listening on 192.168.217.173
May 10 23:09:44 pfsense2 ntpd[51062]: ntp engine ready
May 10 23:09:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.000026 delay 0.000974, next query 8s
May 10 23:09:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.001123 delay 0.000579, next query 8s
May 10 23:10:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.002138 delay 0.000517, next query 7s
May 10 23:10:07 pfsense2 ntpd[51062]: peer 192.168.211.173 now valid
May 10 23:10:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.003023 delay 0.000494, next query 7s
May 10 23:10:14 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.003896 delay 0.000481, next query 7s
May 10 23:10:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.004773 delay 0.000493, next query 8s
May 10 23:10:29 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.005785 delay 0.000481, next query 31s
May 10 23:11:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.009660 delay 0.000545, next query 30s
May 10 23:11:00 pfsense2 ntpd[51007]: adjusting local clock by -0.005785s
May 10 23:11:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.007643 delay 0.000535, next query 32s
May 10 23:12:02 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.000216 delay 0.000538, next query 34s
May 10 23:12:36 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.012943 delay 0.000507, next query 32s
May 10 23:13:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.024931 delay 0.000570, next query 34s
May 10 23:13:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.037648 delay 0.000523, next query 30s
May 10 23:14:12 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.048891 delay 0.000559, next query 34s
May 10 23:14:46 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.061599 delay 0.000503, next query 31s
May 10 23:14:46 pfsense2 ntpd[51007]: adjusting local clock by 0.061599s
May 10 23:14:46 pfsense2 ntpd[51062]: clock is now synced
May 10 23:15:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.011714 delay 0.000492, next query 30s
May 10 23:15:47 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.022966 delay 0.000564, next query 34s
May 10 23:16:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.035677 delay 0.000484, next query 31s
May 10 23:16:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.046052 delay 0.000539, next query 30s
May 10 23:17:22 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.042270 delay 0.000537, next query 32s
May 10 23:17:54 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.038249 delay 0.000513, next query 33s
May 10 23:18:27 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.034094 delay 0.000514, next query 30s
May 10 23:18:57 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.030318 delay 0.000504, next query 30s
May 10 23:18:57 pfsense2 ntpd[51007]: adjusting local clock by 0.035677s
May 10 23:19:27 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.009066 delay 0.000487, next query 34s
May 10 23:20:01 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.013336 delay 0.000505, next query 33s
May 10 23:20:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.017537 delay 0.000564, next query 33s
May 10 23:21:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.012586 delay 0.000564, next query 31s
May 10 23:21:38 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.012605 delay 0.000429, next query 33s
May 10 23:22:11 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.000226 delay 0.000584, next query 33s
May 10 23:22:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.012100 delay 0.000467, next query 32s
May 10 23:23:16 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.024079 delay 0.000466, next query 31s
May 10 23:23:47 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.035678 delay 0.000466, next query 32s
May 10 23:23:47 pfsense2 ntpd[51007]: adjusting local clock by -0.012605s
May 10 23:24:19 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.060259 delay 0.000473, next query 30s
May 10 23:24:49 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.071490 delay 0.000493, next query 33s
May 10 23:25:22 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.083847 delay 0.000505, next query 34s
May 10 23:25:56 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.096563 delay 0.000501, next query 34s
May 10 23:25:56 pfsense2 ntpd[51007]: adjusting local clock by 0.036685s
May 10 23:26:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.072680 delay 0.000565, next query 32s
May 10 23:27:02 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.084605 delay 0.000430, next query 32s
May 10 23:27:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.096552 delay 0.000455, next query 34s
May 10 23:27:34 pfsense2 ntpd[51007]: adjusting local clock by 0.084605s
May 10 23:28:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.022379 delay 0.000515, next query 30s
May 10 23:28:38 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.033658 delay 0.000640, next query 31s
May 10 23:29:09 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.045105 delay 0.000577, next query 33s
May 10 23:29:43 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.058102 delay 0.000645, next query 34s
May 10 23:30:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.070758 delay 0.000506, next query 33s
May 10 23:30:50 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.082694 delay 0.000638, next query 31s
May 10 23:31:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.091798 delay 0.000532, next query 30s
May 10 23:31:21 pfsense2 ntpd[51007]: adjusting local clock by 0.011947s
May 10 23:31:51 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.076095 delay 0.000618, next query 30s
May 10 23:31:51 pfsense2 ntpd[51007]: adjusting local clock by 0.058811s
May 10 23:32:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.013942 delay 0.000457, next query 30s
May 10 23:32:51 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.010366 delay 0.000874, next query 31s
May 10 23:33:22 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.006279 delay 0.000522, next query 32s
May 10 23:33:54 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.001817 delay 0.000507, next query 33s
May 10 23:34:27 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.002359 delay 0.000448, next query 32s
May 10 23:34:27 pfsense2 ntpd[51007]: adjusting local clock by -0.002359s
May 10 23:34:59 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.003968 delay 0.000622, next query 31s
May 10 23:35:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.007925 delay 0.000485, next query 33s
May 10 23:36:03 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.012061 delay 0.000605, next query 33s
May 10 23:36:36 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.016231 delay 0.000497, next query 34s
May 10 23:37:10 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.023564 delay 0.000441, next query 32s
May 10 23:37:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.043588 delay 0.000468, next query 31s
May 10 23:38:13 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.062992 delay 0.000478, next query 33s
May 10 23:38:46 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.083648 delay 0.000465, next query 32s
May 10 23:38:46 pfsense2 ntpd[51007]: adjusting clock frequency by 216.056263 to 357.239857ppm
May 10 23:39:18 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.102244 delay 0.000464, next query 34s
May 10 23:39:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.113886 delay 0.000443, next query 34s
May 10 23:40:26 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.125506 delay 0.000420, next query 34s
May 10 23:41:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.137131 delay 0.000451, next query 30s
May 10 23:41:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.147393 delay 0.000435, next query 34s
May 10 23:41:30 pfsense2 ntpd[51007]: adjusting local clock by -0.023564s
May 10 23:42:04 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.135878 delay 0.000439, next query 32s
May 10 23:42:36 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.146394 delay 0.000453, next query 34s
May 10 23:43:10 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.158022 delay 0.000445, next query 32s
May 10 23:43:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.168956 delay 0.000482, next query 32s
May 10 23:44:14 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.179971 delay 0.000582, next query 31s
May 10 23:44:45 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.190499 delay 0.000483, next query 33s
May 10 23:44:45 pfsense2 ntpd[51007]: adjusting local clock by -0.125506s
May 10 23:45:18 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.076685 delay 0.000479, next query 30s
May 10 23:45:48 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.086946 delay 0.000437, next query 31s
May 10 23:45:48 pfsense2 ntpd[51007]: adjusting local clock by -0.115892s
May 10 23:45:48 pfsense2 ntpd[51062]: clock is now unsynced
May 10 23:46:19 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.075650 delay 0.000539, next query 31s
May 10 23:46:50 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.086263 delay 0.000473, next query 33s
May 10 23:47:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.097546 delay 0.000492, next query 30s
May 10 23:47:53 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.107818 delay 0.000443, next query 30s
May 10 23:48:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.118067 delay 0.000463, next query 31s
May 10 23:48:54 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.128668 delay 0.000459, next query 32s
May 10 23:49:26 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.139626 delay 0.000471, next query 34s
May 10 23:50:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.150800 delay 0.000504, next query 30s
May 10 23:50:00 pfsense2 ntpd[51007]: adjusting local clock by -0.086946s
May 10 23:50:00 pfsense2 ntpd[51062]: clock is now synced
May 10 23:50:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.074547 delay 0.000501, next query 32s
May 10 23:51:02 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.085514 delay 0.000443, next query 33s
May 10 23:51:35 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.096786 delay 0.000496, next query 34s
May 10 23:52:09 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.108427 delay 0.000443, next query 31s
May 10 23:52:09 pfsense2 ntpd[51007]: adjusting local clock by -0.130264s
May 10 23:52:09 pfsense2 ntpd[51062]: clock is now unsynced
May 10 23:52:40 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.011192 delay 0.000582, next query 33s
May 10 23:53:13 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.022501 delay 0.000457, next query 31s
May 10 23:53:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.033077 delay 0.000519, next query 30s
May 10 23:54:14 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.043363 delay 0.000446, next query 34s
May 10 23:54:48 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.054898 delay 0.000635, next query 33s
May 10 23:55:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.066270 delay 0.000467, next query 31s
May 10 23:55:21 pfsense2 ntpd[51007]: adjusting local clock by -0.119777s
May 10 23:55:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.008635 delay 0.000484, next query 30s
May 10 23:56:22 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.001618 delay 0.000462, next query 31s
May 10 23:56:22 pfsense2 ntpd[51007]: adjusting local clock by -0.112190s
May 10 23:56:53 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.010690 delay 0.000536, next query 30s
May 10 23:57:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.000413 delay 0.000484, next query 34s
May 10 23:57:57 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.011204 delay 0.000461, next query 34s
May 10 23:58:31 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.022832 delay 0.000448, next query 33s
May 10 23:58:31 pfsense2 ntpd[51007]: adjusting local clock by -0.068139s
May 10 23:59:04 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.013674 delay 0.000488, next query 34s
May 10 23:59:38 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.025303 delay 0.000478, next query 31s
May 11 00:00:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.035413 delay 0.000454, next query 34s
May 11 00:00:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.047023 delay 0.000515, next query 32s
May 11 00:01:14 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.057968 delay 0.000472, next query 30s
May 11 00:01:45 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.068236 delay 0.000454, next query 31s
May 11 00:02:16 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.078839 delay 0.000436, next query 31s
May 11 00:02:47 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.089443 delay 0.000442, next query 34s
May 11 00:02:47 pfsense2 ntpd[51007]: adjusting local clock by -0.022832s
May 11 00:02:47 pfsense2 ntpd[51062]: clock is now synced
May 11 00:03:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.078711 delay 0.000575, next query 32s
May 11 00:03:53 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.089188 delay 0.000442, next query 32s
May 11 00:04:25 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.100111 delay 0.000448, next query 32s
May 11 00:04:57 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.111041 delay 0.000518, next query 31s
May 11 00:05:28 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.121619 delay 0.000579, next query 32s
May 11 00:06:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.132604 delay 0.000455, next query 31s
May 11 00:06:31 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.143177 delay 0.000544, next query 33s
May 11 00:06:31 pfsense2 ntpd[51007]: adjusting local clock by -0.078839s
May 11 00:07:04 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.076118 delay 0.000481, next query 34s
May 11 00:07:04 pfsense2 ntpd[51007]: adjusting local clock by -0.072943s
May 11 00:07:04 pfsense2 ntpd[51062]: clock is now unsynced
May 11 00:07:38 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.077100 delay 0.000578, next query 32s
May 11 00:08:10 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.088092 delay 0.000462, next query 32s
May 11 00:08:10 pfsense2 ntpd[51007]: adjusting local clock by -0.118526s
May 11 00:08:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.020401 delay 0.000609, next query 34s
May 11 00:08:42 pfsense2 ntpd[51007]: adjusting local clock by -0.113449s
May 11 00:09:16 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.013354 delay 0.000458, next query 33s
May 11 00:09:49 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.024642 delay 0.000458, next query 32s
May 11 00:10:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.035564 delay 0.000544, next query 33s
May 11 00:10:21 pfsense2 ntpd[51007]: adjusting local clock by -0.096441s
May 11 00:10:53 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.013852 delay 0.000512, next query 33s
May 11 00:11:26 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.025131 delay 0.000560, next query 34s
May 11 00:12:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.036780 delay 0.000487, next query 30s
May 11 00:12:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.047038 delay 0.000458, next query 32s
May 11 00:13:02 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.057978 delay 0.000543, next query 33s
May 11 00:13:35 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.069275 delay 0.000478, next query 31s
May 11 00:14:06 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.079859 delay 0.000454, next query 34s
May 11 00:14:06 pfsense2 ntpd[51007]: adjusting local clock by -0.024642s
May 11 00:14:06 pfsense2 ntpd[51062]: clock is now synced
May 11 00:14:40 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.066843 delay 0.000496, next query 31s
May 11 00:15:11 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.077412 delay 0.000552, next query 31s
May 11 00:15:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.088026 delay 0.000506, next query 32s
May 11 00:16:14 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.098937 delay 0.000584, next query 30s
May 11 00:16:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.109221 delay 0.000486, next query 30s
May 11 00:17:14 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.119496 delay 0.000446, next query 32s
May 11 00:17:47 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.130416 delay 0.000525, next query 33s
May 11 00:18:20 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.141716 delay 0.000439, next query 30s
May 11 00:18:20 pfsense2 ntpd[51007]: adjusting local clock by -0.079859s
May 11 00:18:50 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.072611 delay 0.000470, next query 32s
May 11 00:19:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.083059 delay 0.000503, next query 33s
May 11 00:19:54 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.094313 delay 0.000543, next query 30s
May 11 00:20:24 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.104590 delay 0.000462, next query 33s
May 11 00:20:57 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.115880 delay 0.000521, next query 31s
May 11 00:21:28 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.126472 delay 0.000439, next query 34s
May 11 00:22:02 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.138105 delay 0.000489, next query 31s
May 11 00:22:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.148683 delay 0.000526, next query 31s
May 11 00:22:34 pfsense2 ntpd[51007]: adjusting local clock by -0.141716s
May 11 00:23:04 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.017590 delay 0.000434, next query 32s
May 11 00:23:36 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.028519 delay 0.000478, next query 34s
May 11 00:24:10 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.040161 delay 0.000477, next query 33s
May 11 00:24:43 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.051437 delay 0.000451, next query 34s
May 11 00:25:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.063103 delay 0.000513, next query 34s
May 11 00:25:51 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.074695 delay 0.000474, next query 33s
May 11 00:25:51 pfsense2 ntpd[51007]: adjusting local clock by -0.169688s
May 11 00:25:51 pfsense2 ntpd[51062]: clock is now unsynced
May 11 00:26:24 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.040488 delay 0.000450, next query 32s
May 11 00:26:56 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.029546 delay 0.000475, next query 34s
May 11 00:27:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.017904 delay 0.000474, next query 30s
May 11 00:27:30 pfsense2 ntpd[51007]: adjusting local clock by -0.137778s
May 11 00:28:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.025256 delay 0.000511, next query 34s
May 11 00:28:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.013686 delay 0.000562, next query 32s

and a few hours later

May 11 06:22:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.282812 delay 0.000530, next query 32s
May 11 06:22:40 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.293744 delay 0.000550, next query 30s
May 11 06:22:40 pfsense2 ntpd[51007]: adjusting local clock by -0.093768s
May 11 06:22:40 pfsense2 ntpd[51062]: clock is now synced
May 11 06:23:10 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.210488 delay 0.000566, next query 31s
May 11 06:23:41 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.205951 delay 0.000630, next query 34s
May 11 06:24:15 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.200633 delay 0.000492, next query 34s
May 11 06:24:49 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.195279 delay 0.000489, next query 31s
May 11 06:25:20 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.190395 delay 0.000439, next query 32s
May 11 06:25:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.185091 delay 0.000439, next query 31s
May 11 06:25:52 pfsense2 ntpd[51007]: adjusting local clock by -0.271629s
May 11 06:26:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.091169 delay 0.000503, next query 32s
May 11 06:26:55 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.082530 delay 0.000478, next query 34s
May 11 06:27:29 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.070885 delay 0.000461, next query 33s
May 11 06:28:02 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.059588 delay 0.000433, next query 33s
May 11 06:28:35 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.048310 delay 0.000514, next query 31s
May 11 06:29:06 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.037687 delay 0.000457, next query 31s
May 11 06:29:37 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.027066 delay 0.000495, next query 31s
May 11 06:30:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.016484 delay 0.000523, next query 33s
May 11 06:30:08 pfsense2 ntpd[51007]: adjusting local clock by -0.328719s
May 11 06:30:08 pfsense2 ntpd[51062]: clock is now unsynced
May 11 06:30:41 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.190255 delay 0.000504, next query 32s
May 11 06:31:13 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.179324 delay 0.000514, next query 31s
May 11 06:31:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.168705 delay 0.000509, next query 30s
May 11 06:32:14 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.158413 delay 0.000463, next query 33s
May 11 06:32:14 pfsense2 ntpd[51007]: adjusting local clock by -0.206130s
May 11 06:32:47 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.087531 delay 0.000438, next query 31s
May 11 06:33:18 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.076935 delay 0.000450, next query 30s
May 11 06:33:18 pfsense2 ntpd[51007]: adjusting local clock by -0.196030s
May 11 06:33:48 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.088585 delay 0.000543, next query 32s
May 11 06:34:20 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.077645 delay 0.000591, next query 34s
May 11 06:34:54 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.065966 delay 0.000454, next query 32s
May 11 06:35:26 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.055014 delay 0.000429, next query 34s
May 11 06:36:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.043374 delay 0.000485, next query 31s
May 11 06:36:31 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.032765 delay 0.000470, next query 30s
May 11 06:37:01 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 0.022494 delay 0.000449, next query 34s
May 11 06:37:01 pfsense2 ntpd[51007]: adjusting local clock by 0.003002s
May 11 06:37:35 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.076329 delay 0.000454, next query 34s
May 11 06:38:09 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.087969 delay 0.000465, next query 32s
May 11 06:38:41 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.098908 delay 0.000527, next query 34s
May 11 06:39:15 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.110554 delay 0.000476, next query 33s
May 11 06:39:48 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.121835 delay 0.000467, next query 32s
May 11 06:39:48 pfsense2 ntpd[51007]: adjusting local clock by 0.055014s
May 11 06:39:48 pfsense2 ntpd[51062]: clock is now synced
May 11 06:40:20 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.187333 delay 0.000859, next query 32s
May 11 06:40:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.198421 delay 0.000561, next query 32s
May 11 06:41:24 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.209339 delay 0.000626, next query 34s
May 11 06:41:24 pfsense2 ntpd[51007]: adjusting local clock by -0.025506s
May 11 06:41:24 pfsense2 ntpd[51062]: clock is now unsynced
May 11 06:41:58 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.189053 delay 0.000496, next query 32s
May 11 06:41:58 pfsense2 ntpd[51007]: adjusting local clock by -0.052316s
May 11 06:42:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.156210 delay 0.000462, next query 30s
May 11 06:42:30 pfsense2 ntpd[51007]: adjusting local clock by -0.047954s
May 11 06:43:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.150682 delay 0.000564, next query 30s
May 11 06:43:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.145928 delay 0.000636, next query 31s
May 11 06:44:01 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.141100 delay 0.000455, next query 32s
May 11 06:44:33 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.146796 delay 0.000645, next query 34s
May 11 06:45:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.158494 delay 0.000509, next query 31s
May 11 06:45:38 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -0.169112 delay 0.000462, next query 32s

I haven't looked into what this all means, but that the clock wanders in and out of sync every few minutes over a period of over six hours suggests some instability in the timekeeping.

wallabybob

I haven't been watching the ntp log as closely as I intended. At an uptime of about 30 hours the log shows

May 11 22:39:58 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -508.183479 delay 0.000470, next query 32s
May 11 22:39:58 pfsense2 ntpd[51007]: adjusting local clock by 191.008028s
May 11 22:40:31 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -222.807827 delay 0.000686, next query 33s
May 11 22:41:04 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -222.802611 delay 0.000519, next query 30s
May 11 22:41:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -222.797848 delay 0.000517, next query 34s
May 11 22:42:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -222.792472 delay 0.000478, next query 32s
May 11 22:42:08 pfsense2 ntpd[51007]: adjusting local clock by -317.873994s
May 11 22:42:41 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 285.441266 delay 0.000474, next query 34s
May 11 22:42:41 pfsense2 ntpd[51007]: adjusting local clock by -825.913256s
May 11 22:43:15 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.650885 delay 0.000469, next query 30s
May 11 22:43:45 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.642206 delay 0.000448, next query 33s
May 11 22:44:18 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.630895 delay 0.000430, next query 33s
May 11 22:44:18 pfsense2 ntpd[51007]: adjusting local clock by -825.423028s
May 11 22:44:50 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.619398 delay 0.000504, next query 31s
May 11 22:45:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.608780 delay 0.000546, next query 32s
May 11 22:45:53 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.597836 delay 0.000550, next query 32s
May 11 22:46:26 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.586532 delay 0.000499, next query 34s
May 11 22:47:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.575486 delay 0.000471, next query 31s
May 11 22:47:31 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.580382 delay 0.000481, next query 33s
May 11 22:48:03 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.590586 delay 0.000502, next query 32s
May 11 22:48:35 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 793.595640 delay 0.000509, next query 32s
May 11 22:48:35 pfsense2 ntpd[51007]: adjusting local clock by -824.122473s

and

May 12 03:42:56 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124363.969514 delay 0.000685, next query 33s
May 12 03:43:28 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124363.963105 delay 0.000453, next query 30s
May 12 03:43:58 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124363.952847 delay 0.000485, next query 31s
May 12 03:44:29 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124363.942219 delay 0.000433, next query 31s
May 12 03:45:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124363.931614 delay 0.000525, next query 33s
May 12 03:45:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124363.919966 delay 0.000454, next query 33s
May 12 03:46:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124363.908667 delay 0.000455, next query 34s
May 12 03:46:41 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124363.897024 delay 0.000475, next query 32s
May 12 03:46:41 pfsense2 ntpd[51007]: adjusting local clock by -124787.993983s
May 12 03:47:12 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124757.939061 delay 0.000444, next query 30s
May 12 03:47:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124757.928800 delay 0.000464, next query 34s
May 12 03:48:16 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124757.917142 delay 0.000415, next query 34s
May 12 03:48:51 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 124757.905181 delay 0.000471, next query 32s
May 12 03:48:51 pfsense2 ntpd[51007]: adjusting local clock by -50484.202414s
May 12 03:49:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 50454.752664 delay 0.000557, next query 34s
May 12 03:49:57 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 50454.741002 delay 0.000436, next query 32s
May 12 03:50:28 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 50454.735041 delay 0.000449, next query 32s
May 12 03:51:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 50454.724089 delay 0.000458, next query 30s
May 12 03:51:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 50454.713826 delay 0.000475, next query 31s
May 12 03:52:01 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 50454.703219 delay 0.000472, next query 34s
May 12 03:52:36 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 50454.691243 delay 0.000506, next query 31s
May 12 03:52:36 pfsense2 ntpd[51007]: adjusting local clock by 73880.864806s
May 12 03:53:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.255360 delay 0.000459, next query 32s
May 12 03:53:39 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.266273 delay 0.000521, next query 31s
May 12 03:54:10 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.276855 delay 0.000497, next query 32s
May 12 03:54:10 pfsense2 ntpd[51007]: adjusting local clock by 198638.311947s
May 12 03:54:43 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -198667.199919 delay 0.000579, next query 34s
May 12 03:54:43 pfsense2 ntpd[51007]: adjusting local clock by 249092.887949s
May 12 03:55:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.952526 delay 0.000544, next query 30s
May 12 03:55:17 pfsense2 ntpd[51007]: adjusting local clock by 249092.711987s
May 12 03:55:47 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.956831 delay 0.000462, next query 30s
May 12 03:56:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.967042 delay 0.000553, next query 33s
May 12 03:56:50 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.978336 delay 0.000513, next query 34s
May 12 03:57:24 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.989943 delay 0.000489, next query 34s
May 12 03:57:24 pfsense2 ntpd[51007]: adjusting local clock by 249092.066034s
May 12 03:57:59 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.985615 delay 0.000465, next query 31s
May 12 03:58:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.996188 delay 0.000510, next query 32s
May 12 03:59:02 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249122.007130 delay 0.000465, next query 31s
May 12 03:59:33 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249122.017701 delay 0.000466, next query 34s
May 12 04:00:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249122.029323 delay 0.000485, next query 32s
May 12 04:00:07 pfsense2 ntpd[51007]: adjusting local clock by 175182.012587s
May 12 04:00:39 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.801790 delay 0.000496, next query 33s
May 12 04:01:13 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.808030 delay 0.000584, next query 31s
May 12 04:01:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.818617 delay 0.000602, next query 32s
May 12 04:02:16 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.829545 delay 0.000573, next query 34s
May 12 04:02:16 pfsense2 ntpd[51007]: adjusting local clock by -73940.589244s
May 12 04:02:50 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 73909.109770 delay 0.000468, next query 33s
May 12 04:03:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 73909.098461 delay 0.000439, next query 32s
May 12 04:03:23 pfsense2 ntpd[51007]: adjusting local clock by -323062.239858s
May 12 04:03:54 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323031.078105 delay 0.000460, next query 32s
May 12 04:04:26 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323031.067174 delay 0.000478, next query 30s
May 12 04:04:56 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323031.056886 delay 0.000442, next query 30s
May 12 04:05:27 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323031.046271 delay 0.000454, next query 33s
May 12 04:06:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323031.035162 delay 0.000834, next query 34s
May 12 04:06:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323031.023322 delay 0.000443, next query 34s
May 12 04:07:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323031.011714 delay 0.000587, next query 30s
May 12 04:07:37 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323031.006456 delay 0.000601, next query 30s
May 12 04:07:37 pfsense2 ntpd[51007]: adjusting local clock by -323060.991372s
May 12 04:08:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323031.017668 delay 0.000512, next query 33s
May 12 04:08:40 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323031.006349 delay 0.000484, next query 33s
May 12 04:09:14 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 323030.994709 delay 0.000449, next query 30s
May 12 04:09:14 pfsense2 ntpd[51007]: adjusting local clock by -249151.407911s
May 12 04:09:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 249121.885974 delay 0.000484, next query 33s
May 12 04:10:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 249121.874662 delay 0.000441, next query 30s
May 12 04:10:46 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 249121.869394 delay 0.000478, next query 34s
May 12 04:10:46 pfsense2 ntpd[51007]: adjusting local clock by 73880.108976s
May 12 04:11:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.194042 delay 0.000465, next query 33s
May 12 04:11:54 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.190823 delay 0.000587, next query 33s
May 12 04:12:27 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.185617 delay 0.000496, next query 32s
May 12 04:12:59 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.180535 delay 0.000551, next query 33s
May 12 04:13:32 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.175133 delay 0.000826, next query 34s
May 12 04:14:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.164950 delay 0.000456, next query 34s
May 12 04:14:41 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.159555 delay 0.000432, next query 30s
May 12 04:14:41 pfsense2 ntpd[51007]: adjusting local clock by 73878.900411s
May 12 04:15:11 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.121240 delay 0.000443, next query 33s
May 12 04:15:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.115993 delay 0.000486, next query 33s
May 12 04:16:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.110768 delay 0.000484, next query 34s
May 12 04:16:51 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.105388 delay 0.000475, next query 31s
May 12 04:17:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.095476 delay 0.000450, next query 32s
May 12 04:17:55 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.090413 delay 0.000444, next query 33s
May 12 04:18:28 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.093246 delay 0.000476, next query 32s
May 12 04:19:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -73909.104167 delay 0.000471, next query 34s
May 12 04:19:00 pfsense2 ntpd[51007]: adjusting local clock by 322999.480073s
May 12 04:19:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323030.990413 delay 0.000579, next query 34s
May 12 04:19:34 pfsense2 ntpd[51007]: adjusting local clock by 249090.150518s
May 12 04:20:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.842489 delay 0.000536, next query 30s
May 12 04:20:39 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.847747 delay 0.000485, next query 33s
May 12 04:21:12 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.844980 delay 0.000449, next query 31s
May 12 04:21:43 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.840062 delay 0.000493, next query 30s
May 12 04:22:13 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -249121.835335 delay 0.000511, next query 33s
May 12 04:22:13 pfsense2 ntpd[51007]: adjusting local clock by 175180.234277s
May 12 04:22:46 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.708857 delay 0.000480, next query 33s
May 12 04:23:19 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.703611 delay 0.000497, next query 33s
May 12 04:23:53 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.693394 delay 0.000465, next query 34s
May 12 04:24:27 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.687997 delay 0.000485, next query 33s
May 12 04:25:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.682783 delay 0.000428, next query 30s
May 12 04:25:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.677984 delay 0.000578, next query 30s
May 12 04:25:30 pfsense2 ntpd[51007]: adjusting local clock by 175179.280104s
May 12 04:26:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.704085 delay 0.000503, next query 30s
May 12 04:26:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.699343 delay 0.000490, next query 32s
May 12 04:27:03 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.697457 delay 0.000516, next query 32s
May 12 04:27:35 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.708391 delay 0.000515, next query 30s
May 12 04:28:05 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.718652 delay 0.000485, next query 34s
May 12 04:28:39 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.730252 delay 0.000492, next query 34s
May 12 04:29:13 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -175212.739737 delay 0.000553, next query 31s
May 12 04:29:13 pfsense2 ntpd[51007]: adjusting local clock by -73943.679877s
May 12 04:29:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 73909.108046 delay 0.000484, next query 30s
May 12 04:30:15 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 73909.112906 delay 0.000494, next query 34s
May 12 04:30:49 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 73909.112638 delay 0.000461, next query 30s
May 12 04:31:19 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 73909.102374 delay 0.000452, next query 34s
May 12 04:31:53 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 73909.090730 delay 0.000499, next query 30s
May 12 04:32:22 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 73909.085452 delay 0.000465, next query 30s
May 12 04:32:22 pfsense2 ntpd[51007]: adjusting local clock by -249155.417659s
May 12 04:32:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 249121.758001 delay 0.000565, next query 34s
May 12 04:33:26 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 249121.746339 delay 0.000521, next query 34s
May 12 04:34:01 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 249121.734375 delay 0.000596, next query 32s
May 12 04:34:33 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 249121.723370 delay 0.000416, next query 34s
May 12 04:35:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 249121.711717 delay 0.000465, next query 34s
May 12 04:35:40 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 249121.705083 delay 0.000448, next query 33s
May 12 04:35:40 pfsense2 ntpd[51007]: adjusting local clock by -424367.146310s
May 12 04:36:13 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 424334.412419 delay 0.000452, next query 31s
May 12 04:36:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 424334.401812 delay 0.000459, next query 34s
May 12 04:37:19 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 424334.389830 delay 0.000431, next query 30s
May 12 04:37:49 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 424334.379558 delay 0.000438, next query 34s
May 12 04:38:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 424334.367903 delay 0.000462, next query 34s
May 12 04:38:57 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 424334.356253 delay 0.000491, next query 34s
May 12 04:38:57 pfsense2 ntpd[51007]: adjusting local clock by -350457.058935s
May 12 04:39:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 350425.247241 delay 0.000456, next query 34s
May 12 04:40:04 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 350425.235620 delay 0.000509, next query 31s
May 12 04:40:35 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 350425.224983 delay 0.000472, next query 34s
May 12 04:41:10 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 350425.212985 delay 0.000471, next query 34s
May 12 04:41:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 350425.201359 delay 0.000442, next query 34s
May 12 04:41:44 pfsense2 ntpd[51007]: adjusting local clock by -101334.500564s
May 12 04:42:18 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 101303.466362 delay 0.000505, next query 34s
May 12 04:42:18 pfsense2 ntpd[51007]: adjusting local clock by 323000.059267s
May 12 04:42:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323030.925734 delay 0.000486, next query 33s
May 12 04:43:25 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323030.936996 delay 0.000493, next query 32s
May 12 04:43:57 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323030.947937 delay 0.000478, next query 34s
May 12 04:44:31 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323030.958840 delay 0.001892, next query 30s
May 12 04:45:01 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323030.969778 delay 0.000585, next query 30s
May 12 04:45:32 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323030.975050 delay 0.000511, next query 34s
May 12 04:46:06 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323030.986670 delay 0.000466, next query 30s
May 12 04:46:06 pfsense2 ntpd[51007]: adjusting local clock by 322998.908994s
May 12 04:46:36 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323030.986578 delay 0.000603, next query 30s
May 12 04:47:06 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323030.996871 delay 0.000559, next query 31s
May 12 04:47:37 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323031.007461 delay 0.000518, next query 32s
May 12 04:48:09 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323031.018382 delay 0.000528, next query 30s
May 12 04:48:40 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323031.023637 delay 0.000512, next query 33s
May 12 04:49:13 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323031.034898 delay 0.000533, next query 31s
May 12 04:49:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323031.045502 delay 0.000472, next query 33s
May 12 04:50:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -323031.056767 delay 0.000497, next query 30s
May 12 04:50:17 pfsense2 ntpd[51007]: adjusting local clock by 673422.865624s
May 12 04:50:47 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -673456.278636 delay 0.000508, next query 32s
May 12 04:51:19 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -673456.289567 delay 0.000495, next query 31s
May 12 04:51:51 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -673456.295157 delay 0.000502, next query 34s
May 12 04:52:25 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -673456.306767 delay 0.000512, next query 32s
May 12 04:52:57 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -673456.317493 delay 0.000824, next query 30s
May 12 04:53:27 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -673456.327953 delay 0.000482, next query 33s
May 12 04:54:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -673456.339156 delay 0.000660, next query 33s
May 12 04:54:00 pfsense2 ntpd[51007]: adjusting local clock by 350390.763954s
May 12 04:54:33 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -350425.363833 delay 0.000470, next query 33s
May 12 04:55:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -350425.370101 delay 0.000449, next query 30s
May 12 04:55:37 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -350425.380341 delay 0.000476, next query 34s
May 12 04:56:11 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -350425.393788 delay 0.000460, next query 31s
May 12 04:56:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -350425.404373 delay 0.000456, next query 30s
May 12 04:57:12 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -350425.414576 delay 0.000591, next query 32s
May 12 04:57:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -350425.425519 delay 0.000547, next query 34s
May 12 04:57:44 pfsense2 ntpd[51007]: adjusting local clock by 27358.598451s
May 12 04:58:19 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -27394.386638 delay 0.000556, next query 33s
May 12 04:58:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -27394.397928 delay 0.000447, next query 32s
May 12 04:59:24 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -27394.408846 delay 0.000527, next query 34s
May 12 04:59:24 pfsense2 ntpd[51007]: adjusting local clock by -646098.229503s
May 12 04:59:58 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 646061.901898 delay 0.000573, next query 30s
May 12 05:00:28 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 646061.891585 delay 0.000456, next query 34s
May 12 05:01:01 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 646061.884972 delay 0.000564, next query 34s
May 12 05:01:35 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 646061.873302 delay 0.000493, next query 32s
May 12 05:02:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 646061.862312 delay 0.000466, next query 34s
May 12 05:02:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 646061.850363 delay 0.000539, next query 34s
May 12 05:03:16 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 646061.838707 delay 0.000485, next query 31s
May 12 05:03:16 pfsense2 ntpd[51007]: adjusting local clock by -996522.439604s
May 12 05:03:47 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 996487.198217 delay 0.000573, next query 32s
May 12 05:04:19 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 996487.187205 delay 0.000472, next query 32s
May 12 05:04:50 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 996487.181247 delay 0.000453, next query 33s
May 12 05:04:50 pfsense2 ntpd[51007]: adjusting local clock by -1023916.367531s
May 12 05:05:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 1023881.567874 delay 0.000538, next query 34s
May 12 05:05:57 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 1023881.556228 delay 0.000453, next query 34s
May 12 05:06:32 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 1023881.544249 delay 0.000508, next query 30s
May 12 05:07:02 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 1023881.533979 delay 0.000524, next query 34s
May 12 05:07:36 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 1023881.522301 delay 0.000536, next query 32s
May 12 05:08:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 1023881.516359 delay 0.000509, next query 30s
May 12 05:08:37 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 1023881.506059 delay 0.000463, next query 31s
May 12 05:09:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 1023881.495439 delay 0.000471, next query 33s
May 12 05:09:08 pfsense2 ntpd[51007]: adjusting local clock by -377853.185946s
May 12 05:09:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 377819.592215 delay 0.000495, next query 30s
May 12 05:10:12 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 377819.581954 delay 0.000533, next query 32s
May 12 05:10:12 pfsense2 ntpd[51007]: adjusting local clock by 618634.315302s
May 12 05:10:44 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -618667.603888 delay 0.000489, next query 33s
May 12 05:11:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -618667.615162 delay 0.000528, next query 30s
May 12 05:11:47 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -618667.625416 delay 0.000447, next query 31s
May 12 05:12:19 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -618667.630960 delay 0.000638, next query 32s
May 12 05:12:51 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -618667.641916 delay 0.000575, next query 31s
May 12 05:12:51 pfsense2 ntpd[51007]: adjusting local clock by 1642515.076529s
May 12 05:13:22 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1642549.208758 delay 0.000502, next query 30s
May 12 05:13:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1642549.219019 delay 0.000455, next query 33s
May 12 05:14:25 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1642549.230270 delay 0.000530, next query 31s
May 12 05:14:56 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1642549.240870 delay 0.000473, next query 34s
May 12 05:15:31 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1642549.247488 delay 0.000547, next query 34s
May 12 05:16:05 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1642549.259101 delay 0.000474, next query 32s
May 12 05:16:05 pfsense2 ntpd[51007]: adjusting local clock by 1642514.056360s
May 12 05:16:37 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1642549.219858 delay 0.000506, next query 34s
May 12 05:17:11 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1642549.231431 delay 0.000621, next query 32s
May 12 05:17:43 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1642549.242391 delay 0.000572, next query 34s
May 12 05:18:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1642549.254033 delay 0.000465, next query 33s
May 12 05:18:17 pfsense2 ntpd[51007]: adjusting local clock by 1023845.770944s
May 12 05:18:51 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1023881.634886 delay 0.000439, next query 32s
May 12 05:19:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1023881.645818 delay 0.000444, next query 31s
May 12 05:19:54 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1023881.656404 delay 0.000463, next query 31s
May 12 05:20:25 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1023881.666995 delay 0.000474, next query 31s
May 12 05:20:56 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1023881.677572 delay 0.000513, next query 34s
May 12 05:21:30 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1023881.689212 delay 0.000438, next query 33s
May 12 05:22:04 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1023881.695455 delay 0.000552, next query 34s
May 12 05:22:38 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1023881.711495 delay 0.010353, next query 32s
May 12 05:22:38 pfsense2 ntpd[51007]: adjusting local clock by -618704.753075s
May 12 05:23:10 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 618667.493768 delay 0.000459, next query 30s
May 12 05:23:39 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 618667.488487 delay 0.000476, next query 33s
May 12 05:24:12 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 618667.477194 delay 0.000554, next query 31s
May 12 05:24:43 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 618667.466568 delay 0.000508, next query 32s
May 12 05:25:15 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 618667.455616 delay 0.000547, next query 32s
May 12 05:25:48 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 618667.444293 delay 0.000488, next query 34s
May 12 05:25:48 pfsense2 ntpd[51007]: adjusting local clock by -2261253.057107s
May 12 05:26:22 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 2261216.686668 delay 0.000412, next query 33s
May 12 05:26:55 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 2261216.675361 delay 0.000429, next query 31s
May 12 05:27:25 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 2261216.669754 delay 0.000461, next query 33s
May 12 05:27:25 pfsense2 ntpd[51007]: adjusting local clock by -3285134.261319s
May 12 05:27:58 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 3285098.347664 delay 0.000486, next query 34s
May 12 05:28:32 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 3285098.335909 delay 0.000628, next query 31s
May 12 05:29:04 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 3285098.325063 delay 0.000513, next query 30s
May 12 05:29:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 3285098.314776 delay 0.000468, next query 32s
May 12 05:30:06 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 3285098.303796 delay 0.000447, next query 30s
May 12 05:30:36 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 3285098.293520 delay 0.000494, next query 30s
May 12 05:30:36 pfsense2 ntpd[51007]: adjusting local clock by -2666465.812551s
May 12 05:31:05 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 2666430.794483 delay 0.000440, next query 33s
May 12 05:31:05 pfsense2 ntpd[51007]: adjusting local clock by -405248.980882s
May 12 05:31:38 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.096614 delay 0.000706, next query 31s
May 12 05:32:09 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.085887 delay 0.000438, next query 31s
May 12 05:32:41 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.077928 delay 0.000456, next query 33s
May 12 05:33:14 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.083123 delay 0.000457, next query 34s
May 12 05:33:48 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.088468 delay 0.000443, next query 30s
May 12 05:34:17 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.098199 delay 0.000461, next query 33s
May 12 05:34:50 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.103382 delay 0.000436, next query 34s
May 12 05:35:24 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.108739 delay 0.000463, next query 32s
May 12 05:35:24 pfsense2 ntpd[51007]: adjusting local clock by -405247.697189s
May 12 05:35:57 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.125247 delay 0.000441, next query 32s
May 12 05:36:29 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.130290 delay 0.000485, next query 32s
May 12 05:37:01 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.135454 delay 0.000710, next query 33s
May 12 05:37:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.140516 delay 0.000500, next query 33s
May 12 05:38:06 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.135790 delay 0.000485, next query 34s
May 12 05:38:40 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.124147 delay 0.000485, next query 30s
May 12 05:39:10 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 405214.113862 delay 0.000493, next query 31s
May 12 05:39:10 pfsense2 ntpd[51007]: adjusting local clock by 2261184.227295s
May 12 05:39:41 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -2261216.686954 delay 0.000510, next query 30s
May 12 05:40:11 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -2261216.697226 delay 0.000455, next query 30s
May 12 05:40:11 pfsense2 ntpd[51007]: adjusting local clock by 2666398.025677s
May 12 05:40:42 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -2666430.805815 delay 0.000599, next query 33s
May 12 05:41:15 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -2666430.808561 delay 0.000470, next query 34s
May 12 05:41:49 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -2666430.803183 delay 0.000523, next query 34s
May 12 05:42:23 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -2666430.797770 delay 0.000563, next query 30s
May 12 05:42:53 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -2666430.793041 delay 0.000570, next query 34s
May 12 05:43:27 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -2666430.787671 delay 0.000480, next query 32s
May 12 05:44:00 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -2666430.777595 delay 0.000474, next query 34s
May 12 05:44:34 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -2666430.772225 delay 0.000453, next query 34s
May 12 05:44:34 pfsense2 ntpd[51007]: adjusting local clock by 3071610.835924s
May 12 05:45:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: not synced (alarm), next query 3130s

dhatz

May 12 04:27:56 fw ntpd[44064]: ntp engine ready
May 12 04:27:56 fw ntpd[44064]: reply from 79.107.99.220: offset 0.770593 delay 0.017599, next query 7s
May 12 04:27:56 fw ntpd[44064]: reply from 194.177.210.54: offset 0.774162 delay 0.019691, next query 6s
May 12 04:27:57 fw ntpd[43932]: set local clock to Sat May 12 04:27:57 EEST 2012 (offset 0.770593s)
May 12 04:27:57 fw ntpd[43932]: no reply received in time, skipping initial time setting
May 12 04:27:57 fw ntpd[44064]: ntp engine exiting
May 12 04:27:57 fw ntpd[44552]: ntp engine ready
May 12 04:27:57 fw ntpd[44552]: reply from 79.107.99.220: offset 0.000240 delay 0.017734, next query 9s
May 12 04:27:57 fw ntpd[44552]: reply from 194.177.210.54: offset 0.004508 delay 0.018784, next query 7s
May 12 04:27:57 fw ntpd[44552]: reply from 192.108.114.23: offset 0.005046 delay 0.039272, next query 8s
May 12 04:27:58 fw ntpd[44552]: ntp_dispatch_imsg_dns in ntp engine: pipe closed
May 12 04:27:58 fw ntpd[44552]: ntp engine exiting
May 12 04:27:58 fw ntpd[44345]: dispatch_imsg in main: pipe closed
May 12 04:27:58 fw ntpd[44345]: Lost child: child exited
May 12 04:27:58 fw ntpd[44345]: Terminating
May 12 04:27:58 fw ntpd[49361]: ntp engine ready
May 12 04:27:58 fw ntpd[49361]: reply from 79.107.99.220: offset -0.000033 delay 0.017815, next query 8s
May 12 04:27:58 fw ntpd[49361]: reply from 194.177.210.54: offset 0.003868 delay 0.019986, next query 8s
May 12 04:27:58 fw ntpd[49298]: set local clock to Sat May 12 04:27:58 EEST 2012 (offset -0.000033s)
May 12 04:27:58 fw ntpd[49298]: no reply received in time, skipping initial time setting
May 12 04:27:58 fw ntpd[49361]: ntp engine exiting
May 12 04:27:58 fw ntpd[49639]: ntp engine ready
May 12 04:27:58 fw ntpd[49639]: reply from 79.107.99.220: offset -0.000798 delay 0.017132, next query 7s
May 12 04:27:58 fw ntpd[49639]: reply from 194.177.210.54: offset 0.003582 delay 0.016776, next query 8s
May 12 04:27:58 fw ntpd[49639]: reply from 192.108.114.23: offset 0.004120 delay 0.037525, next query 7s
May 12 04:28:05 fw ntpd[49639]: reply from 79.107.99.220: offset -0.004370 delay 0.016132, next query 6s
May 12 04:28:05 fw ntpd[49639]: reply from 192.108.114.23: offset -0.000400 delay 0.037696, next query 8s
May 12 04:28:06 fw ntpd[49639]: reply from 194.177.210.54: offset -0.001225 delay 0.017436, next query 5s
May 12 04:28:11 fw ntpd[49639]: reply from 79.107.99.220: offset -0.007383 delay 0.016419, next query 8s
May 12 04:28:11 fw ntpd[49639]: reply from 194.177.210.54: offset -0.003733 delay 0.017761, next query 7s
May 12 04:28:13 fw ntpd[49639]: reply from 192.108.114.23: offset -0.005322 delay 0.035420, next query 6s
May 12 04:28:18 fw ntpd[49639]: peer 194.177.210.54 now valid
May 12 04:28:18 fw ntpd[49639]: reply from 194.177.210.54: offset -0.007695 delay 0.015995, next query 5s
May 12 04:28:19 fw ntpd[49639]: peer 79.107.99.220 now valid
May 12 04:28:19 fw ntpd[49639]: reply from 79.107.99.220: offset -0.011771 delay 0.016599, next query 8s
May 12 04:28:19 fw ntpd[49639]: peer 192.108.114.23 now valid
May 12 04:28:19 fw ntpd[49639]: reply from 192.108.114.23: offset -0.007601 delay 0.036809, next query 8s
May 12 04:28:23 fw ntpd[49639]: reply from 194.177.210.54: offset -0.010548 delay 0.015997, next query 7s
May 12 04:28:27 fw ntpd[49639]: reply from 79.107.99.220: offset -0.016080 delay 0.016232, next query 6s
May 12 04:28:27 fw ntpd[49639]: reply from 192.108.114.23: offset -0.012152 delay 0.036406, next query 6s
May 12 04:28:29 fw ntpd[49639]: reply from 194.177.210.54: offset -0.013352 delay 0.015710, next query 8s
May 12 04:28:32 fw ntpd[49639]: reply from 79.107.99.220: offset -0.018594 delay 0.015621, next query 6s
May 12 04:28:33 fw ntpd[49639]: reply from 192.108.114.23: offset -0.016145 delay 0.035643, next query 5s
May 12 04:28:37 fw ntpd[49639]: reply from 194.177.210.54: offset -0.018003 delay 0.015484, next query 33s
May 12 04:28:38 fw ntpd[49639]: reply from 79.107.99.220: offset -0.021904 delay 0.015574, next query 30s
May 12 04:28:38 fw ntpd[49639]: reply from 192.108.114.23: offset -0.018043 delay 0.036050, next query 31s
May 12 04:29:08 fw ntpd[49639]: reply from 79.107.99.220: offset -0.038343 delay 0.016934, next query 34s
May 12 04:29:09 fw ntpd[49639]: reply from 192.108.114.23: offset -0.035152 delay 0.034785, next query 33s
May 12 04:29:10 fw ntpd[49639]: reply from 194.177.210.54: offset -0.035222 delay 0.016800, next query 32s
May 12 04:29:10 fw ntpd[49598]: adjusting local clock by -0.021904s
May 12 04:29:42 fw ntpd[49639]: reply from 79.107.99.220: offset -0.034412 delay 0.017323, next query 32s
May 12 04:29:42 fw ntpd[49639]: reply from 194.177.210.54: offset -0.029968 delay 0.019371, next query 32s
May 12 04:29:43 fw ntpd[49639]: reply from 192.108.114.23: offset -0.029037 delay 0.040293, next query 32s
May 12 04:30:15 fw ntpd[49639]: reply from 79.107.99.220: offset -0.050428 delay 0.017310, next query 30s
May 12 04:30:15 fw ntpd[49639]: reply from 194.177.210.54: offset -0.046264 delay 0.017464, next query 32s
May 12 04:30:15 fw ntpd[49639]: reply from 192.108.114.23: offset -0.046320 delay 0.039055, next query 30s
May 12 04:30:45 fw ntpd[49639]: reply from 79.107.99.220: offset -0.067086 delay 0.017133, next query 34s
May 12 04:30:45 fw ntpd[49639]: reply from 192.108.114.23: offset -0.062367 delay 0.036528, next query 30s
May 12 04:30:47 fw ntpd[49639]: reply from 194.177.210.54: offset -0.064523 delay 0.015687, next query 32s
May 12 04:31:15 fw ntpd[49639]: reply from 192.108.114.23: offset -0.079434 delay 0.034785, next query 33s
May 12 04:31:19 fw ntpd[49639]: reply from 79.107.99.220: offset -0.085590 delay 0.016697, next query 31s
May 12 04:31:19 fw ntpd[49639]: reply from 194.177.210.54: offset -0.081032 delay 0.016899, next query 30s
May 12 04:31:48 fw ntpd[49639]: reply from 192.108.114.23: offset -0.096437 delay 0.036486, next query 34s
May 12 04:31:49 fw ntpd[49639]: reply from 194.177.210.54: offset -0.097571 delay 0.016769, next query 33s
May 12 04:31:50 fw ntpd[49639]: reply from 79.107.99.220: offset -0.101961 delay 0.017051, next query 34s
May 12 04:32:22 fw ntpd[49639]: reply from 194.177.210.54: offset -0.130778 delay 0.048954, next query 33s
May 12 04:32:22 fw ntpd[49639]: reply from 192.108.114.23: offset -0.120312 delay 0.049504, next query 32s
May 12 04:32:24 fw ntpd[49639]: reply from 79.107.99.220: offset -0.119948 delay 0.015944, next query 33s
May 12 04:32:54 fw ntpd[49639]: reply from 192.108.114.23: offset -0.131749 delay 0.034900, next query 30s
May 12 04:32:55 fw ntpd[49639]: reply from 194.177.210.54: offset -0.132374 delay 0.016587, next query 30s
May 12 04:32:55 fw ntpd[49598]: adjusting local clock by -0.064523s
May 12 04:32:55 fw ntpd[49639]: clock is now synced
May 12 04:32:57 fw ntpd[49639]: reply from 79.107.99.220: offset -0.073215 delay 0.015708, next query 34s
May 12 04:33:24 fw ntpd[49639]: reply from 192.108.114.23: offset -0.083783 delay 0.036279, next query 31s
May 12 04:33:25 fw ntpd[49639]: reply from 194.177.210.54: offset -0.084345 delay 0.015916, next query 34s
May 12 04:33:31 fw ntpd[49639]: reply from 79.107.99.220: offset -0.090948 delay 0.016019, next query 34s
May 12 04:33:54 fw ntpd[49639]: reply from 192.108.114.23: offset -0.099368 delay 0.034954, next query 32s
May 12 04:33:58 fw ntpd[49639]: reply from 194.177.210.54: offset -0.101245 delay 0.017548, next query 33s
May 12 04:34:05 fw ntpd[49639]: reply from 79.107.99.220: offset -0.109434 delay 0.016188, next query 31s
May 12 04:34:26 fw ntpd[49639]: reply from 192.108.114.23: offset -0.116094 delay 0.036366, next query 30s
May 12 04:34:31 fw ntpd[49639]: reply from 194.177.210.54: offset -0.118553 delay 0.016552, next query 31s
May 12 04:34:36 fw ntpd[49639]: reply from 79.107.99.220: offset -0.126086 delay 0.017467, next query 30s
May 12 04:34:56 fw ntpd[49639]: reply from 192.108.114.23: offset -0.132378 delay 0.035698, next query 31s
May 12 04:35:02 fw ntpd[49639]: reply from 194.177.210.54: offset -0.135289 delay 0.016183, next query 30s
May 12 04:35:02 fw ntpd[49598]: adjusting local clock by -0.074237s
May 12 04:35:02 fw ntpd[49639]: clock is now unsynced
May 12 04:35:06 fw ntpd[49639]: reply from 79.107.99.220: offset -0.068319 delay 0.015998, next query 30s
May 12 04:35:27 fw ntpd[49639]: reply from 192.108.114.23: offset -0.074855 delay 0.035540, next query 31s
May 12 04:35:33 fw ntpd[49639]: reply from 194.177.210.54: offset -0.078387 delay 0.016447, next query 30s
May 12 04:35:37 fw ntpd[49639]: reply from 79.107.99.220: offset -0.085210 delay 0.017066, next query 33s
May 12 04:35:59 fw ntpd[49639]: reply from 192.108.114.23: offset -0.091670 delay 0.035482, next query 32s
May 12 04:36:03 fw ntpd[49639]: reply from 194.177.210.54: offset -0.094008 delay 0.015849, next query 30s
May 12 04:36:10 fw ntpd[49639]: reply from 79.107.99.220: offset -0.102647 delay 0.017510, next query 32s
May 12 04:36:42 fw ntpd[49639]: reply from 79.107.99.220: offset -0.119095 delay 0.016107, next query 30s
May 12 04:36:46 fw ntpd[49639]: no reply from 192.108.114.23 received in time, next query 300s
May 12 04:36:46 fw ntpd[49639]: peer 192.108.114.23 now invalid
May 12 04:36:48 fw ntpd[49639]: 2 out of 3 peers valid
May 12 04:36:48 fw ntpd[49639]: bad peer from pool gr.pool.ntp.org (192.108.114.23)
May 12 04:36:48 fw ntpd[49639]: no reply from 194.177.210.54 received in time, next query 300s
May 12 04:36:48 fw ntpd[49639]: peer 194.177.210.54 now invalid
May 12 04:37:12 fw ntpd[49639]: reply from 79.107.99.220: offset -0.135306 delay 0.017791, next query 33s
May 12 04:37:12 fw ntpd[49598]: adjusting local clock by -0.077555s
May 12 04:37:45 fw ntpd[49639]: reply from 79.107.99.220: offset -0.084594 delay 0.017305, next query 33s
May 12 04:38:18 fw ntpd[49639]: reply from 79.107.99.220: offset -0.101806 delay 0.016130, next query 32s
May 12 04:38:50 fw ntpd[49639]: reply from 79.107.99.220: offset -0.118886 delay 0.016409, next query 34s
May 12 04:39:24 fw ntpd[49639]: reply from 79.107.99.220: offset -0.136448 delay 0.017717, next query 31s
May 12 04:39:24 fw ntpd[49598]: adjusting local clock by -0.062331s
May 12 04:39:55 fw ntpd[49639]: reply from 79.107.99.220: offset -0.109751 delay 0.032519, next query 34s
May 12 04:40:29 fw ntpd[49639]: reply from 79.107.99.220: offset -0.121216 delay 0.016206, next query 30s
May 12 04:40:59 fw ntpd[49639]: reply from 79.107.99.220: offset -0.136465 delay 0.017057, next query 33s
May 12 04:40:59 fw ntpd[49598]: adjusting local clock by -0.065861s
May 12 04:41:32 fw ntpd[49639]: reply from 79.107.99.220: offset -0.103222 delay 0.017493, next query 32s
May 12 04:41:46 fw ntpd[49639]: reply from 192.108.114.23: offset -0.105240 delay 0.036683, next query 7s
May 12 04:41:48 fw ntpd[49639]: reply from 194.177.210.54: offset -0.106383 delay 0.016372, next query 5s
May 12 04:41:53 fw ntpd[49639]: reply from 194.177.210.54: offset -0.099407 delay 0.036994, next query 8s
May 12 04:41:53 fw ntpd[49639]: reply from 192.108.114.23: offset -0.098624 delay 0.057531, next query 8s
May 12 04:42:01 fw ntpd[49639]: reply from 194.177.210.54: offset -0.082838 delay 0.077395, next query 5s
May 12 04:42:01 fw ntpd[49639]: reply from 192.108.114.23: offset -0.082315 delay 0.098382, next query 7s
May 12 04:42:03 fw ntpd[49639]: reply from 79.107.99.220: offset -0.114091 delay 0.027838, next query 34s
May 12 04:42:06 fw ntpd[49639]: peer 194.177.210.54 now valid
May 12 04:42:06 fw ntpd[49639]: reply from 194.177.210.54: offset -0.116900 delay 0.017441, next query 5s
May 12 04:42:08 fw ntpd[49639]: peer 192.108.114.23 now valid
May 12 04:42:08 fw ntpd[49639]: reply from 192.108.114.23: offset -0.117321 delay 0.035494, next query 8s
May 12 04:42:11 fw ntpd[49639]: reply from 194.177.210.54: offset -0.119660 delay 0.018297, next query 8s
May 12 04:42:16 fw ntpd[49639]: reply from 192.108.114.23: offset -0.121107 delay 0.036196, next query 7s
May 12 04:42:19 fw ntpd[49639]: reply from 194.177.210.54: offset -0.122998 delay 0.016097, next query 6s
May 12 04:42:23 fw ntpd[49639]: reply from 192.108.114.23: offset -0.125186 delay 0.035444, next query 7s
May 12 04:42:25 fw ntpd[49639]: reply from 194.177.210.54: offset -0.125804 delay 0.015351, next query 32s
May 12 04:42:31 fw ntpd[49639]: reply from 192.108.114.23: offset -0.129040 delay 0.035929, next query 33s
May 12 04:42:38 fw ntpd[49639]: reply from 79.107.99.220: offset -0.138253 delay 0.016933, next query 33s
May 12 04:42:58 fw ntpd[49639]: reply from 194.177.210.54: offset -0.143674 delay 0.017428, next query 34s
May 12 04:42:58 fw ntpd[49598]: adjusting local clock by -0.131546s
May 12 04:43:04 fw ntpd[49639]: reply from 192.108.114.23: offset -0.021319 delay 0.035169, next query 31s
May 12 04:43:11 fw ntpd[49639]: reply from 79.107.99.220: offset -0.030433 delay 0.017407, next query 34s
May 12 04:43:32 fw ntpd[49639]: reply from 194.177.210.54: offset -0.036033 delay 0.017525, next query 30s
May 12 04:43:35 fw ntpd[49639]: reply from 192.108.114.23: offset -0.038011 delay 0.035726, next query 30s
May 12 04:43:45 fw ntpd[49639]: reply from 79.107.99.220: offset -0.048904 delay 0.018332, next query 33s
May 12 04:44:02 fw ntpd[49639]: reply from 194.177.210.54: offset -0.052044 delay 0.017614, next query 31s
May 12 04:44:05 fw ntpd[49639]: reply from 192.108.114.23: offset -0.053979 delay 0.034936, next query 31s
May 12 04:44:18 fw ntpd[49639]: reply from 79.107.99.220: offset -0.066052 delay 0.016565, next query 30s
May 12 04:44:33 fw ntpd[49639]: reply from 194.177.210.54: offset -0.068872 delay 0.015591, next query 33s
May 12 04:44:36 fw ntpd[49639]: reply from 192.108.114.23: offset -0.070545 delay 0.035545, next query 33s
May 12 04:44:48 fw ntpd[49639]: reply from 79.107.99.220: offset -0.081463 delay 0.016743, next query 33s
May 12 04:45:06 fw ntpd[49639]: reply from 194.177.210.54: offset -0.085850 delay 0.017215, next query 31s
May 12 04:45:09 fw ntpd[49639]: reply from 192.108.114.23: offset -0.087479 delay 0.036191, next query 32s
May 12 04:45:21 fw ntpd[49639]: reply from 79.107.99.220: offset -0.099614 delay 0.017300, next query 33s
May 12 04:45:37 fw ntpd[49639]: reply from 194.177.210.54: offset -0.102244 delay 0.016677, next query 34s
May 12 04:45:41 fw ntpd[49639]: reply from 192.108.114.23: offset -0.104899 delay 0.036324, next query 30s
May 12 04:45:54 fw ntpd[49639]: reply from 79.107.99.220: offset -0.116298 delay 0.016718, next query 30s
May 12 04:46:11 fw ntpd[49639]: reply from 194.177.210.54: offset -0.122919 delay 0.021334, next query 34s
May 12 04:46:11 fw ntpd[49639]: reply from 192.108.114.23: offset -0.119854 delay 0.036803, next query 32s
May 12 04:46:24 fw ntpd[49639]: reply from 79.107.99.220: offset -0.133142 delay 0.015986, next query 30s
May 12 04:46:43 fw ntpd[49639]: reply from 192.108.114.23: offset -0.137312 delay 0.035884, next query 31s
May 12 04:46:44 fw ntpd[49639]: reply from 194.177.210.54: offset -0.137732 delay 0.015813, next query 30s
May 12 04:46:44 fw ntpd[49598]: adjusting local clock by -0.087417s
May 12 04:46:53 fw ntpd[49639]: reply from 79.107.99.220: offset -0.079623 delay 0.016507, next query 34s
May 12 04:47:14 fw ntpd[49639]: reply from 194.177.210.54: offset -0.084871 delay 0.016842, next query 33s
May 12 04:47:14 fw ntpd[49639]: reply from 192.108.114.23: offset -0.084110 delay 0.037357, next query 32s
May 12 04:47:27 fw ntpd[49639]: reply from 79.107.99.220: offset -0.097776 delay 0.016359, next query 32s
May 12 04:47:46 fw ntpd[49639]: reply from 192.108.114.23: offset -0.101964 delay 0.034433, next query 31s
May 12 04:47:47 fw ntpd[49639]: reply from 194.177.210.54: offset -0.102418 delay 0.016164, next query 31s
May 12 04:47:59 fw ntpd[49639]: reply from 79.107.99.220: offset -0.114346 delay 0.016552, next query 33s
May 12 04:48:17 fw ntpd[49639]: reply from 192.108.114.23: offset -0.118617 delay 0.035556, next query 30s
May 12 04:48:18 fw ntpd[49639]: reply from 194.177.210.54: offset -0.118816 delay 0.016154, next query 32s
May 12 04:48:32 fw ntpd[49639]: reply from 79.107.99.220: offset -0.131498 delay 0.015703, next query 32s
May 12 04:48:48 fw ntpd[49639]: reply from 192.108.114.23: offset -0.134187 delay 0.037186, next query 33s
May 12 04:48:51 fw ntpd[49639]: reply from 194.177.210.54: offset -0.134994 delay 0.018038, next query 31s
May 12 04:48:51 fw ntpd[49598]: adjusting local clock by -0.125881s
May 12 04:49:05 fw ntpd[49639]: reply from 79.107.99.220: offset -0.047269 delay 0.016075, next query 34s
May 12 04:49:21 fw ntpd[49639]: reply from 192.108.114.23: offset -0.050386 delay 0.036145, next query 30s
May 12 04:49:22 fw ntpd[49639]: reply from 194.177.210.54: offset -0.050999 delay 0.016905, next query 32s
May 12 04:49:39 fw ntpd[49639]: reply from 79.107.99.220: offset -0.065242 delay 0.016211, next query 30s
May 12 04:49:51 fw ntpd[49639]: reply from 192.108.114.23: offset -0.065418 delay 0.036230, next query 34s
May 12 04:49:54 fw ntpd[49639]: reply from 194.177.210.54: offset -0.067539 delay 0.015291, next query 32s
May 12 04:50:09 fw ntpd[49639]: reply from 79.107.99.220: offset -0.081052 delay 0.017031, next query 33s
May 12 04:50:25 fw ntpd[49639]: reply from 192.108.114.23: offset -0.084079 delay 0.035812, next query 31s
May 12 04:50:26 fw ntpd[49639]: reply from 194.177.210.54: offset -0.084478 delay 0.015837, next query 33s
May 12 04:50:42 fw ntpd[49639]: reply from 79.107.99.220: offset -0.098495 delay 0.016019, next query 32s
May 12 04:50:56 fw ntpd[49639]: reply from 192.108.114.23: offset -0.100178 delay 0.035591, next query 30s
May 12 04:50:59 fw ntpd[49639]: reply from 194.177.210.54: offset -0.101885 delay 0.017411, next query 33s
May 12 04:50:59 fw ntpd[49598]: adjusting local clock by -0.091415s
May 12 04:51:14 fw ntpd[49639]: reply from 79.107.99.220: offset -0.085819 delay 0.016217, next query 32s
May 12 04:51:26 fw ntpd[49639]: reply from 192.108.114.23: offset -0.086874 delay 0.034870, next query 30s
May 12 04:51:32 fw ntpd[49639]: reply from 194.177.210.54: offset -0.090058 delay 0.016176, next query 33s
May 12 04:51:46 fw ntpd[49639]: reply from 79.107.99.220: offset -0.103203 delay 0.016857, next query 31s
May 12 04:51:56 fw ntpd[49639]: reply from 192.108.114.23: offset -0.102605 delay 0.035424, next query 31s
May 12 04:52:05 fw ntpd[49639]: reply from 194.177.210.54: offset -0.107630 delay 0.016180, next query 30s
May 12 04:52:17 fw ntpd[49639]: reply from 79.107.99.220: offset -0.101991 delay 0.051390, next query 34s
May 12 04:52:27 fw ntpd[49639]: reply from 192.108.114.23: offset -0.119187 delay 0.035113, next query 34s
May 12 04:52:34 fw ntpd[49639]: reply from 194.177.210.54: offset -0.122300 delay 0.016592, next query 34s
May 12 04:52:50 fw ntpd[49639]: reply from 79.107.99.220: offset -0.136920 delay 0.016097, next query 31s
May 12 04:53:01 fw ntpd[49639]: reply from 192.108.114.23: offset -0.136997 delay 0.034894, next query 33s
May 12 04:53:08 fw ntpd[49639]: reply from 194.177.210.54: offset -0.140624 delay 0.015719, next query 32s
May 12 04:53:21 fw ntpd[49639]: reply from 79.107.99.220: offset -0.153201 delay 0.016817, next query 32s
May 12 04:53:34 fw ntpd[49639]: reply from 192.108.114.23: offset -0.153667 delay 0.036913, next query 33s
May 12 04:53:40 fw ntpd[49639]: reply from 194.177.210.54: offset -0.158023 delay 0.014972, next query 33s
May 12 04:53:53 fw ntpd[49639]: reply from 79.107.99.220: offset -0.170409 delay 0.015779, next query 32s
May 12 04:54:07 fw ntpd[49639]: reply from 192.108.114.23: offset -0.171624 delay 0.035492, next query 32s
May 12 04:54:13 fw ntpd[49639]: reply from 194.177.210.54: offset -0.174577 delay 0.016802, next query 31s
May 12 04:54:13 fw ntpd[49598]: adjusting local clock by -0.158023s
May 12 04:54:13 fw ntpd[49639]: clock is now synced
May 12 04:54:26 fw ntpd[49639]: reply from 79.107.99.220: offset -0.029330 delay 0.016215, next query 31s
May 12 04:54:40 fw ntpd[49639]: reply from 192.108.114.23: offset -0.031501 delay 0.036595, next query 30s
May 12 04:54:45 fw ntpd[49639]: reply from 194.177.210.54: offset -0.034096 delay 0.016487, next query 32s
May 12 04:54:57 fw ntpd[49639]: reply from 79.107.99.220: offset -0.046510 delay 0.016164, next query 31s
May 12 04:55:10 fw ntpd[49639]: reply from 192.108.114.23: offset -0.045516 delay 0.039319, next query 32s
May 12 04:55:17 fw ntpd[49639]: reply from 194.177.210.54: offset -0.050967 delay 0.015554, next query 31s
May 12 04:55:28 fw ntpd[49639]: reply from 79.107.99.220: offset -0.062724 delay 0.015655, next query 30s
May 12 04:55:42 fw ntpd[49639]: reply from 192.108.114.23: offset -0.063976 delay 0.036071, next query 31s
May 12 04:55:48 fw ntpd[49639]: reply from 194.177.210.54: offset -0.066862 delay 0.016093, next query 32s
May 12 04:55:58 fw ntpd[49639]: reply from 79.107.99.220: offset -0.078360 delay 0.016171, next query 31s
May 12 04:56:13 fw ntpd[49639]: reply from 192.108.114.23: offset -0.080224 delay 0.035871, next query 34s
May 12 04:56:20 fw ntpd[49639]: reply from 194.177.210.54: offset -0.084083 delay 0.015999, next query 31s
May 12 04:56:29 fw ntpd[49639]: reply from 79.107.99.220: offset -0.095908 delay 0.016607, next query 33s
May 12 04:56:47 fw ntpd[49639]: reply from 192.108.114.23: offset -0.098437 delay 0.035774, next query 31s
May 12 04:56:51 fw ntpd[49639]: reply from 194.177.210.54: offset -0.100468 delay 0.016432, next query 33s
May 12 04:57:02 fw ntpd[49639]: reply from 79.107.99.220: offset -0.112537 delay 0.015971, next query 33s
May 12 04:57:18 fw ntpd[49639]: reply from 192.108.114.23: offset -0.114681 delay 0.035459, next query 31s
May 12 04:57:24 fw ntpd[49639]: reply from 194.177.210.54: offset -0.118216 delay 0.016730, next query 34s
May 12 04:57:35 fw ntpd[49639]: reply from 79.107.99.220: offset -0.130276 delay 0.016983, next query 31s
May 12 04:57:49 fw ntpd[49639]: reply from 192.108.114.23: offset -0.131293 delay 0.034877, next query 31s
May 12 04:57:58 fw ntpd[49639]: reply from 194.177.210.54: offset -0.136314 delay 0.015939, next query 30s
May 12 04:57:58 fw ntpd[49598]: adjusting local clock by -0.108247s
May 12 04:57:58 fw ntpd[49639]: clock is now unsynced
May 12 04:58:06 fw ntpd[49639]: reply from 79.107.99.220: offset -0.084157 delay 0.016591, next query 34s
May 12 04:58:20 fw ntpd[49639]: reply from 192.108.114.23: offset -0.085077 delay 0.035133, next query 33s
May 12 04:58:27 fw ntpd[49639]: reply from 194.177.210.54: offset -0.088600 delay 0.016088, next query 33s
May 12 04:58:39 fw ntpd[49639]: reply from 79.107.99.220: offset -0.101228 delay 0.016374, next query 32s
May 12 04:58:53 fw ntpd[49639]: reply from 192.108.114.23: offset -0.102234 delay 0.035972, next query 34s
May 12 04:59:00 fw ntpd[49639]: reply from 194.177.210.54: offset -0.106525 delay 0.016017, next query 30s
May 12 04:59:11 fw ntpd[49639]: reply from 79.107.99.220: offset -0.118344 delay 0.015858, next query 31s
May 12 04:59:27 fw ntpd[49639]: reply from 192.108.114.23: offset -0.120742 delay 0.036024, next query 30s
May 12 04:59:30 fw ntpd[49639]: reply from 194.177.210.54: offset -0.122094 delay 0.016541, next query 32s
May 12 04:59:30 fw ntpd[49598]: adjusting local clock by -0.130815s
May 12 04:59:42 fw ntpd[49639]: reply from 79.107.99.220: offset -0.066116 delay 0.016231, next query 30s
May 12 04:59:57 fw ntpd[49639]: reply from 192.108.114.23: offset -0.067699 delay 0.035625, next query 32s
May 12 05:00:03 fw ntpd[49639]: reply from 194.177.210.54: offset -0.143646 delay 0.185228, next query 31s
May 12 05:00:13 fw ntpd[49639]: reply from 79.107.99.220: offset -0.082644 delay 0.016160, next query 31s
May 12 05:00:30 fw ntpd[49639]: reply from 192.108.114.23: offset -0.085137 delay 0.037189, next query 32s
May 12 05:00:34 fw ntpd[49639]: reply from 194.177.210.54: offset -0.086822 delay 0.016346, next query 32s
May 12 05:00:44 fw ntpd[49639]: reply from 79.107.99.220: offset -0.098439 delay 0.016490, next query 34s
May 12 05:01:02 fw ntpd[49639]: reply from 192.108.114.23: offset -0.102047 delay 0.036488, next query 30s
May 12 05:01:06 fw ntpd[49639]: reply from 194.177.210.54: offset -0.104360 delay 0.015427, next query 31s
May 12 05:01:18 fw ntpd[49639]: reply from 79.107.99.220: offset -0.117203 delay 0.016285, next query 31s
May 12 05:01:32 fw ntpd[49639]: reply from 192.108.114.23: offset -0.118465 delay 0.035974, next query 33s
May 12 05:01:37 fw ntpd[49639]: reply from 194.177.210.54: offset -0.120800 delay 0.015981, next query 30s
May 12 05:01:49 fw ntpd[49639]: reply from 79.107.99.220: offset -0.130864 delay 0.020409, next query 30s
May 12 05:02:05 fw ntpd[49639]: reply from 192.108.114.23: offset -0.135347 delay 0.035048, next query 31s
May 12 05:02:07 fw ntpd[49639]: reply from 194.177.210.54: offset -0.137770 delay 0.018384, next query 30s
May 12 05:02:07 fw ntpd[49598]: adjusting local clock by -0.156674s
May 12 05:02:19 fw ntpd[49639]: reply from 79.107.99.220: offset -0.044857 delay 0.016679, next query 32s
May 12 05:02:36 fw ntpd[49639]: reply from 192.108.114.23: offset -0.026251 delay 0.077790, next query 32s
May 12 05:02:37 fw ntpd[49639]: reply from 194.177.210.54: offset -0.041309 delay 0.029973, next query 34s
May 12 05:02:51 fw ntpd[49639]: reply from 79.107.99.220: offset -0.061568 delay 0.016510, next query 33s
May 12 05:03:08 fw ntpd[49639]: reply from 192.108.114.23: offset -0.064449 delay 0.035378, next query 33s
May 12 05:03:10 fw ntpd[49639]: reply from 194.177.210.54: offset -0.066003 delay 0.015313, next query 31s
May 12 05:03:23 fw ntpd[49639]: reply from 79.107.99.220: offset -0.078288 delay 0.016263, next query 34s
May 12 05:03:41 fw ntpd[49639]: reply from 194.177.210.54: offset -0.082394 delay 0.016209, next query 33s
May 12 05:03:41 fw ntpd[49639]: reply from 192.108.114.23: offset -0.081636 delay 0.037392, next query 31s
May 12 05:03:57 fw ntpd[49639]: reply from 79.107.99.220: offset -0.096411 delay 0.016875, next query 33s
May 12 05:04:12 fw ntpd[49639]: reply from 192.108.114.23: offset -0.098197 delay 0.036270, next query 34s
May 12 05:04:14 fw ntpd[49639]: reply from 194.177.210.54: offset -0.099491 delay 0.017075, next query 34s
May 12 05:04:30 fw ntpd[49639]: reply from 79.107.99.220: offset -0.114799 delay 0.017562, next query 34s
May 12 05:04:46 fw ntpd[49639]: reply from 192.108.114.23: offset -0.116025 delay 0.036562, next query 32s
May 12 05:04:48 fw ntpd[49639]: reply from 194.177.210.54: offset -0.117487 delay 0.016189, next query 30s
May 12 05:05:04 fw ntpd[49639]: reply from 79.107.99.220: offset -0.131979 delay 0.016580, next query 34s
May 12 05:05:18 fw ntpd[49639]: reply from 194.177.210.54: offset -0.132976 delay 0.016728, next query 30s
May 12 05:05:18 fw ntpd[49598]: adjusting local clock by -0.127176s
May 12 05:05:19 fw ntpd[49639]: reply from 192.108.114.23: negative delay -0.028148s, next query 3107s
May 12 05:05:39 fw ntpd[49639]: reply from 79.107.99.220: offset -0.084505 delay 0.017397, next query 33s
May 12 05:05:49 fw ntpd[49639]: reply from 194.177.210.54: offset -0.083610 delay 0.016623, next query 31s
May 12 05:06:12 fw ntpd[49639]: reply from 79.107.99.220: offset -0.101661 delay 0.018143, next query 33s
May 12 05:06:20 fw ntpd[49639]: reply from 194.177.210.54: offset -0.100229 delay 0.015447, next query 31s
May 12 05:06:45 fw ntpd[49639]: reply from 79.107.99.220: offset -0.119310 delay 0.016695, next query 33s
May 12 05:06:51 fw ntpd[49639]: reply from 194.177.210.54: offset -0.116723 delay 0.015883, next query 30s
May 12 05:07:18 fw ntpd[49639]: reply from 79.107.99.220: offset -0.136351 delay 0.016870, next query 30s
May 12 05:07:21 fw ntpd[49639]: reply from 194.177.210.54: offset -0.131860 delay 0.015728, next query 33s
May 12 05:07:48 fw ntpd[49639]: reply from 79.107.99.220: offset -0.152980 delay 0.016456, next query 32s
May 12 05:07:54 fw ntpd[49639]: reply from 194.177.210.54: offset -0.149990 delay 0.016063, next query 30s
May 12 05:08:20 fw ntpd[49639]: reply from 79.107.99.220: offset -0.169411 delay 0.016451, next query 33s
May 12 05:08:24 fw ntpd[49639]: reply from 194.177.210.54: offset -0.164915 delay 0.016452, next query 34s
May 12 05:08:53 fw ntpd[49639]: reply from 79.107.99.220: offset -0.187719 delay 0.016143, next query 32s
May 12 05:08:58 fw ntpd[49639]: reply from 194.177.210.54: offset -0.183370 delay 0.017222, next query 30s
May 12 05:09:25 fw ntpd[49639]: reply from 79.107.99.220: offset -0.204034 delay 0.016502, next query 34s
May 12 05:09:28 fw ntpd[49639]: reply from 194.177.210.54: offset -0.199493 delay 0.016378, next query 34s
May 12 05:09:59 fw ntpd[49639]: reply from 79.107.99.220: offset -0.221922 delay 0.016926, next query 31s
May 12 05:10:02 fw ntpd[49639]: reply from 194.177.210.54: offset -0.217457 delay 0.016421, next query 31s
May 12 05:10:30 fw ntpd[49639]: reply from 79.107.99.220: offset -0.238166 delay 0.016051, next query 33s
May 12 05:10:33 fw ntpd[49639]: reply from 194.177.210.54: offset -0.233199 delay 0.015933, next query 30s
May 12 05:11:03 fw ntpd[49639]: reply from 79.107.99.220: offset -0.255886 delay 0.017309, next query 32s
May 12 05:11:03 fw ntpd[49639]: reply from 194.177.210.54: offset -0.248369 delay 0.017339, next query 32s
May 12 05:11:35 fw ntpd[49639]: reply from 79.107.99.220: offset -0.272694 delay 0.016962, next query 32s
May 12 05:11:35 fw ntpd[49639]: reply from 194.177.210.54: offset -0.265831 delay 0.017914, next query 34s
May 12 05:12:07 fw ntpd[49639]: reply from 79.107.99.220: offset -0.289178 delay 0.017057, next query 32s
May 12 05:12:09 fw ntpd[49639]: reply from 194.177.210.54: offset -0.284844 delay 0.016877, next query 31s
May 12 05:12:39 fw ntpd[49639]: reply from 79.107.99.220: offset -0.305944 delay 0.016265, next query 31s
May 12 05:12:40 fw ntpd[49639]: reply from 194.177.210.54: offset -0.300634 delay 0.017463, next query 34s
May 12 05:13:09 fw ntpd[49639]: reply from 79.107.99.220: offset -0.322411 delay 0.016153, next query 30s
May 12 05:13:14 fw ntpd[49639]: reply from 194.177.210.54: offset -0.318958 delay 0.016145, next query 31s
May 12 05:13:39 fw ntpd[49639]: reply from 79.107.99.220: offset -0.338957 delay 0.017282, next query 33s
May 12 05:14:00 fw ntpd[49639]: no reply from 194.177.210.54 received in time, next query 300s
May 12 05:14:00 fw ntpd[49639]: peer 194.177.210.54 now invalid
May 12 05:14:12 fw ntpd[49639]: reply from 79.107.99.220: offset -0.355603 delay 0.017441, next query 34s
May 12 05:14:46 fw ntpd[49639]: reply from 79.107.99.220: offset -0.372940 delay 0.017917, next query 34s
May 12 05:15:20 fw ntpd[49639]: reply from 79.107.99.220: offset -0.391758 delay 0.016550, next query 33s
May 12 05:15:53 fw ntpd[49639]: reply from 79.107.99.220: offset -0.407341 delay 0.019883, next query 32s
May 12 05:16:26 fw ntpd[49639]: reply from 79.107.99.220: offset -0.426394 delay 0.015927, next query 32s
May 12 05:16:58 fw ntpd[49639]: reply from 79.107.99.220: offset -0.443550 delay 0.016660, next query 34s
May 12 05:17:32 fw ntpd[49639]: reply from 79.107.99.220: offset -0.461124 delay 0.017674, next query 34s
May 12 05:18:06 fw ntpd[49639]: reply from 79.107.99.220: offset -0.478948 delay 0.017307, next query 33s
May 12 05:18:39 fw ntpd[49639]: reply from 79.107.99.220: offset -0.483774 delay 0.043604, next query 30s
May 12 05:19:01 fw ntpd[49639]: reply from 194.177.210.54: offset -0.502313 delay 0.017070, next query 5s
May 12 05:19:06 fw ntpd[49639]: reply from 194.177.210.54: offset -0.504694 delay 0.016063, next query 7s
May 12 05:19:09 fw ntpd[49639]: reply from 79.107.99.220: offset -0.512532 delay 0.016299, next query 32s
May 12 05:19:13 fw ntpd[49639]: reply from 194.177.210.54: offset -0.508456 delay 0.016243, next query 6s
May 12 05:19:19 fw ntpd[49639]: peer 194.177.210.54 now valid
May 12 05:19:19 fw ntpd[49639]: reply from 194.177.210.54: offset -0.511222 delay 0.016554, next query 6s
May 12 05:19:25 fw ntpd[49639]: reply from 194.177.210.54: offset -0.514874 delay 0.017011, next query 9s
May 12 05:19:34 fw ntpd[49639]: reply from 194.177.210.54: offset -0.519673 delay 0.016589, next query 7s
May 12 05:19:41 fw ntpd[49639]: reply from 79.107.99.220: offset -0.529516 delay 0.017086, next query 33s
May 12 05:19:41 fw ntpd[49639]: reply from 194.177.210.54: offset -0.522542 delay 0.017275, next query 31s
May 12 05:20:12 fw ntpd[49639]: reply from 194.177.210.54: offset -0.540038 delay 0.016418, next query 34s
May 12 05:20:14 fw ntpd[49639]: reply from 79.107.99.220: offset -0.547214 delay 0.016558, next query 32s
May 12 05:20:46 fw ntpd[49639]: reply from 79.107.99.220: offset -0.563136 delay 0.017123, next query 33s
May 12 05:20:46 fw ntpd[49639]: reply from 194.177.210.54: offset -0.557268 delay 0.017776, next query 32s
May 12 05:21:18 fw ntpd[49639]: reply from 194.177.210.54: offset -0.574383 delay 0.017225, next query 31s
May 12 05:21:19 fw ntpd[49639]: reply from 79.107.99.220: offset -0.581051 delay 0.016456, next query 33s
May 12 05:21:49 fw ntpd[49639]: reply from 194.177.210.54: offset -0.591127 delay 0.015788, next query 31s
May 12 05:21:52 fw ntpd[49639]: reply from 79.107.99.220: offset -0.597472 delay 0.018915, next query 31s
May 12 05:22:20 fw ntpd[49639]: reply from 194.177.210.54: offset -0.607796 delay 0.017103, next query 31s
May 12 05:22:22 fw ntpd[49639]: reply from 79.107.99.220: offset -0.614818 delay 0.016300, next query 31s
May 12 05:22:51 fw ntpd[49639]: reply from 194.177.210.54: offset -0.623521 delay 0.015958, next query 32s
May 12 05:22:53 fw ntpd[49639]: reply from 79.107.99.220: offset -0.630707 delay 0.016633, next query 34s
May 12 05:23:23 fw ntpd[49639]: reply from 194.177.210.54: offset -0.616045 delay 0.065610, next query 32s
May 12 05:23:27 fw ntpd[49639]: reply from 79.107.99.220: offset -0.650100 delay 0.017611, next query 34s
May 12 05:23:55 fw ntpd[49639]: reply from 194.177.210.54: offset -0.657485 delay 0.017622, next query 34s
May 12 05:24:01 fw ntpd[49639]: reply from 79.107.99.220: offset -0.666194 delay 0.017675, next query 30s
May 12 05:24:30 fw ntpd[49639]: reply from 194.177.210.54: offset -0.675917 delay 0.016976, next query 32s
May 12 05:24:32 fw ntpd[49639]: reply from 79.107.99.220: offset -0.683099 delay 0.016170, next query 30s
May 12 05:25:02 fw ntpd[49639]: reply from 79.107.99.220: offset -0.699282 delay 0.016188, next query 33s
May 12 05:25:02 fw ntpd[49639]: reply from 194.177.210.54: offset -0.692262 delay 0.017851, next query 34s
May 12 05:25:35 fw ntpd[49639]: reply from 79.107.99.220: offset -0.716383 delay 0.015934, next query 30s
May 12 05:25:36 fw ntpd[49639]: reply from 194.177.210.54: offset -0.711171 delay 0.016152, next query 32s
May 12 05:26:05 fw ntpd[49639]: reply from 79.107.99.220: offset -0.731988 delay 0.016267, next query 31s
May 12 05:26:08 fw ntpd[49639]: reply from 194.177.210.54: offset -0.728291 delay 0.016951, next query 33s
May 12 05:26:36 fw ntpd[49639]: reply from 79.107.99.220: offset -0.749171 delay 0.016359, next query 32s
May 12 05:26:41 fw ntpd[49639]: reply from 194.177.210.54: offset -0.745286 delay 0.016426, next query 33s
May 12 05:27:08 fw ntpd[49639]: reply from 79.107.99.220: offset -0.765663 delay 0.015956, next query 33s
May 12 05:27:14 fw ntpd[49639]: reply from 194.177.210.54: offset -0.762608 delay 0.016438, next query 30s
May 12 05:27:41 fw ntpd[49639]: reply from 79.107.99.220: offset -0.783906 delay 0.018353, next query 31s
May 12 05:27:44 fw ntpd[49639]: reply from 194.177.210.54: offset -0.778554 delay 0.015902, next query 32s
May 12 05:28:12 fw ntpd[49639]: reply from 79.107.99.220: offset -0.800134 delay 0.017810, next query 30s
May 12 05:28:16 fw ntpd[49639]: reply from 194.177.210.54: offset -0.795472 delay 0.015879, next query 32s
May 12 05:28:42 fw ntpd[49639]: reply from 79.107.99.220: offset -0.815270 delay 0.017454, next query 33s
May 12 05:28:48 fw ntpd[49639]: reply from 194.177.210.54: offset -0.811929 delay 0.016423, next query 34s
May 12 05:29:15 fw ntpd[49639]: reply from 79.107.99.220: offset -0.832975 delay 0.016566, next query 33s
May 12 05:29:21 fw ntpd[49639]: reply from 194.177.210.54: offset -0.830289 delay 0.016113, next query 30s
May 12 05:29:48 fw ntpd[49639]: reply from 79.107.99.220: offset -0.851139 delay 0.017383, next query 33s
May 12 05:29:51 fw ntpd[49639]: reply from 194.177.210.54: offset -0.845917 delay 0.016638, next query 34s
May 12 05:30:21 fw ntpd[49639]: reply from 79.107.99.220: offset -0.868336 delay 0.016623, next query 33s
May 12 05:30:25 fw ntpd[49639]: reply from 194.177.210.54: offset -0.863777 delay 0.016863, next query 32s
May 12 05:30:54 fw ntpd[49639]: reply from 79.107.99.220: offset -0.885439 delay 0.015645, next query 31s
May 12 05:30:57 fw ntpd[49639]: reply from 194.177.210.54: offset -0.880965 delay 0.016387, next query 31s
May 12 05:31:25 fw ntpd[49639]: reply from 79.107.99.220: offset -0.902106 delay 0.016765, next query 30s
May 12 05:31:28 fw ntpd[49639]: reply from 194.177.210.54: offset -0.897283 delay 0.016502, next query 32s
May 12 05:31:56 fw ntpd[49639]: reply from 79.107.99.220: offset -0.918528 delay 0.016540, next query 32s
May 12 05:32:01 fw ntpd[49639]: reply from 194.177.210.54: offset -0.914438 delay 0.015405, next query 32s
May 12 05:32:28 fw ntpd[49639]: reply from 79.107.99.220: offset -0.934747 delay 0.016517, next query 31s
May 12 05:32:33 fw ntpd[49639]: reply from 194.177.210.54: offset -0.931777 delay 0.015605, next query 31s
May 12 05:32:59 fw ntpd[49639]: reply from 79.107.99.220: offset -0.951088 delay 0.016289, next query 31s
May 12 05:33:04 fw ntpd[49639]: reply from 194.177.210.54: offset -0.947213 delay 0.016360, next query 31s
May 12 05:33:30 fw ntpd[49639]: reply from 79.107.99.220: offset -0.967618 delay 0.017914, next query 31s
May 12 05:33:35 fw ntpd[49639]: reply from 194.177.210.54: offset -0.964531 delay 0.016677, next query 34s
May 12 05:34:01 fw ntpd[49639]: reply from 79.107.99.220: offset -0.984075 delay 0.015970, next query 33s
May 12 05:34:09 fw ntpd[49639]: reply from 194.177.210.54: offset -0.981966 delay 0.015420, next query 33s
May 12 05:34:34 fw ntpd[49639]: reply from 79.107.99.220: offset -1.000242 delay 0.019310, next query 32s
May 12 05:34:42 fw ntpd[49639]: reply from 194.177.210.54: offset -0.999378 delay 0.017270, next query 31s
May 12 05:35:06 fw ntpd[49639]: reply from 79.107.99.220: offset -1.018376 delay 0.016683, next query 30s
May 12 05:35:13 fw ntpd[49639]: reply from 194.177.210.54: offset -1.016089 delay 0.015902, next query 34s
May 12 05:35:36 fw ntpd[49639]: reply from 79.107.99.220: offset -1.033645 delay 0.016422, next query 32s
May 12 05:35:47 fw ntpd[49639]: reply from 194.177.210.54: offset -1.033733 delay 0.016441, next query 31s
May 12 05:36:08 fw ntpd[49639]: reply from 79.107.99.220: offset -1.044717 delay 0.029182, next query 31s
May 12 05:36:18 fw ntpd[49639]: reply from 194.177.210.54: offset -1.050009 delay 0.016658, next query 34s
May 12 05:36:39 fw ntpd[49639]: reply from 79.107.99.220: offset -1.067296 delay 0.016569, next query 31s
May 12 05:36:52 fw ntpd[49639]: reply from 194.177.210.54: offset -1.068351 delay 0.016319, next query 33s
May 12 05:37:10 fw ntpd[49639]: reply from 79.107.99.220: offset -1.083282 delay 0.016153, next query 30s
May 12 05:37:25 fw ntpd[49639]: reply from 194.177.210.54: offset -1.085360 delay 0.017619, next query 34s
May 12 05:37:39 fw ntpd[49639]: reply from 79.107.99.220: offset -1.099247 delay 0.016043, next query 31s
May 12 05:37:59 fw ntpd[49639]: reply from 194.177.210.54: offset -1.103972 delay 0.015844, next query 34s
May 12 05:38:10 fw ntpd[49639]: reply from 79.107.99.220: offset -1.114825 delay 0.018190, next query 32s

wallabybob

It is possible this is utterly irrelevant, but the "bad file descriptor" reports happen soon after the increasingly unlikely clock adjustment values start getting into territory where the number of seconds could be overflowing 32 bits.

The reported clock adjustments don't seem to be taking effect and there is no indication any of the ntpd processes notice.

May 12 09:57:36 pfsense2 ntpd[51007]: adjusting local clock by 1064411700.356701s
May 12 09:58:07 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1064411738.686966 delay 0.000582, next query 31s
May 12 09:58:38 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1064411738.697569 delay 0.000529, next query 31s
May 12 09:59:09 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1064411738.708118 delay 0.000622, next query 31s
May 12 09:59:40 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1064411738.718725 delay 0.000528, next query 33s
May 12 10:00:14 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1064411738.724996 delay 0.000608, next query 34s
May 12 10:00:14 pfsense2 ntpd[51007]: adjusting local clock by 1221456052.912002s
May 12 10:00:48 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1221456092.081884 delay 0.000559, next query 33s
May 12 10:01:21 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1221456092.093124 delay 0.000612, next query 31s
May 12 10:01:52 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1221456092.103718 delay 0.000561, next query 33s
May 12 10:02:25 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1221456092.107547 delay 0.000482, next query 30s
May 12 10:02:55 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1221456092.102751 delay 0.000563, next query 33s
May 12 10:03:29 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1221456092.092541 delay 0.000505, next query 32s
May 12 10:04:01 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -1221456092.094274 delay 0.000611, next query 31s
May 12 10:04:01 pfsense2 ntpd[51007]: adjusting local clock by 157044313.117055s
May 12 10:04:32 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -157044353.444915 delay 0.000585, next query 32s
May 12 10:05:04 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -157044353.455843 delay 0.000539, next query 31s
May 12 10:05:35 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -157044353.466427 delay 0.000568, next query 30s
May 12 10:06:05 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -157044353.476696 delay 0.000624, next query 31s
May 12 10:06:37 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset -157044353.482255 delay 0.000475, next query 32s
May 12 10:06:37 pfsense2 ntpd[51007]: adjusting local clock by -907367426.381670s
May 12 10:07:08 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 907367385.221527 delay 0.000543, next query 31s
May 12 10:07:39 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 907367385.210924 delay 0.000544, next query 33s
May 12 10:08:12 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 907367385.199629 delay 0.000552, next query 33s
May 12 10:08:46 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 907367385.187986 delay 0.000479, next query 30s
May 12 10:09:16 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 907367385.177740 delay 0.000549, next query 31s
May 12 10:09:47 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 907367385.167141 delay 0.000569, next query 32s
May 12 10:10:19 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 907367385.156223 delay 0.000628, next query 31s
May 12 10:10:49 pfsense2 ntpd[51062]: reply from 192.168.211.173: offset 907367385.150583 delay 0.000552, next query 30s
May 12 10:10:49 pfsense2 ntpd[51007]: adjusting local clock by -2128823517.229217s
May 12 10:11:19 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: No such file or directory
May 12 11:04:27 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 11:58:35 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 12:52:54 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 13:44:00 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 14:37:21 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 15:32:00 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 16:25:03 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 17:19:13 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 18:13:09 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 19:03:46 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 19:53:51 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 20:47:39 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 21:39:25 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 22:31:07 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor
May 12 23:25:18 pfsense2 ntpd[51062]: recvmsg control format 192.168.211.173: Bad file descriptor

jimp

As an extra data point, this is definitely an OpenNTPD issue as it's even happening on 2.0.2 images I'm building and testing. My ALIX has been up ~16hrs and is logging that its clock is being reset by around -1400000 seconds.

We're discussing dropping OpenNTPD in favor of FreeBSD's even though we've hesitated in the past. We'll have to work around its limitations in other ways, but it's better than having a wonky clock.

johnpoz

"We're discussing dropping OpenNTPD"

Sweet!!! No more having to edit the ntp.conf every update to pfsense and manually start ntpd.

jimp

Current snaps should be switched to ntpd, works fine for me so far on a vm.

Some notes that I mentioned to other devs about the switch:

1. The boot-time behavior needs some observation, not sure if what I'm doing there is sufficient. I pass -g to ntpd which allows a large first skew, but I'm not sure if it's fast enough to sync at boot. We may need to bring back the call to ntpdate in rc before launching.

2. FreeBSD's ntpd has no concept of selective binding/listening, it listens on all by default, and we can't use its restrict keywords because they are not compatible with *.pool.ntp.org - the restrict keywords can't handle multiple A records being returned. As such, I removed Services > OpenNTPD since the options were now irrelevant.

3. I added a status page at Status > NTP that parses the ntpq output

Adding on 3, I committed a fix today to clean the page up and make it a little better, but that's not in a snapshot yet.