[ale] NTPD issues

[Jim Patterson]

Ryan,

Those offset and jitter values are HUGE.  Is your local clock
significantly wrong?

I would suggest replacing yuor ntp config with:
driftfile /var/lib/ntp/ntp.drift
server 0.us.pool.ntp.org
server 1.us.pool.ntp.org
server 2.us.pool.ntp.org

That will get you three (more or less at random) different public ntp servers.

Once that is ready, stop your ntp client and do a:
ntpdate -u pool.ntp.org

That will force your clock to be correct, then you can restart ntpd.

If that does not work, let if run for a little while then post your nptq info
like you did before.

Jim Patterson


On Tue, 8 Mar 2005 13:23:35 -0500, Ryan Fish <fishr at bellsouth.net> 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
>