Prev: no sound on my hp dv7 notebook using alsa
Next: ntpd still not working
From: root on 2 Nov 2009 05:53
Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote:
> root <NoEMail(a)home.org> wrote:
>> How long does it take for the daemon to fix the
>> clock drift? The daemon has been running for
>> 9 hours and my clock is off by 6 minutes. Without
>> ntpd my clock would have been off by roughly the
>> same amount.
>
> If so it seems as if ntpd hasn't succeeded in keeping your clock
> synchronized. What output do you get from ntptrace?
>
> regards Henrik

I read the man page for ntptrace and for:
ntptrace 0.pool.ntp.org
jabber.sotelips.net: timed out, nothing received
***Request timed out

Similarly for:
ntptrace tick.ucla.edu
tick.ucla.edu: timed out, nothing received
***Request timed out

I can ping both of these servers and they are alive.
Moreover, I ran ntpdate to tick.ucla.edu just
before starting ntpd. The daemon opens and locks
a socket, but it isn't talking to anyone.
From: Giovanni on 2 Nov 2009 06:01
On 11/02/09 11:44, root wrote:

> I just re-started ntpd, after deciding it wasn't helping. After a
> few seconds of operation ntptrace yields:
> localhost: stratum 16, offset 0.000000, synch distance 0.000210
>
> I don't have a man entry for ntptrace, what should I be looking
> for?

It simply means that your ntp server can't get to any time server and
it it is synchronizing on the local clock.

Is your network working?

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
< http://giovanni.homelinux.net/ >
From: root on 2 Nov 2009 06:23
root <NoEMail(a)home.org> wrote:
> Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote:
>> root <NoEMail(a)home.org> wrote:
>>> How long does it take for the daemon to fix the
>>> clock drift? The daemon has been running for
>>> 9 hours and my clock is off by 6 minutes. Without
>>> ntpd my clock would have been off by roughly the
>>> same amount.
>>
>> If so it seems as if ntpd hasn't succeeded in keeping your clock
>> synchronized. What output do you get from ntptrace?
>>
>> regards Henrik
>
> I read the man page for ntptrace and for:
> ntptrace 0.pool.ntp.org
> jabber.sotelips.net: timed out, nothing received
> ***Request timed out
>
> Similarly for:
> ntptrace tick.ucla.edu
> tick.ucla.edu: timed out, nothing received
> ***Request timed out
>
> I can ping both of these servers and they are alive.
> Moreover, I ran ntpdate to tick.ucla.edu just
> before starting ntpd. The daemon opens and locks
> a socket, but it isn't talking to anyone.

I had started ntpd with an old /etc/rc.d/rc.ntpd script.
When I use rc.ntpd.new I can get a connection. Here is
what I see:

ntptrace tick.ucla.edu
tick.ucla.edu: timed out, nothing received
***Request timed out

ntptrace 0.pool.ntp.org
0.pool.ntp.org: stratum 2, offset -0.000071, synch distance 0.045360
clock.trit.net: timed out, nothing received
***Request timed out

ntptrace 1.pool.ntp.org
1.pool.ntp.org: timed out, nothing received
***Request timed out

ntptrace 2.pool.ntp.org
2.pool.ntp.org: stratum 2, offset 0.000666, synch distance 0.073360
***Association ID 54222 unknown to server

ntptrace 3.pool.ntp.org
3.pool.ntp.org: stratum 3, offset 0.000119, synch distance 0.044794
10.1.11.61: timed out, nothing received
***Request timed out

Without any argument to ntptrace I just get:
localhost: stratum 11, offset 0.000000, synch distance 0.206585

