[ntp:questions] why is my pool server's offset so bad
Richard B. Gilbert
rgilbert88 at comcast.net
Thu Jan 31 06:26:33 UTC 2008
Pat Farrell wrote:
> On Wed, 30 Jan 2008 23:40:17 -0500, Richard B. Gilbert wrote:
>>>But lately, the offsets are diving down. See
>>Sorry about that. How about supplying some USEFUL information
>>about your server! Knowing what O/S you are running on which hardware
>>platform, what version of ntpd
> I opened it up for general queries so you can ntpq -p and see.
> Its a debian Etch on a dual Xeon (intel 32) platform.
> ntpd 4.2.2p4
> Its got no real clocks, its just a load sharing device, getting good time
> from overworked upstream ntp servers and sharing it with the world
>>It might be helpful to start with the ntpq -p "banner".
> Don't know what you mean by 'banner'
> here is ntpq -p
> pfarrell at noise:/etc$ ntpq -p
> remote refid st t when poll reach delay offset jitter
> ntp-2.cns.vt.ed 18.104.22.168 2 u 31h 64 0 17.908 -0.296 0.000
> ntp-4.cns.vt.ed 22.214.171.124 2 u 31h 64 0 18.567 0.637 0.000
> ancalagon.cede. .INIT. 16 u - 1024 0 0.000 0.000 0.000
> prometheus.acm. .����. 16 u 31h 64 0 0.000 0.000 0.000
> time-b.nist.gov .ACTS. 1 u 31h 64 0 13.555 6.162 0.000
The above is what I mean by "banner".
Yours says that it has been 31 hours since four of your servers last
responded to queries!! It would appear that "ancalagon.cede." has NEVER
responded since ntpd was started!
I just did my own ntpq -p and it is now claiming 32 hours since anybody
responded. Obviously you have not unplugged your network cable but
there must be SOME reason why no one will talk to you!
Could you have done something so naughty that your servers have sent you
the "Kiss Of Death"?
More information about the questions