SEO

Hi,
I can't sync my PC's clock with ANY NTP server (including pool.ntp.org).
Whenever I try, using MCC, (even with firewall shut down temporarily),
several tens of seconds pass till I eventually get the message it couldn't
connect with the chosen server.

The respective syslog is:
Nov 26 08:17:51 Atlantis clock.pl[8413]: ### Program is starting ###
Nov 26 08:17:52 Atlantis clock.pl[8413]: running: /bin/rpm -q --qf %{name}
ntp
Nov 26 08:18:04 Atlantis clock.pl[8413]: modified file /etc/ntp.conf
Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command: /sbin/chkconfig
--level 35 ntpd on
Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command: service ntpd stop
Nov 26 08:18:04 Atlantis ntpd[5764]: ntpd exiting on signal 15
Nov 26 08:18:04 Atlantis ntpd: ntpd shutdown succeeded
Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command: /usr/sbin/ntpdate
pool.nrp.org
Nov 26 08:20:45 Atlantis clock.pl[8413]: ### Program is exiting ###
Nov 26 08:20:47 Atlantis drakconf.real[8382]: modified file /etc/mcc.conf

My OS: Fully updated Mandriva 2006_64.
I'm permanently connected to my LAN with includes an ADSL modem router that
acts as my gateway.

TIA

Michael Badt wrote:
> Hi,
> I can't sync my PC's clock with ANY NTP server (including pool.ntp.org).
> Whenever I try, using MCC, (even with firewall shut down temporarily),
> several tens of seconds pass till I eventually get the message it couldn't
> connect with the chosen server.
>
> The respective syslog is:
> Nov 26 08:17:51 Atlantis clock.pl[8413]: ### Program is starting ###
> Nov 26 08:17:52 Atlantis clock.pl[8413]: running: /bin/rpm -q --qf %{name}
> ntp
> Nov 26 08:18:04 Atlantis clock.pl[8413]: modified file /etc/ntp.conf
> Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command: /sbin/chkconfig
> --level 35 ntpd on
> Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command: service ntpd stop
> Nov 26 08:18:04 Atlantis ntpd[5764]: ntpd exiting on signal 15
> Nov 26 08:18:04 Atlantis ntpd: ntpd shutdown succeeded

This can be due to the clock being too far off the NTP time.
To prevent time jumps, the NTP daemon limits the error it's
willing to correct.

> Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command: /usr/sbin/ntpdate
> pool.nrp.org

There is no server 'pool.nrp.org'. Please check the script for
a misprint: 'pool.ntp.org' exists.

Try running the ntpdate command manually, as root.

--

Tauno Voipio
tauno voipio (at) iki fi

Thnaks Tauno,
I foolowed your recommendation, for several ntp servers with the following
result:
26 Nov 13:36:06 ntpdate[8475]: ntpdate 4.2.0@1.1161-r Thu Sep 8 10:35:44
CEST 2005 (1)
26 Nov 13:36:06 ntpdate[8475]: no servers can be used, exiting

Any idea?

Tauno Voipio wrote:

> Michael Badt wrote:
>> Hi,
>> I can't sync my PC's clock with ANY NTP server (including pool.ntp.org).
>> Whenever I try, using MCC, (even with firewall shut down temporarily),
>> several tens of seconds pass till I eventually get the message it
>> couldn't connect with the chosen server.
>>
>> The respective syslog is:
>> Nov 26 08:17:51 Atlantis clock.pl[8413]: ### Program is starting ###
>> Nov 26 08:17:52 Atlantis clock.pl[8413]: running: /bin/rpm -q --qf
>> %{name} ntp
>> Nov 26 08:18:04 Atlantis clock.pl[8413]: modified file /etc/ntp.conf
>> Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command:
>> /sbin/chkconfig --level 35 ntpd on
>> Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command: service ntpd
>> stop Nov 26 08:18:04 Atlantis ntpd[5764]: ntpd exiting on signal 15
>> Nov 26 08:18:04 Atlantis ntpd: ntpd shutdown succeeded
>
> This can be due to the clock being too far off the NTP time.
> To prevent time jumps, the NTP daemon limits the error it's
> willing to correct.
>
>> Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command:
>> /usr/sbin/ntpdate pool.nrp.org
>
> There is no server 'pool.nrp.org'. Please check the script for
> a misprint: 'pool.ntp.org' exists.
>
> Try running the ntpdate command manually, as root.
>

Michael Badt wrote:

> Thnaks Tauno,
> I foolowed your recommendation, for several ntp servers with the following
> result:
> 26 Nov 13:36:06 ntpdate[8475]: ntpdate 4.2.0@1.1161-r Thu Sep 8 10:35:44
> CEST 2005 (1)
> 26 Nov 13:36:06 ntpdate[8475]: no servers can be used, exiting
>
> Any idea?

What is the output of the command (as root);

/usr/sbin/ntpdate -u us.pool.ntp.org


--
"A personal computer is called a personal computer because it's yours,
Anything that runs on that computer, you should have control over."
Andrew Moss, Microsoft's senior director of technical policy, 2005

