[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
Mike
On 03/08/2005 02:06 PM, Jim Patterson wrote:
> 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
>><a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
>>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
--
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Mike Murphy
781 Inman Mews Drive Atlanta GA 30307
Landline: 404-653-1070
Mobile: 404-545-6234
Email: mike at tyderia.net
AIM: mmichael453
JDAM: 33:45:14.0584N 84:21:43.038W
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00147" href="msg00147.html">[ale] NTPD issues</a></strong>
<ul><li><em>From:</em> fishr at bellsouth.net (Ryan Fish)</li></ul></li>
<li><strong><a name="00149" href="msg00149.html">[ale] NTPD issues</a></strong>
<ul><li><em>From:</em> unixdude at gmail.com (Jim Patterson)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00151.html">[ale] Trying to install on a new dell</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00153.html">[ale] Trying to install on a new dell</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00149.html">[ale] NTPD issues</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00169.html">[ale] NTPD issues</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00152"><strong>Date</strong></a></li>
<li><a href="threads.html#00152"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>