NTP Sync don1t work

[Marcelo Fco. Pereira Jr]

Hi Guys...

I still try to create a NTP Server with 3 clients and when I utilize the ntpdate -d do my server the follow message occurs:

ntpdate[2186]: no server suitable for synchronization found

Here is the results of the command ntpdate -d < server>:

transmit(10.20.46.163)
receive(10.20.46.163)
transmit(10.20.46.163)
receive(10.20.46.163)
transmit(10.20.46.163)
receive(10.20.46.163)
transmit(10.20.46.163)
receive(10.20.46.163)
transmit(10.20.46.163)
server 10.20.46.163, port 123
stratum 16, precision -18, leap 11, trust 000
refid [0.0.0.0], delay 0.02602, dispersion 0.00000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 3:28:16.000
originate timestamp: cae1ad09.8536b000 Sun, Nov 11 2007 13:32:09.520
transmit timestamp: cae1ad09.83605000 Sun, Nov 11 2007 13:32:09.513
filter delay: 0.02617 0.02605 0.02602 0.02602
0.00000 0.00000 0.00000 0.00000
filter offset: 0.006968 0.006925 0.006926 0.006927
0.000000 0.000000 0.000000 0.000000
delay 0.02602, dispersion 0.00000
offset 0.006926

11 Nov 13:32:09 ntpdate[2186]: no server suitable for synchronization found

Here is the result of ntpq -p :

remote refid st t when poll reach delay offset disp
==============================================================================
LOCAL(1) LOCAL(1) 10 l 27 64 17 0.00 0.000 1885.01

The ntp.conf from server:

server 127.127.1.1
fudge 127.127.1.1 stratum 10

The ntp.conf from clients:

server

The netdaemons from clientes:

export NTPDATE_SERVER=
export XNTPD=0
export XNTPD_ARGS=

Tks for the Help!!!

[Wouter Jagers]

Hi there,

Unsure here, but maybe it doesn't want to because you're setting the local timeserver to stratum 10. Usually this is done to make sure all other time sources are tried first, but in this case we don't seem to have another source.

Could you try removing the 'stratum 10' line and try again ?

Keep in mind that you might have to wait 5 to 15 minutes for your timeserver to get 'ready for requests'.

Cheers,
Wout

[BUPA IS]

Hello Marcello,

> 11 Nov 13:32:09 ntpdate[2186]: no server suitable for synchronization found

There is no valid clock running into the ntp on the server . I think the lines near the front of the hp supplied ntp.conf example are wrong .
try this to get the local clock driver .

server 127.127.1.0 # local clock
fudge 127.127.1.0 stratum 10

If this is your going to be your " master clock " i would try setting a higher stratum than 10 however remember that unix hardware clocks are quite unreliable .
You have not started the ntp dameons in the clients , setting the clock at boot time only (or on an adhoc basis) could result in erractic time jumps on the clients. Change XNTPD=1 to start the xntpd service on both the clients and the server in /etc/rc.config.d/netdaemons

time in Brazil is distributed by O Observatório Nacional

http://pcdsh01.on.br/
choose SINCRONISMO PÃ BLICO

You can set your master server to get the time from this and let all you clients synchronise with that or use the pools at www.ntp.org

http://www.pool.ntp.org/zone/south-america
good luck
Mike

[rick jones]

Changing the stratum of the local fudged clock may help, but I wouldn't be surprised if ntpdate didn't like a fudged clock regardless of stratum.

It would be a "good thing" to configure some proper time sources if you can - either a local GPS clock or the like, or time from some "upstream" servers, if your firewalls are willing. http://www.pool.ntp.org/ is a good resource.