I have this one host, 12.1-p2, part of an Elasticsearch (Graylog) cluster that is constantly getting way out of sync time-wise. This is BSD on metal, like the other members of the cluster, and is the only one out of all my BSDs, virtual or otherwise, that exhibits this behaviour. As of right now it is 38 seconds out. When this started the system was a PE 2950, but it has since been updated to a 710R - which somewhat rules out an RTC issue. Unfortunately, I don't see much useful detail in ntp.log.
ntp.conf is relatively vanilla, and the same as other hosts on the network that are keeping time just fine. I did re-point the servers to the freebsd pool instead of our internal NTP server as a test, but saw no improvement.
The clock will correct eventually, but not very quickly and it drops out of the Graylog cluster when the offset gets too severe.
Looking for any troubleshooting / debugging tips, or thoughts on what might be going on here.
ntp.conf is relatively vanilla, and the same as other hosts on the network that are keeping time just fine. I did re-point the servers to the freebsd pool instead of our internal NTP server as a test, but saw no improvement.
The clock will correct eventually, but not very quickly and it drops out of the Graylog cluster when the offset gets too severe.
Looking for any troubleshooting / debugging tips, or thoughts on what might be going on here.