Anyone else having issues with the kmjs time sync feature?

Have you checked the NTP server configuration?

Try forcing the sync via the command line interface. Sometimes the GUI fails to write the correct offset.

I had this exact issue last month. It turned out the problem wasn't the kmjs module itself, but an underlying OS patch that reset the timezone database. You might need to check system logs for 'timezone' or 'system clock' errors.

Short. Check firewall.

Did you confirm that the main server's time source is itself accurate? If the source is drifting, kmjs will just sync the drift. Maybe check the primary server's physical clock source.

I think the issue might be related to Daylight Saving Time transitions. If the sync happens right around the DST change, the offset calculation can fail, causing those multi-minute discrepancies you mentioned. Have you tested the sync process immediately before and after a known DST change?

The documentation is outdated. We had to manually edit the config file to use a specific secondary time source because the primary one was unreliable. It was a patch, but it required root access.

It's a known bug in version 3.1.2. The community found a temporary workaround involving a specific registry key edit. Search the GitHub issues for 'kmjs time zone offset fix' for the details.

Long response: I spent an entire afternoon debugging this. After ruling out the OS and the network, I realized the discrepancy was caused by a conflicting service running on the same port as the time sync service. It was a logging utility that was intermittently hijacking the time signal packets. You need to audit all services running on the host machine and ensure nothing is touching the system clock API. This was a very deep dive, but it solved the random discrepancies completely.

Try rebooting the entire cluster.

Have you verified user permissions? Sometimes the manual reset fails because the service account running kmjs doesn't have write access to the system time files. Check the permissions directory.

Maybe the problem is hardware related. Could the local clock crystal be failing? It's worth testing the physical clock source if software fixes fail.

The manual reset function often just writes a local value, which is why it doesn't stick if the underlying system service keeps overriding it. You need to address the service that is doing the overriding, not just the module.

Check the firewall rules for outbound UDP traffic on the NTP port. It's the most common oversight.

If you are using a VPN or proxy layer between the kmjs module and the main server, that intermediary layer could be injecting time skew or throttling the sync packets, causing the random discrepancies. Bypass the proxy temporarily for testing.