I have been chasing something similar. On Debian 8.8 and prior Jessie versions, systemd-timesyncd worked very well and issued a lot of (level debug) messages that told you what was going on, and the level of correction being applied. When it is running the time would stay synced within 20 milliseconds or so.
On Stretch, I have been unable to receive any of these update messages. Normally every 30 minutes, after initial correction convergence. rsyslog is correctly configured to capture them. All I see is a single syslog message at the time of initial sync, then nothing. I am unable to convince myself that systemd-timesyncd is actually running, even though systemctl status systemd-timesyncd.service says that it is. --- Graham == On Friday, December 8, 2017 at 9:39:21 PM UTC-6, wku...@gmail.com wrote: > > I've an IOT application distributed over multiple systems all on a local > network and all synchronized with some flavor of ntp running. > > These all stay syncronized to within a second over long periods: > Raspberry Pi2 > Raspberry Pi3 > Raspberry PiZero-W > Ubuntu 16.04 desktop > Commercial Lorex security DVR > > These two have drifted about three seconds slow already, although they > seem well synced with each other: > Beaglebone Green running Debian 8.9 (rebooted this morning) > Beaglebone White running Debian 9.2 (booted yesterday morning) > > > All the Raspberries are running Raspbian, verson 8 for the Pi2 and version > 9 for the rest > > My initial assumption is somehow they are using different time servers > that have a systematic error. Problem is I can't find where the > systemd-timesync stores its servers to see if Beaglebones ntp server > settings matches the others. > > The Lorex box would drift until I changed it sync interval from 6 hours to > 1 hour. All the systems that now stay synced appear to be using > pool.ntp.org, I can't seem to find where the Beaglbones store the server > they use. > > Like with most things systemd I'm finding lots of misleading and confusing > information that is generally not matching what I'm finding on my systems, > but the Beaglebone solution may be as simple as it was for the Lorex device > -- shorten the sync interval. But how do I find what the interval is and > then how do I shorten it? > > This system has been running and evolving since 2015, and I've noticed the > Beaglebones generally would be "off" + or - a few seconds from the > beginning of development, but I'm just now getting to adding the feature > that needs time sync accurate within one second. > > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/e68d2316-638c-4c02-a874-969ab3bb96e8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