On Sat, 26 Nov 2005 13:38:20 +0200, Michael Badt shouted Hoy......


>
> Thnaks Tauno,
> I foolowed your recommendation, for several ntp servers with the
> following result:
> 26 Nov 13:36:06 ntpdate[8475]: ntpdate 4.2.0@1.1161-r Thu Sep 8
> 10:35:44 CEST 2005 (1)
> 26 Nov 13:36:06 ntpdate[8475]: no servers can be used, exiting
>
> Any idea?
>
> Tauno Voipio wrote:
>
>
[putulin]

Yes, give ntpdate a "server" to use as in this example:

/usr/sbin/ntpdate time-a.nist.gov

which returns

[root@client-1 ~]# /usr/sbin/ntpdate time-a.nist.gov 26 Nov 07:36:27
ntpdate[4295]: adjust time server 129.6.15.28 offset -0.032740 sec

If you are running ntpd on the same boxen then make sure ntpd is not
running when you try ntpdate.

If it is, this is what will happen:

-bash-3.00# ntpdate time-a.nist.gov
Looking for host time-a.nist.gov and service ntp host found :
time-a.nist.gov
26 Nov 07:34:35 ntpdate[17073]: the NTP socket is in use, exiting

--
Dancin' in the ruins tonight
mail: echo onub-hgbg@pbyhzohf.ee.pbz | perl -pe 'y/a-z/n-za-m/'
Tayo'y Mga Pinoy

Michael Badt wrote:
> Thnaks Tauno,
> I foolowed your recommendation, for several ntp servers with the following
> result:
> 26 Nov 13:36:06 ntpdate[8475]: ntpdate 4.2.0@1.1161-r Thu Sep 8 10:35:44
> CEST 2005 (1)
> 26 Nov 13:36:06 ntpdate[8475]: no servers can be used, exiting
>
> Any idea?
>
> Tauno Voipio wrote:
>
>
>>Michael Badt wrote:
>>
>>>Hi,
>>>I can't sync my PC's clock with ANY NTP server (including pool.ntp.org).
>>>Whenever I try, using MCC, (even with firewall shut down temporarily),
>>>several tens of seconds pass till I eventually get the message it
>>>couldn't connect with the chosen server.
>>>
>>>The respective syslog is:
>>>Nov 26 08:17:51 Atlantis clock.pl[8413]: ### Program is starting ###
>>>Nov 26 08:17:52 Atlantis clock.pl[8413]: running: /bin/rpm -q --qf
>>>%{name} ntp
>>>Nov 26 08:18:04 Atlantis clock.pl[8413]: modified file /etc/ntp.conf
>>>Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command:
>>>/sbin/chkconfig --level 35 ntpd on
>>>Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command: service ntpd
>>>stop Nov 26 08:18:04 Atlantis ntpd[5764]: ntpd exiting on signal 15
>>>Nov 26 08:18:04 Atlantis ntpd: ntpd shutdown succeeded
>>
>>This can be due to the clock being too far off the NTP time.
>>To prevent time jumps, the NTP daemon limits the error it's
>>willing to correct.
>>
>>
>>>Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command:
>>>/usr/sbin/ntpdate pool.nrp.org
>>
>>There is no server 'pool.nrp.org'. Please check the script for
>>a misprint: 'pool.ntp.org' exists.
>>
>>Try running the ntpdate command manually, as root.

NTP is using UDP port 123 for both directions. Check that
there is nothing blocking these packets.

In the really bad case, your ISP (Actcom?) is eating them.
Ask if there is a NTP server in the ISP network.

HTH

--

Tauno Voipio
tauno voipio (at) iki fi

"Tauno Voipio" <tauno.voipio@INVALIDiki.fi> wrote in message
news:f9Whf.58$sG3.36@read3.inet.fi...
> Michael Badt wrote:
>> Hi,
>> I can't sync my PC's clock with ANY NTP server (including pool.ntp.org).
>> Whenever I try, using MCC, (even with firewall shut down temporarily),
>> several tens of seconds pass till I eventually get the message it
>> couldn't
>> connect with the chosen server.
>>
>> The respective syslog is:
>> Nov 26 08:17:51 Atlantis clock.pl[8413]: ### Program is starting ###
>> Nov 26 08:17:52 Atlantis clock.pl[8413]: running: /bin/rpm -q --qf
>> %{name} ntp
>> Nov 26 08:18:04 Atlantis clock.pl[8413]: modified file /etc/ntp.conf
>> Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command:
>> /sbin/chkconfig
>> --level 35 ntpd on
>> Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command: service ntpd
>> stop
>> Nov 26 08:18:04 Atlantis ntpd[5764]: ntpd exiting on signal 15
>> Nov 26 08:18:04 Atlantis ntpd: ntpd shutdown succeeded
>
> This can be due to the clock being too far off the NTP time.
> To prevent time jumps, the NTP daemon limits the error it's
> willing to correct.

