using clock2.redhat.com with ntpd causes failure

Harry Putnam reader at newsguy.com
Tue Apr 13 03:16:09 UTC 2004


"Charles R. Anderson" <cra at WPI.EDU> writes:

> On Sat, Apr 10, 2004 at 01:59:06PM -0500, Harry Putnam wrote:
>> I was under the impression that clock2.redhat.com was usable for ntpd.
>> But a little test with rdate shows the possible source of failure:
>> 
>>    rdate -p clock2.redhat.com
>>    Alarm clock
>
> rdate does not talk NTP.  Try ntpdate (while ntpd is not running).

  # ntpdate -q clock2.redhat.com
  Looking for host clock2.redhat.com and service ntp
  host found : clock3.redhat.com
  server 209.132.176.4, stratum 0, offset 0.000000, delay 0.00000
  12 Apr 22:15:17 ntpdate[12261]: no server suitable for synchronization found

Are you able to synchronize on clock2?





More information about the test mailing list