Correct. NTP is falling back to using the internal (LOCAL) clock, probably not ideal.
Your "Reach" is also 0, so it never got out to the time server.
The current time server in use will have an "*" next to it, for example
Code:
remote refid st t when poll reach delay offset jitter
==============================================================================
*10.0.0.2 132.145.5.107 2 u 1008 1024 377 0.991 -0.179 0.987
nist.gov .STEP. 16 u - 1024 0 0.000 0.000 0.000
LOCAL(0) .LOCL. 10 l 35d 64 0 0.000 0.000 0.000
If the time is to adrift it may never sync, but from the looks of it your not syncing because you are never reaching the time servers, for whatever reason, fix that first. Then, if the time is still adrift, run a manual sync, wait 15 minutes and see if you a) Have "*" next to the time servers, b) It has reached it.
You can try to test this with ntpdate -d time-p1 time-s1 which should try to reach out to those servers. The TCP/UDP ports are both 123, so you may need to check that this is open for your server to get out on.
Hi
i an not able to understand what below command in saying in its O/P
what i understand is the astrick(*) one is acting as a ntp master.
but not able to understand what insane and sys.peer here means.
# ntpq
ntpq> pe
remote refid st when poll reach delay ... (2 Replies)
In our environment we used to lot of events for ntp issues. I am unable to find the what needs to consider here. :(
ntpq -p fields.
remote refid st t when poll reach delay offset jitter
---------- Post updated at 05:13 AM ---------- Previous update was at 04:47 AM... (1 Reply)
Howdy guys,
I have 2 sun solaris server(T200) in cluster mode.
I put the command below ntpq -p.
I need your help to understand the output. I plan to change the date and time in both server.
node1:/home/mydir> ntpq -p
remote refid st t when poll reach delay ... (6 Replies)
