Hello!
[EMAIL PROTECTED] writes:
> I added the ntp servcer in the /etc/ntp.conf
> and ntpdate server.gov
> After restart the ntp service
> and it showed
>
> [root@mail etc]# ntptrace
> localhost.localdomain: stratum 16, offset 0.000033, synch distance
> 0.00005
> 0.0.0.0: *Not Synchronized*
>
> Does it work? or not work?
> How do I know it?
For looking at current ntp status,
ntpq -p
on the machine in question is a lot more useful than ntptrace.
As ntptrace shows your machine as stratum 16 (maximum distance from
synch provider), it means that it's currently not synchronized.
ntpq prints a list of all synch partners and their communication
status like this:
remote refid st t when poll reach delay offset jitter
==============================================================================
*sol.fo.et.local mars.fo.et.loca 3 u 731 1024 377 0.497 -6.304 0.666
+terra.fo.et.loc sol.fo.et.local 4 u 886 1024 376 0.454 -1.539 0.063
The columns mean (roughly) the following:
- remote: The name (or ip) of each synchronisation provider
- refid: The name (or ip) than provider gets its synch from
- st: The "stratum" (distance in hops from "external" synch such as
GPS or DCF77 receiver)
- t: The type of communications relationship - 'u' is for Unicast
+ Now the rather more interesting ones:
- when: How many seconds ago did your machine talk to this sych
provider
- poll: The interval between asking this synch provider (in seconds)
So this means that 'when' should ordinarily be something between 0 and
poll.
- reach: A bit field describing the success of the last few
communications attempts - 377 is the maximum, the higher the number -
the better. After starting ntpd this (obviously) takes a while to
stabilize. (about 8x poll seconds)
- delay: How long (milliseconds) is the average comm. delay?
- offset: What is the time difference to that provider (also ms)
- jitter: A measurement of the "uncertainty" of the provided synch
times (mostly due to network fluctuations).
In front of the first column symbols may appear:
'*' - this is our current synch provider
'+' - this is not our synch provider, but it appears valid to us.
'-' - this synch provider seems to differ too much from other clock
sources to be used
' ' (no symbol) - this synch provider is unreachable
Also, http://www.eecis.udel.edu/~ntp/ has tons of docs regarding ntp.
After starting ntpd it takes some time (2 - 10 minutes) before the
diagnostic values become meaningful.
The message from ntptrace you posted above seems to indicate that your
ntpd never talked to its synch provider - perhaps you have firewall
rules in place which keep it from doing so? ntpd needs to be able to
reach port 123 UDP of all of its synch providers and receive their
replies.
So long,
Joe
--
"I use emacs, which might be thought of as a thermonuclear
word processor."
-- Neal Stephenson, "In the beginning... was the command line"
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
