[ntp:hackers] Unexpected origin timestamp

Harlan Stenn stenn at ntp.org
Thu Apr 21 02:38:42 UTC 2016

Havard Eidnes writes:
> >> Apr 19 01:03:56 oliven ntpd[17457]: receive: Unexpected origin timestamp=
>  0xdabfe612.67e4fee0 from 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.
> >
> > http://bugs.ntp.org/show_bug.cgi?id=3D2952
> Ah, thanks!  Commenting out the return statements in 4.3.91 made
> the association work again, with an occasionally logged message
> and the corresponding dropped sample.

There's more to the fix than that.  But if you watch your log files and
look for problems, simply removing that 'return' will solve that
problem, even though it opens things up to other problems.


More information about the hackers mailing list