How far off is your current time from the ntp server's time? If
they're way out of whack, I think ntp will refuse to synchronize. I
forget how large of a disparity it will handle, but if they're an
entire hour different, it might just do nothing. I'd expect an error
message in that case, though. Try setting the system time with 'date'
to something close to the ntp server's time, then start up the ntp
process again.
alex
On Aug 25, 2009, at 2:43 PM, Steven A. DuChene wrote:
> Hmm, Here it never starts doing those transmit packets after
> locating the servers.
>
> I just tried it with the firewall turned off and I still get the
> same result so it must not be the firewall.
> I am on a Cox cable modem. I wonder if Cox blocks NTP on their
> network?
> --
> Steve
>
> -----Original Message-----
>> From: Eric Shubert <ejs@shubes.net>
>> Sent: Aug 25, 2009 3:33 PM
>> To: plug-discuss@lists.plug.phoenix.az.us
>> Subject: Re: correct way to set timezone & clock/date?
>>
>> Here's what I get on a test server of mine:
>> [root@dellefield ~]# ntpdate -v -d dewey.lib.ci.phoenix.az.us
>> ntp.drydog.com
>> 25 Aug 12:28:28 ntpdate[6149]: ntpdate 4.2.2p1@1.1570-o Tue May 19
>> 13:58:06 UTC 2009 (1)
>> Looking for host dewey.lib.ci.phoenix.az.us and service ntp
>> host found : dewey.lib.ci.phoenix.az.us
>> Looking for host ntp.drydog.com and service ntp
>> host found : rrcs-66-27-60-10.west.biz.rr.com
>> transmit(148.167.132.200)
>> receive(148.167.132.200)
>> transmit(148.167.132.200)
>> receive(148.167.132.200)
>> transmit(148.167.132.200)
>> transmit(66.27.60.10)
>> receive(148.167.132.200)
>> transmit(148.167.132.200)
>> receive(148.167.132.200)
>> transmit(148.167.132.200)
>> receive(66.27.60.10)
>> transmit(66.27.60.10)
>> receive(66.27.60.10)
>> transmit(66.27.60.10)
>> receive(66.27.60.10)
>> transmit(66.27.60.10)
>> receive(66.27.60.10)
>> transmit(66.27.60.10)
>> server 148.167.132.200, port 123
>> stratum 2, precision -20, leap 00, trust 000
>> refid [148.167.132.200], delay 0.09081, dispersion 0.01126
>> transmitted 4, in filter 4
>> reference time: ce3eb3eb.9159d1f0 Tue, Aug 25 2009 12:03:07.567
>> originate timestamp: ce3eb9de.49e55521 Tue, Aug 25 2009 12:28:30.288
>> transmit timestamp: ce3eb9de.43a0f909 Tue, Aug 25 2009 12:28:30.264
>> filter delay: 0.11383 0.13196 0.11774 0.09081
>> 0.00000 0.00000 0.00000 0.00000
>> filter offset: 0.002299 0.012727 0.005610 -0.00813
>> 0.000000 0.000000 0.000000 0.000000
>> delay 0.09081, dispersion 0.01126
>> offset -0.008137
>>
>> server 66.27.60.10, port 123
>> stratum 2, precision -21, leap 00, trust 000
>> refid [66.27.60.10], delay 0.28584, dispersion 0.00227
>> transmitted 4, in filter 4
>> reference time: ce3eb980.f314d607 Tue, Aug 25 2009 12:26:56.949
>> originate timestamp: ce3eb9df.19c5555c Tue, Aug 25 2009 12:28:31.100
>> transmit timestamp: ce3eb9de.f711a543 Tue, Aug 25 2009 12:28:30.965
>> filter delay: 0.29257 0.28622 0.28584 0.30823
>> 0.00000 0.00000 0.00000 0.00000
>> filter offset: 0.002869 0.004561 0.005198 -0.00578
>> 0.000000 0.000000 0.000000 0.000000
>> delay 0.28584, dispersion 0.00227
>> offset 0.005198
>>
>> 25 Aug 12:28:31 ntpdate[6149]: adjust time server 148.167.132.200
>> offset
>> -0.008137 sec
>> [root@dellefield ~]#
>>
>> So the ntp servers are ok. Are you in a position to stop the firewall
>> momentarily for a test to be sure that's where your blockage is?
>>
>> Steven A. DuChene wrote:
>>> I ran the following:
>>>
>>> ntpdate -v -d dewey.lib.ci.phoenix.az.us ntp.drydog.com
>>>
>>> and it looked for and found both hosts but then just sits there with
>>> no other output.
>>> --
>>> Steve
>>>
>>>
>>> -----Original Message-----
>>> From: Eric Cope
>>> Sent: Aug 25, 2009 3:10 PM
>>> To: Main PLUG discussion list
>>> Subject: Re: correct way to set timezone & clock/date?
>>>
>>> You can force an update, instead of waiting on the incremental
>>> changes. But, as noted below, it may affect services.
>>> Eric
>>>
>>> On Tue, Aug 25, 2009 at 11:42 AM, Jon M. Hanson
>>> <jon@the-hansons-az.net <mailto:jon@the-hansons-az.net>> wrote:
>>>
>>> ntp also adjusts your clock gradually so it won't immediately
>>> jump to
>>> the correct time. This is to prevent problems with services
>>> (like cron
>>> and logging) that depend on a clock that doesn't suddenly
>>> change.
>>>
>>> Sent from my iPhone
>>>
>>> On Aug 25, 2009, at 11:33 AM, Alex Dean <alex@crackpot.org
>>> <mailto:alex@crackpot.org>> wrote:
>>>
>>>> Try tailing /var/log/messages (you said this was fedora, right?)
>>>> when you start up the ntp daemon. It can take a while (>1 minute
>>>> sometimes) for the time servers to synchronize, but you
>>> should see
>>>> some log activity during that time to show you that it's working.
>>>>
>>>> alex
>>>>
>>>> On Aug 25, 2009, at 1:27 PM, Steven A. DuChene wrote:
>>>>
>>>>> Hmm, so I did the following:
>>>>>
>>>>> # iptables -A input_ext -p tcp -m tcp --dport 123 -j ACCEPT
>>>>>
>>>>> and then tried starting ntp services again but it still
>>> seems to hang
>>>>> when trying to get the initial date and time. So adding a
>>> rule to the
>>>>> firewall for tcp access on port 123 seems to have made no
>>> difference
>>>>> to my problem.
>>>>>
>>>>> nuts...
>>>>> --
>>>>> Steve
>>>>>
>>>>> -----Original Message-----
>>>>>> From: "kitepilot@kitepilot.com
>>> <mailto:kitepilot@kitepilot.com>" <kitepilot@kitepilot.com
>>> <mailto:kitepilot@kitepilot.com>>
>>>>>> Sent: Aug 25, 2009 2:13 PM
>>>>>> To: "Steven A. DuChene" <linux-clusters@mindspring.com
>>> <mailto:linux-clusters@mindspring.com>>, Main PLUG
>>>>>> discussion list <plug-discuss@lists.plug.phoenix.az.us
>>> <mailto:plug-discuss@lists.plug.phoenix.az.us>>
>>>>>> Subject: Re: correct way to set timezone & clock/date?
>>>>>>
>>>>>> From /etc/services
>>>>>>
>>>>>> ntp 123/tcp
>>>>>> ntp 123/udp # Network Time
>>>>>> Protocol
>>>>>>
>>>>>> I would use "ntp" instead of "udp", and if it doesn't work,
>>> take a
>>>>>> dump...
>>>>>> :)
>>>>>> ET
>>>>>>
>>>>>
>>>>> ---------------------------------------------------
>>>>> PLUG-discuss mailing list -
>>> PLUG-discuss@lists.plug.phoenix.az.us
>>> <mailto:PLUG-discuss@lists.plug.phoenix.az.us>
>>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>>>>
>>>>
>>>> ---------------------------------------------------
>>>> PLUG-discuss mailing list -
>>> PLUG-discuss@lists.plug.phoenix.az.us
>>> <mailto:PLUG-discuss@lists.plug.phoenix.az.us>
>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list -
>>> PLUG-discuss@lists.plug.phoenix.az.us
>>> <mailto:PLUG-discuss@lists.plug.phoenix.az.us>
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>>>
>>>
>>>
>>>
>>> --
>>> Eric Cope
>>> http://cope-et-al.com
>>>
>>>
>>
>>
>> --
>> -Eric 'shubes'
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
(text/plain)
