[ntp:hackers] Unexpected origin timestamp
stenn at ntp.org
Tue Apr 19 22:32:29 UTC 2016
Havard Eidnes writes:
> 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 0x=
> dabfe612.67e4fee0 from 184.108.40.206 xmt 0xdabfe65c.916f4455
> on each poll, the latest now being
> Apr 19 12:33:14 oliven ntpd: receive: Unexpected origin timestamp 0x=
> dabfe612.67e4fee0 from 220.127.116.11 xmt 0xdac087ea.918f0c08
> It seems the "origin timestamp" has somehow become stuck?
> Any ideas?
It used to be that this situation caused a counter increment and was
This is the first time I've seen a report of the situation you describe.
Is there anything interesting in the syslog on the sending system?
What does 'ntpq -p' show on both machines?
There are some patches around peer mode in 4.2.8p7, scheduled for public
release on Tuesday the 26th of April. I have no idea if they will fix
the situation you are seeing or not. The peer mode tests have been
working fine for me and several others who have been testing it.
Harlan Stenn <stenn at ntp.org>
http://networktimefoundation.org - be a member!
More information about the hackers