[SOLVED] NTPD problem on OPNsense 16.1.2-amd64

[kaipanoi]

I upgraded to 16 and now NTPD won't sync upstream. Here's a query right after restarting the service (note it looks happy):

Code Select Expand


# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*com1243.eecs.ut 130.207.244.240  2 u    -   64    1   52.187  -1370.1 602.678
+ec2-52-0-56-137 198.82.247.108   3 u    3   64    1   30.554  -1196.4 604.234
+time-a.timefreq .ACTS.           1 u    2   64    1   72.799  -1190.5 604.624
+131.107.13.100  .ACTS.           1 u    3   64    1  109.730  -1088.2 602.899


This log entry will appear:

Code Select Expand


Feb  6 14:43:02 fw ntpd[58138]: 0.0.0.0 c618 08 no_sys_peer


And then it falls over:

Code Select Expand


# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
com1243.eecs.ut 130.207.244.240  2 u   59   64    3   48.302  -6736.5 5828.65
ec2-52-0-56-137 198.82.247.108   3 u   64   64    3   31.480  -6288.3 5556.01
time-a.timefreq .ACTS.           1 u   63   64    3   72.770  -6281.8 5555.80
131.107.13.100  .ACTS.           1 u   63   64    3  107.870  -6273.4 5648.01


status_ntpd.php says "Unreach/Pending" for all four: (see attached)

Here's the config file:

Code Select Expand


#
# OPNsense ntp configuration file
#

tinker panic 0
# Orphan mode stratum
tos orphan 12


# Upstream Servers
server 0.debian.pool.ntp.org iburst maxpoll 9
server 1.debian.pool.ntp.org iburst maxpoll 9
server 2.debian.pool.ntp.org iburst maxpoll 9
server 3.debian.pool.ntp.org iburst maxpoll 9


disable monitor
statsdir /var/log/ntp
logconfig =syncall +clockall +peerall +sysall
driftfile /var/db/ntpd.drift
restrict default nomodify notrap
restrict -6 default nomodify notrap

interface ignore all
interface listen vtnet0


[franco]

Which VM type is this? Virtio has problems lately (on FreeBSD 10.2)

[kaipanoi]

Ah yes, sorry. It's a KVM/QEMU guest in red hat.

I switched my local NTP server to a physical machine and all the problems went away. I think the issue was the physical host for this VM was syncing time to this guest, which was then syncing it's hardware clock with the physical host.

[franco]

Okay, thanks for checking back :)