[ntp:hackers] Unexpected origin timestamp
mlichvar at redhat.com
Wed Apr 20 09:18:59 UTC 2016
On Tue, Apr 19, 2016 at 12:39:40PM +0200, Havard Eidnes wrote:
> I recently upgraded NTPD to 4.3.91 on the second host in a pair
> which is configured with "peer xx.xx.xx.xx" -- the other one was
> already upgraded to the same version. Since the restart of the
> second ntpd, it has been logging
> Apr 19 01:03:56 oliven ntpd: receive: Unexpected origin timestamp 0xdabfe612.67e4fee0 from 126.96.36.199 xmt 0xdabfe65c.916f4455
> It seems the "origin timestamp" has somehow become stuck?
This is a known problem with recent ntp versions. The latest comment
in the bug says it will be fixed in 4.2.8p7.
More information about the hackers