[ale] NTPD issues

[Ryan Fish]

I am using the same NTP servers on a box I have running here at home without
any trouble.  This box has a dynamic IP assigned by BS on their kooky
schedule...

Why then would I have the same result with different NTP servers just added
today?

Does it matter if the server in question is able to resolve the NTP server
addresses but NOT ping them successfully?  I can ping all the same NTP
servers from other servers in the same network and from my home boxes.
Since I am also able to successfully run NTPD from those same boxes I am
leaning towards this being some sort of a network connectivity issue which I
will need to figure out how to cure.  Make sense?

Anyway, keep the ideas coming!

Thanks again.
-Ryan


----- Original Message ----- 
From: "H. A. Story" <adrin at bellsouth.net>
To: <FishR at bellsouth.net>; "Atlanta Linux Enthusiasts" <ale at ale.org>
Sent: Tuesday, March 08, 2005 9:38 PM
Subject: Re: [ale] NTPD issues


> Hi,
> Looks like a problem I had.  Some ntp servers will start rejecting you
> if you connect to many times during a period, to fix this I just made a
> script that only runs once a day to adjust the clock. This also takes
> care of the jitter problem.
>
> Keep in mind it may not be all you if you are on a dynamic IP.
>
>
> Ryan Fish wrote:
> > I have been successfully using ntpd on a RHEL3 ES server for roughly 1.5
months now.  For some yet unknown reason the service just stopped working
properly yesterday.  By this, I mean the service will run but will not
actually connect to any NTP server I list in ntp.conf.
> >
> > ntpq -p returns the following:
> >
> >      remote           refid      st t when poll reach   delay   offset
jitter
> >
============================================================================
==
> > *LOCAL(0)        LOCAL(0)        10 l    6   64  377    0.000    0.000
0.008
> >  hickory.cc.colu navobs1.wustl.e  2 u   13   64  377   22.013  -129454
4630.18
> >  ns1.usg.edu     ntp0.mcs.anl.go  2 u   37   64  377    2.586  -129254
6320.01
> >  louie.udel.edu  128.4.40.20      2 u   22   64  377   47.435  -129373
5099.01
> >  rubidium.broad. .GPS.            1 u   46   64  377   38.199  -129208
7104.82
> >
> >
> > ntpq -d followed by assoc returns the following even after waiting a
couple hours:
> >
> > ind assID status  conf reach auth condition  last_event cnt
> > ===========================================================
> >   1 59084  9614   yes   yes  none  sys.peer   reachable  1
> >   2 59085  9014   yes   yes  none    reject   reachable  1
> >   3 59086  9014   yes   yes  none    reject   reachable  1
> >   4 59087  9014   yes   yes  none    reject   reachable  1
> >   5 59088  9014   yes   yes  none    reject   reachable  1
> >
> > I have stopped, restarted and added more NTP servers but the service
never actually starts working as it has and should.
> >
> > Any ideas???
> >
> > TIA
> > - Ryan
> >
> >
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://www.ale.org/mailman/listinfo/ale
>
>