Re: ntpq no longer working -

Bob Goodwin wrote:

Ok, that produces some meaningful data, I don't know how Mozilla Compose
will mangle it but :

ntpq> host 127.0.0.1
current host set to 127.0.0.1
ntpq> peers
Got packet, size = 32
Packet okay
***Can't find host localhost

This seems to indicate that "localhost" is missing from your /etc/hosts
file. Check that and try the normal "ntpq -p".


remote refid st t when poll reach delay offset
jitter
==============================================================================

Got packet, size = 432
Packet okay
Got packet, size = 220
Packet okay
clock2.redhat.c .CDMA. 1 u 110 1024 377 2030.40 633.536
558.706
Got packet, size = 444
Packet okay
Got packet, size = 220
Packet okay
ntp-1.cns.vt.ed 198.82.247.40 2 u 410 1024 377 2568.57 901.177
706.564
Got packet, size = 440
Packet okay
Got packet, size = 212
Packet okay
*ntp-2.cns.vt.ed 198.82.247.40 2 u 397 1024 377 769.755 -22.853
76.805
Got packet, size = 444
Packet okay
Got packet, size = 212
Packet okay
ntp-3.cns.vt.ed 198.82.247.40 2 u 581 1024 377 1694.40 427.961
328.748
Got packet, size = 440
Packet okay
Got packet, size = 212
Packet okay
+ntp-4.cns.vt.ed 198.82.247.40 2 u 85 1024 377 873.344 46.931
109.827

The delay and offset numbers look pretty high, perhaps system delays via
the satelltie connection?

BobG



--
Take your work seriously but never take yourself seriously; and do not
take what happens either to yourself or your work seriously.
-- Booth Tarkington

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: ntpq no longer working -
    ... ntpq> host 127.0.0.1 ... current host set to 127.0.0.1 ... ntpq> peers ... Packet okay ...
    (Fedora)
  • Re: ntpq no longer working -
    ... clock2.redhat.com server ... But I still can't see what's happening, since ntpq doesn't ... ***No host open, use `host' command ... Packet okay ...
    (Fedora)