[Bug 242137] [NTP] "Unexpected origin timestamp 0xe180e455.d15bf3fb does not match aorg 0000000000.00000000 from server" (kernel reports TIME_ERROR: 0x41: Clock Unsynchronized)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242137

Cy Schubert <cy at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|bugs at FreeBSD.org            |cy at FreeBSD.org
                 CC|                            |cy at FreeBSD.org

--- Comment #15 from Cy Schubert <cy at FreeBSD.org> ---
Read this carefully. There are a number of outputs being requested here.

Your network or upstream has issues. Compare offset and jitter of the server
that has the error with the server that does not. You've only been able to
reach once (or 7 times). Compere this with those that work.

Can we have output of cat /var/db/ntp/ntp.drift please? Large drift in
conjunction with the inability to contact each ntp sever is the cause of this
error.

You should see synchronization flags (*, #, +, -) in your ntpq output. We see
none. You're not synchronizing. Again, this points to probable problems with
either your local network, upstream, or denied by your firewall.

----

Try adding rlimit memlock 32 to ntp.conf. (This will not work with ASLR
enabled.) This was the only change to ntp prior to r354367. (With ASLR enabled,
mlock() caused a segfault and stack corruption.)

How much RAM is installed on this machaine? How much swap is configured? How
much swap is in use?

----

Please answer all of the questions above. Again:

1. Can you ping your ntp servers? What is the round trip time?
2. Is UDP/123 open?
3. What is in ntp.drift?
4. How much RAM is in the machine?
5. Is swap being used and is ntpd using some of that swap?
6. Does setting memlock in ntp.conf do anything for you?

-- 
You are receiving this mail because:
You are the assignee for the bug.