[ntp:questions] Impossible to "ntpdate" a client using an orphan mode server

mister_zed at voila.fr mister_zed at voila.fr
Wed Jun 24 20:15:36 UTC 2015


Hello Hans,

Thanks for trying to help me, but in reality it is much less than 41ms (this trace given was not caught on my plateform). 
But, ntpdate is normally able to synchronize to time servers with much more than 41ms of delay (example : on my PC, I can use ntpdate to synchronize to wwv.nist.gov (located in Fort Collins, Colorado). I am in Paris, France, at something like 7 or 8,000km, so with much more than 41 ms of delay...

The only workaround I found consists in using "ntpd -q -g" instead of "ntpdate"... In my opinion, using "orphan mode" instead of "undiscipline local clock" driver introduces regressions...

For info, I am using v4.2.8 compiled by Meinberg.

Regards

> Message du 24/06/15 à 16h55
> De : "MAYER Hans" 
> A : "questions at lists.ntp.org" 
> Copie à : 
> Objet : Re: [ntp:questions] Impossible to "ntpdate" a client using an orphan mode server
> 
> 
> Wow,
> You have a delay of 41.062 ms within a switched network ? 
> This is pretty high.
> I am typically below 0.5 ms and about 2 ms into the Internet. 
> Maybe you should look for network issues first.
> 
> // Hans
> 
> 
> 
> -----Original Message-----
> From: questions [mailto:questions-bounces+mayer=iiasa.ac.at at lists.ntp.org] On Behalf Of mister_zed at voila.fr
> Sent: Monday, June 22, 2015 11:42 PM
> To: questions at lists.ntp.org
> Subject: [ntp:questions] Impossible to "ntpdate" a client using an orphan mode server
> 
> Hello,
> my network is quite simple : 1 server and 2 clients linked by an ethernet switch.
> 
> Server configuration (@IP 10.1.1.21):
> tos orphan 12
> 
> Clients have the same config :
> server 10.1.1.21 iburst
> 
> On both client 1 & 2, ntpq -p shows something like:
> remote refid st t when poll reach delay offset jitter ==============================================================================
> *10.1.1.21 127.0.0.1 2 u 307 12 377 41.062 0.504 0.877
> 
> I think the "*" shows that server is correctly configured and operational. Clients 1 & 2 have selected server (10.1.1.10) as reference and their clocks are synchronized to server's one.
> 
> Next, I stop ntpd on client 1 and I try to synchronize to 10.1.1.21 using ntpdate :
> # killall ntpd
> # ntpdate -b 10.1.1.21
> 22 Jun 21:22:00 ntpdate[3791]: no server suitable for synchronization found
> 
> The result is the same on client2. I tried with several machines (I replace the server by two others machines, same for client) and it is always the same... My problem is that I use lot of scripts forcing time sync using ntpdate and of course, they are not working any more... I cannot understand why ntpdate always refuses to synchronize to an "orphan mode server". This mode causes important regression compared to "old" undisciplined local clock driver...
> Please, could you help me making orphan mode and ntpdate working together ? because undisciplined local clock driver is OK with ntpdate but too long to select local clock as reference on server side.
> Regards
> Gwen
> 
> ___________________________________________________________
> Mode, hifi, maison,… J'achète malin. Je compare les prix avec Voila.fr http://shopping.voila.fr/ _______________________________________________
> questions mailing list
> questions at lists.ntp.org
> http://lists.ntp.org/listinfo/questions
> _______________________________________________
> questions mailing list
> questions at lists.ntp.org
> http://lists.ntp.org/listinfo/questions

___________________________________________________________
Mode, hifi, maison,… J'achète malin. Je compare les prix avec Voila.fr http://shopping.voila.fr/


More information about the questions mailing list