At this time my /etc/ntp.conf file is:
server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10
multicastclient # listen on default 224.0.1.1
broadcastdelay 0.008
keys /etc/ntp/keys
trustedkey 65535
requestkey 65535
controlkey 65535
driftfile /etc/ntp/drift
pidfile /var/run/ntpd.pid
server 0.pool.ntp.org
server 1.pool.ntp.org
server 2.pool.ntp.org
server 3.pool.ntp.org
server tick.ucla.edu
From: Giovanni on 2 Nov 2009 07:41
On 11/02/09 12:23, root wrote:
> root <NoEMail(a)home.org> wrote:
>> Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote:
>>> root <NoEMail(a)home.org> wrote:
>>>> How long does it take for the daemon to fix the
>>>> clock drift? The daemon has been running for
>>>> 9 hours and my clock is off by 6 minutes. Without
>>>> ntpd my clock would have been off by roughly the
>>>> same amount.
>>> If so it seems as if ntpd hasn't succeeded in keeping your clock
>>> synchronized. What output do you get from ntptrace?
>>>
>>> regards Henrik
>> I read the man page for ntptrace and for:
>> ntptrace 0.pool.ntp.org
>> jabber.sotelips.net: timed out, nothing received
>> ***Request timed out
>>
>> Similarly for:
>> ntptrace tick.ucla.edu
>> tick.ucla.edu: timed out, nothing received
>> ***Request timed out
>>
>> I can ping both of these servers and they are alive.
>> Moreover, I ran ntpdate to tick.ucla.edu just
>> before starting ntpd. The daemon opens and locks
>> a socket, but it isn't talking to anyone.
>
> I had started ntpd with an old /etc/rc.d/rc.ntpd script.
> When I use rc.ntpd.new I can get a connection. Here is
> what I see:
>
> ntptrace tick.ucla.edu
> tick.ucla.edu: timed out, nothing received
> ***Request timed out
>
> ntptrace 0.pool.ntp.org
> 0.pool.ntp.org: stratum 2, offset -0.000071, synch distance 0.045360
> clock.trit.net: timed out, nothing received
> ***Request timed out
>
> ntptrace 1.pool.ntp.org
> 1.pool.ntp.org: timed out, nothing received
> ***Request timed out
>
> ntptrace 2.pool.ntp.org
> 2.pool.ntp.org: stratum 2, offset 0.000666, synch distance 0.073360
> ***Association ID 54222 unknown to server
>
> ntptrace 3.pool.ntp.org
> 3.pool.ntp.org: stratum 3, offset 0.000119, synch distance 0.044794
> 10.1.11.61: timed out, nothing received
> ***Request timed out
>
> Without any argument to ntptrace I just get:
> localhost: stratum 11, offset 0.000000, synch distance 0.206585
>
> At this time my /etc/ntp.conf file is:
> server 127.127.1.0 # local clock
> fudge 127.127.1.0 stratum 10
> multicastclient # listen on default 224.0.1.1
> broadcastdelay 0.008
> keys /etc/ntp/keys
> trustedkey 65535
> requestkey 65535
> controlkey 65535
> driftfile /etc/ntp/drift
> pidfile /var/run/ntpd.pid
> server 0.pool.ntp.org
> server 1.pool.ntp.org
> server 2.pool.ntp.org
> server 3.pool.ntp.org
> server tick.ucla.edu

My ntp.conf file looks as follows:
## Remote servers (I'm in northern Italy :-) )
server it.pool.ntp.org ## Stratum 2/3 servers
server ch.pool.ntp.org ## Stratum 2/3 servers
## Use local server from LAN as preferred
server milena.home.net.it prefer

## Local clock source
server 127.127.1.0
fudge 127.127.1.0 stratum 10

## Drift file
driftfile /etc/ntp/drift

#multicastclient # listen on default 224.0.1.1
#broadcastdelay 0.008

## Keys file
keys /etc/ntp/ntp.keys
#trustedkey 65535
#requestkey 65535
#controlkey 65535

## Don't serve time or stats or trust anyone else
restrict default noquery nomodify # notrust
restrict localhost

## Work files
# logfile /var/log/ntpd.log
pidfile /var/run/ntpd.pid

## end ntp.conf


I'm not sure, but I think you have to comment the keys ID and the
multicast ditective. ntptrace should give the hierarchy of used ntp
servers.

# root(a)monica:~ > ntptrace
localhost: stratum 3, offset -0.001629, synch distance 0.073363
milena.home.net.it: stratum 2, offset -0.000408, synch \
distance 0.035561
ntp1.inrim.it: stratum 1, offset -0.000033, synch \
distance 0.000138, refid 'UTCI'
# root(a)monica:~ >

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
< http://giovanni.homelinux.net/ >
From: root on 2 Nov 2009 07:51
Giovanni <lsodgf0(a)home.net.it> wrote:
>
> I'm not sure, but I think you have to comment the keys ID and the
> multicast ditective. ntptrace should give the hierarchy of used ntp
> servers.
>
> # root(a)monica:~ > ntptrace
> localhost: stratum 3, offset -0.001629, synch distance 0.073363
> milena.home.net.it: stratum 2, offset -0.000408, synch \
> distance 0.035561
> ntp1.inrim.it: stratum 1, offset -0.000033, synch \
> distance 0.000138, refid 'UTCI'
> # root(a)monica:~ >
>
> Ciao
> Giovanni

I have tried commenting out the keys stuff, but the
ntptrace command, without specifying a server, never
goes anywhere.

I have been running a sequence of these steps:
source /etc/rc.d/rc.ntpd stop
modify /etc/ntp.conf
source /etc/rc.d/rc.ntpd start
ntptrace

Repeat over and over. So far no luck.

I'll try your conf file as is.
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: no sound on my hp dv7 notebook using alsa
Next: ntpd still not working