Quite true. If you take a look at the init script in /etc/init.d/ntp or
/etc/init.d/ntpd, it will usually do a pre-start with the members of
/etc/ntp/step-tickers when starting up, and if there's nothing in
/etc/ntp/step-tickers some setups will use the servers in /etc/ntp.conf.
Doing a restart with "/etc/init.d/ntpd restart" will help that. I've seen it
happen when the network wasn't available when booting the machine.

>> Nov 26 08:18:04 Atlantis clock.pl[8413]: launched command:
>> /usr/sbin/ntpdate
>> pool.nrp.org
>
> There is no server 'pool.nrp.org'. Please check the script for
> a misprint: 'pool.ntp.org' exists.

Ahh. He has a typo, it should be pool.ntp.org.

> Try running the ntpdate command manually, as root.

All your advice was good.

Thanks all,
I've verified that my gw doesn't block port 123.
Yet still I can't find any servers.

Any idea?

Here's the output from both commands (as root):
=========
[root@Atlantis miki]# /usr/sbin/ntpdate time-a.nist.gov
Looking for host time-a.nist.gov and service ntp
host found : 1.0.0.0
26 Nov 18:15:29 ntpdate[11138]: no server suitable for synchronization found
[root@Atlantis miki]#
[root@Atlantis miki]# /usr/sbin/ntpdate -u us.pool.ntp.org
Looking for host us.pool.ntp.org and service ntp
host found : 1.0.0.0
26 Nov 18:16:18 ntpdate[11145]: no server suitable for synchronization found


Lenard wrote:

> Michael Badt wrote:
>
>> Thnaks Tauno,
>> I foolowed your recommendation, for several ntp servers with the
>> following result:
>> 26 Nov 13:36:06 ntpdate[8475]: ntpdate 4.2.0@1.1161-r Thu Sep 8 10:35:44
>> CEST 2005 (1)
>> 26 Nov 13:36:06 ntpdate[8475]: no servers can be used, exiting
>>
>> Any idea?
>
> What is the output of the command (as root);
>
> /usr/sbin/ntpdate -u us.pool.ntp.org
>
>

On Sat, 26 Nov 2005 17:18:36 +0100, Michael Badt <mibadt@gmail.com> wrote:

> Thanks all,
> I've verified that my gw doesn't block port 123.
> Yet still I can't find any servers.
>
> Any idea?
>
> Here's the output from both commands (as root):
> =========
> [root@Atlantis miki]# /usr/sbin/ntpdate time-a.nist.gov
> Looking for host time-a.nist.gov and service ntp
> host found : 1.0.0.0

But what is this? Host 1.0.0.0 ???? This looks like there is something
very wrong with the host name resolution.

Time-a.nist.gov has address 129.6.15.28.

> 26 Nov 18:15:29 ntpdate[11138]: no server suitable for synchronization found
> [root@Atlantis miki]#
> [root@Atlantis miki]# /usr/sbin/ntpdate -u us.pool.ntp.org
> Looking for host us.pool.ntp.org and service ntp
> host found : 1.0.0.0

What? Address 1.0.0.0 again? Very recently in this or another newsgroup,
someone had this address showing up, but I wasn't able to find back to it.

Anyway, us.pool-ntp.org has a bunch of addresses:

$ dig us.pool-ntp.org
[...]
;; ANSWER SECTION:
us.pool.ntp.org. 1500 IN A 24.34.79.42
us.pool.ntp.org. 1500 IN A 65.19.139.44
us.pool.ntp.org. 1500 IN A 65.75.183.220
us.pool.ntp.org. 1500 IN A 66.115.136.4
us.pool.ntp.org. 1500 IN A 67.64.199.49
us.pool.ntp.org. 1500 IN A 67.159.5.116
us.pool.ntp.org. 1500 IN A 72.25.72.228
us.pool.ntp.org. 1500 IN A 204.17.42.199
us.pool.ntp.org. 1500 IN A 207.145.113.115
us.pool.ntp.org. 1500 IN A 208.201.242.2
us.pool.ntp.org. 1500 IN A 209.237.225.10
us.pool.ntp.org. 1500 IN A 217.160.252.229
[...]

What output do you get from name resolution commands like "dig",
or "host"? What address is shown in the output from "ping"? Here
is mine:

$ ping us.pool.ntp.org
PING us.pool.ntp.org (217.160.252.229) 56(84) bytes of data.

Unless you get something valid here, forget about ntp problems, you
have a name resolution problem. Notice that dig/host may be doing
its things differently from "ping". I presume ntpd and ntpdate use
the "gethostbyname()" function, which is probably what "ping" also
does. Therefore, "ping" is probably the most telling here.

> 26 Nov 18:16:18 ntpdate[11145]: no server suitable for synchronization found

-Enrique

Michael Badt wrote:

> Thanks all,
> I've verified that my gw doesn't block port 123.
> Yet still I can't find any servers.
>
> Any idea?

One, try; /usr/sbin/ntpdate -u 128.10.252.7



--
"A personal computer is called a personal computer because it's yours,
Anything that runs on that computer, you should have control over."
Andrew Moss, Microsoft's senior director of technical policy, 2005