ntp help
Lennart Sorensen
lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org
Wed Jul 11 17:41:58 UTC 2007
On Wed, Jul 11, 2007 at 01:35:18PM -0400, Neil Watson wrote:
> I have configured some NTP servers to synchronise with some public, stratum
> 2,
> NTP servers. Now I'm trying to configure a client to synchronise with my new
> NTP servers. The test client reports that it is more accurate than the new
> servers:
>
> [root at tor-lx-config config]# ntpq -pn
> remote refid st t when poll reach delay offset
> jitter
> ==============================================================================
> 192.168.71.12 .INIT. 16 u - 1024 0 0.000 0.000
> 4000.00
> 192.168.71.42 .INIT. 16 u - 1024 0 0.000 0.000
> 4000.00
> 192.168.71.43 .INIT. 16 u - 1024 0 0.000 0.000
> 4000.00
> *127.127.1.0 LOCAL(0) 10 l 50 64 377 0.000 0.000
> 0.002
>
> Why are the new servers reported at stratum 16?
I think .INIT. means it hasn't run long enough to get a feel for the
time from that server. Or perhaps it isn't even able to talk to that
server. Firewall issues perhaps?
It normally ends up looking like this:
# ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
*85.214.46.68 131.188.3.221 2 u 1 64 377 120.248 -430.72 68.783
127.127.1.0 LOCAL(0) 10 l 61 64 377 0.000 0.000 0.004
What does your config look like?
--
Len Sorensen
--
The Toronto Linux Users Group. Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists
More information about the Legacy
mailing list