🚀 go-pugleaf

I'm sure I'll get corrections on this if I falter, but I'll answer anyway.

The message just means that the skew between the clocks (the local clock
and the remote one that it's trying to synch with) is larger than some
threshhold, about 128 milliseconds.  When ntpd synchs with a peer that's
more than the threshhold off from the local clock, it does it by setting
the time rather than calling adjtime(), and it clears the
peer-synchronization filter (array of saved time offsets from the remote
peer) in the process.  This prints the ``Lost NTP peer...'' message. 
What it really means is ``Cleared samples from NTP peer...''.

In short, it's not a problem with the remote peer, but it may be a
subtle indication that your local clock (or the peer's clock) doesn't
keep very consistent time--that one system or the other locks out clock
updates for a while, e.g. over long interrupt-service times.  Or that
some process besides ntpd is using adjtime() to dink with the local
clock.

		Craig