Show Posts
1
24.7 Production Series / 24.7.7 - chronyd - excessive falseticker?
« on: October 25, 2024, 03:42:58 pm »
hi all - wondering if anyone else is seeing excessive falseticker notifications from chronyd since upgrading to 24.7.7 or if it's just me.
for several months my configuration has been: i have disabled ntpd, chrony is set up on port 123, with several upstream NTS peers.
since 24.7.7, most sources are frequently (talking at least 2-4 log lines per minute of the various upstream going falseticker - i have 5 configured) marked as falsetickers leading to lots of "can't synchronize: no majority" errors. looking back at the logs, it started yesterday, which is when i upgraded to 24.7.7.
seems to come and go - there will be a few minutes where everything is a falseticker, and then a few minutes where everything is syncing fine - using sources and tracking chronyd commands to keep on top of things.
seems to happen even with NTS disabled and using regular pool.ntp.org peers instead of NTS peers.
i also have zenarmor on the box, but not protecting the wan interface opnsense should be using to talk to the peers.
just wondering if anyone else is seeing this, if this is "normal" behavior, or maybe it's an indication my hardware might be dying... or if i should just buy a gps ntp box?... no idea. perhaps it's just one of my peers being too out of sync with the others and not an opnsense issue at all. seems to be random which ones get marked as falsetickers though, and a lot of times they are all marked as falsetickers.
thanks!
for several months my configuration has been: i have disabled ntpd, chrony is set up on port 123, with several upstream NTS peers.
since 24.7.7, most sources are frequently (talking at least 2-4 log lines per minute of the various upstream going falseticker - i have 5 configured) marked as falsetickers leading to lots of "can't synchronize: no majority" errors. looking back at the logs, it started yesterday, which is when i upgraded to 24.7.7.
seems to come and go - there will be a few minutes where everything is a falseticker, and then a few minutes where everything is syncing fine - using sources and tracking chronyd commands to keep on top of things.
seems to happen even with NTS disabled and using regular pool.ntp.org peers instead of NTS peers.
i also have zenarmor on the box, but not protecting the wan interface opnsense should be using to talk to the peers.
just wondering if anyone else is seeing this, if this is "normal" behavior, or maybe it's an indication my hardware might be dying... or if i should just buy a gps ntp box?... no idea. perhaps it's just one of my peers being too out of sync with the others and not an opnsense issue at all. seems to be random which ones get marked as falsetickers though, and a lot of times they are all marked as falsetickers.
thanks!
