Re: [ntp:questions] Ntp not syncing after powerfail of server

[Harlan Stenn]

Richard wrote:

> NTPD needs something like thirty minutes before it is able to serve a 
> reasonable facsimile of the correct time.  It needs up to ten hours 
> after startup to deliver the highest quality time that it is capable of.

Well, that's true for cold-start, with no drift file.  But it's not the
normal case, at least for a properly set-up and configured system.

I am used to seeing this reduced to 11 *seconds* if you have a good
drift file and run iburst.

> The corollary to this is that you can't expect NTPD to run 9 AM to 5 PM 
> and deliver the best possible quality of time.  If you want the best 
> possible accuracy, you run NTPD 24x7.

Yup.

H
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Chris Albertson]

On Thu, May 19, 2011 at 5:38 PM, Richard B. Gilbert
 wrote:
> On 5/19/2011 12:08 PM, M. Giertzsch wrote:
>>
>>
>> Am 19.05.2011 17:55, schrieb Chris Albertson:
>>>
>>> On Wed, May 18, 2011 at 2:57 AM, M. Giertzsch
>>> wrote:
>>>
 Now if there is a powerfail, there is no guarantee that the server has
 finished the boot
 before the clients have. In this case the time will not be synced.
>>>
>>> If the clients are running the standard ntpd they will continue poling
>>> "forever" and the server can go up and down. The clients can sync to
>>> it when it is up and of course can't if it isn't.
>>>
>>> BTW it helps to have more than one NTP server. How do you know you
>>> server is serving correct time without some kind of redundant check?
>>>
>>>
>>
>> Hi Chris,
>> thank you for your reply.
>>
>> This is of course true, I can't say that that one server serves the
>> correct time.
>> But in a closed environment I can't guarantee that even when using more
>> servers.
>> If real time is needed I'm in need of a GPS module or something like this.
>
> A GPS Timing Receiver gives you time traceable to NIST.

If it is working and configured properly.  It is easy to have the time
"off" by a full second and there are examples of GPS driven NTP
servers that are far more than a second off.  You will never see that
kind of bug unless you have some kind of cross check set up.

Just for fun I set up and old Garmin nav GPS.  It was all over the
place, very poor time keeping realative to pool servers.

And I think "traceable" to NIST is the wrong term.  In this business
that word "traceable" has special meaning and some specific
administrative rules must be followed.   But in the general sense of
the word, outside of the way NIST uses it then yes the GPS times is
derived from a national standard.  --


=
Chris Albertson
Redondo Beach, California
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Richard B. Gilbert]

On 5/19/2011 12:08 PM, M. Giertzsch wrote:



Am 19.05.2011 17:55, schrieb Chris Albertson:

On Wed, May 18, 2011 at 2:57 AM, M. Giertzsch
wrote:


Now if there is a powerfail, there is no guarantee that the server has
finished the boot
before the clients have. In this case the time will not be synced.

If the clients are running the standard ntpd they will continue poling
"forever" and the server can go up and down. The clients can sync to
it when it is up and of course can't if it isn't.

BTW it helps to have more than one NTP server. How do you know you
server is serving correct time without some kind of redundant check?




Hi Chris,
thank you for your reply.

This is of course true, I can't say that that one server serves the
correct time.
But in a closed environment I can't guarantee that even when using more
servers.
If real time is needed I'm in need of a GPS module or something like this.


A GPS Timing Receiver gives you time traceable to NIST.


But hmm, still it seems to me that the client does not sync when
finished booting


NTPD needs something like thirty minutes before it is able to serve a 
reasonable facsimile of the correct time.  It needs up to ten hours 
after startup to deliver the highest quality time that it is capable of.


The corollary to this is that you can't expect NTPD to run 9 AM to 5 PM 
and deliver the best possible quality of time.  If you want the best 
possible accuracy, you run NTPD 24x7.


There is another program whose name I forget, that does a much faster 
startup at the the price of slightly poorer quality of time.




before the server does. What about that iburst mentioned in my recent
post and may it be that
I have to be more patient waiting for the next poll (but I waited half
an hour).


Something is very wrong there.  NTPD adjusts its poll interval from 32 
or 64 seconds to 1024 seconds as needed.  Over simplifying, the short 
poll intervals give you a relatively speedy convergence to to something 
close to the correct time.  Longer poll intervals give better accuracy.


The "IBURST" keyword causes NTPD to initially send eight requests at 
intervals of two seconds.  The information thus obtained gets NTPD 
initialized more rapidly than it would be otherwise.




___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[E-Mail Sent to this address will be added to the BlackLists]

M. Giertzsch wrote:
> The servers configuration is:
>restrict default notrap nomodify nopeer noquery
-^^^
>restrict 127.0.0.1
>driftfile /var/status/ntp.drift
>pidfile /var/run/ntpd.pid
>server 127.127.1.1
>fudge 127.127.1.1 stratum 7

Isn't the lack of any other restrict statements
 going to disallow query from the clients?


> The clients configuration is:
>restrict default notrap nomodify nopeer noquery
>restrict 127.0.0.1
>driftfile /var/status/ntp.drift
>pidfile /var/run/ntpd.pid
>server 10.9.94.165 iburst
>server 127.127.1.1
>fudge 127.127.1.1 stratum 13
>
>
> To run into the problem that the client is not syncing to the server I
> --> stopped the NTP service on both client and server
> --> changed the time on the client back to january of 1975

That is a big jump,
 (you only get that chance once before panic with ntpd -g),
 some embedded systems use a hard coded min date,
 or check the date / times stamps on some files,
 and if the clock does not appear to be set,
 set to that discovered date / time,
 before running NTPd -g.

> --> started the NTP service on the client
> --> started the NTP service on the server a little later


-- 
E-Mail Sent to this address 
  will be added to the BlackLists.

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Chuck Swiger]

On May 19, 2011, at 2:53 PM, Hal Murray wrote:
>> By default, ntpd will not try to correct a clock which is insanely far off.
>> The -g flag can be used to change this; otherwise run ntpdate -b at boot
>> to get the clock close and then run ntpd afterwards to keep the clock in 
>> sync.
> 
> Running ntpdate at boot time won't work if the server isn't ready yet.

True, but I think you can specify multiple servers to ntpdate if that is likely 
to be a problem.

> I think the -g switch to ntpd will do the right thing, that is allow
> one big jump the first time it sets the clock.

Agreed...

Regards,
-- 
-Chuck

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Hal Murray]

In article <35fcd513-e8ea-4feb-a33b-6d47d6556...@mac.com>,
 Chuck Swiger  writes:
>On May 19, 2011, at 10:01 AM, M. Giertzsch wrote:
>> To run into the problem that the client is not syncing to the server I
>> --> stopped the NTP service on both client and server
>> --> changed the time on the client back to january of 1975
>> --> started the NTP service on the client
>> --> started the NTP service on the server a little later
>
>By default, ntpd will not try to correct a clock which is insanely far off.
> The -g flag can be used to change this; otherwise run ntpdate -b at boot
> to get the clock close and then run ntpd afterwards to keep the clock in sync.

Running ntpdate at boot time won't work if the server isn't ready yet.

I think the -g switch to ntpd will do the right thing, that is allow
one big jump the first time it sets the clock.

-- 
These are my opinions, not necessarily my employer's.  I hate spam.

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] orphan mode

[David Woolley]

Nickolay Orekhov wrote:

Instead of using orphan mode you could try to setup "local reference clock",
see here http://www.eecis.udel.edu/~mills/ntp/html/drivers/driver1.html



Orphan mode is an attempt to do time islands properly.  The local clock 
driver should have been used in hardly any of the cases in which it was 
used before orphan mode, and even less now.  Unfortunately, people 
packaging ntpd included it in default configurations.  In particular, it 
should never be used for leaf nodes.


Many of the problems reported here are the result of inappropriate use 
of the local clock driver.


___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Rob]

M. Giertzsch  wrote:
> To run into the problem that the client is not syncing to the server I
> --> stopped the NTP service on both client and server
> --> changed the time on the client back to january of 1975
> --> started the NTP service on the client
> --> started the NTP service on the server a little later

That is something that NTP is not going to be able to survive!

It will not make the correction from 1975 to today except when it is
told to do so on startup.  When your server is not available on startup,
you are out of luck.

Of course with "normal" conditions, e.g. a powerfail bringing down
everything and clients booting a bit faster than the server, it will
work just fine because the client is still within the acceptable time
difference.

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Steve Kostecke]

On 2011-05-19, M. Giertzsch  wrote:

> This is of course true, I can't say that that one server serves the
> correct time. But in a closed environment I can't guarantee that even
> when using more servers. If real time is needed I'm in need of a GPS
> module or something like this.

The GPS gives you something more important than the "real time". It
gives you a stable time reference.

Without a stable time reference ntpd can't make your clocks tick at 1
second per second. At best you'll have all you clocks playing follow the
leader (chasing your drifting LAN time server).

> But hmm, still it seems to me that the client does not sync when
> finished booting before the server does. What about that iburst
> mentioned in my recent post and may it be that I have to be more
> patient waiting for the next poll (but I waited half an hour).

Try removing the Undisciplined Local Clock lines from the client (the
lines containing 127.127.1.*). I suspect that your clients are choosing
"LOCAL" as their sys_peer and then ignoring your LAN time server).

The Undiscplined Local Clock is not a back-up for "leaf-node" (i.e.
client only) systems. It is only appropriate for an ntpd which must be
able to server time to others when the real time sources are
unreachable, or don't exist.)

-- 
Steve Kostecke 
NTP Public Services Project - http://support.ntp.org/

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] orphan mode

[Steve Kostecke]

On 2011-05-17, Frank Alsop  wrote:

>    We have a relatively small network and are trying to use ntp
> peering and orphan mode and I have a couple of questions.  I have read
> the info at http://www.eecis.udel.edu/~mills/ntp/html/orphan.html

That is the documentation for the current ntp-dev release.

Please use the documentation shipped with your version of NTP or the
documentation archived at http://doc.ntp.org/4.2.4

> but I am having trouble figuring out the correct "tos orphan" statement we 
> should use.
>
> We have a time source at stratum 1.
> We have 4 "peers" at stratum 2
> We have multiple nodes at stratum 3
> We have multiple nodes at stratum 4
>
> So, in our ntp.conf file for the 4 stratum 2 "peered" nodes, we have
> "tos orphan 4".  At the website referred to above, we could infer that
> we need to use "tos orphan 5".  What stratum should we use in our
> orphan statement?

5 is the default orphan stratum. Use at least that (i.e. >= 5).

> Also, we are using 4.2.4p7.  At the following website,
> you could infer that we need a newer rev of ntp.
> http://support.ntp.org/bin/view/Support/OrphanMode
>
> This page seems to indicate we need at least 4.2.5p101, but at least
> to me, isn't perfectly clear.

The current stable release is NTP-4.2.6p3 and you are using NTP-4.2.4p7.
On the surface it does not look like there's much difference between
these two versions. But there is; substantial changes were made in the
4.2.5* development series.

Here's how you should be reading these versions:

NTP-4.2.4p7 == NTP-4 v2.4.7

NTP-4.2.6p3 == NTP-4 v2.6.3

If you want to use Orphan Mode you should upgrade to the current stable
release.

-- 
Steve Kostecke 
NTP Public Services Project - http://support.ntp.org/

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Uwe Klein]

M. Giertzsch wrote:
But hmm, still it seems to me that the client does not sync when 
finished booting
before the server does. What about that iburst mentioned in my recent 
post and may it be that
I have to be more patient waiting for the next poll (but I waited half 
an hour).



What is your client platform and what ntp-client do you use ?

uwe

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Chuck Swiger]

On May 19, 2011, at 10:01 AM, M. Giertzsch wrote:
> To run into the problem that the client is not syncing to the server I
> --> stopped the NTP service on both client and server
> --> changed the time on the client back to january of 1975
> --> started the NTP service on the client
> --> started the NTP service on the server a little later

By default, ntpd will not try to correct a clock which is insanely far off.  
The -g flag can be used to change this; otherwise run ntpdate -b at boot to get 
the clock close and then run ntpd afterwards to keep the clock in sync.

Regards,
-- 
-Chuck

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] orphan mode

[Nickolay Orekhov]

Instead of using orphan mode you could try to setup "local reference clock",
see here http://www.eecis.udel.edu/~mills/ntp/html/drivers/driver1.html

Than, It's
not clear why you need orphan mode at all?
In any case you could set orphan stratum ( or stratum of local ref clock )
to any value lower than your external clock sources but higher than 16.
For ex. 8. or 12. It is important that this value should be lower so when no
external clock sources available your clients will choose this local sources
with very bad stratum.

2011/5/18 Frank Alsop 

> Hi,
>We have a relatively small network and are trying to use ntp peering and
> orphan mode and I have a couple of questions.  I have read the info at
> http://www.eecis.udel.edu/~mills/ntp/html/orphan.html
> but I am having trouble figuring out the correct "tos orphan" statement we
> should use.
>
> We have a time source at stratum 1.
> We have 4 "peers" at stratum 2
> We have multiple nodes at stratum 3
> We have multiple nodes at stratum 4
>
> So, in our ntp.conf file for the 4 stratum 2 "peered" nodes, we have "tos
> orphan
> 4".  At the website referred to above, we could infer that we need to use
> "tos
> orphan 5".  What stratum should we use in our orphan statement?
>
> Also, we are using 4.2.4p7.  At the following website, you could infer that
> we
> need a newer rev of ntp.
> http://support.ntp.org/bin/view/Support/OrphanMode
>
> This page seems to indicate we need at least 4.2.5p101, but at least to me,
> isn't perfectly clear.
>
> thanks for your help,
>
> Frank
> ___
> questions mailing list
> questions@lists.ntp.org
> http://lists.ntp.org/listinfo/questions
>
>
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[M. Giertzsch]

Am 18.05.2011 11:57, schrieb M. Giertzsch:

Hello together,

I want to synchronise a local network and there is no uplink to the 
outside world.
So I have one dedicated ntp server and all other devices are client of 
this server.
Now if there is a powerfail, there is no guarantee that the server has 
finished the boot

before the clients have. In this case the time will not be synced.

Is anybody aware of options taking account to this? Does anyone know 
threads
or howtos for further reading? Am I doing a mistake or do I have my 
clients missconfigured?




Hello again (and sorry for the flood of posts),

in order to unconfuse myself I have done a new and easier setup of my 
problem.

Now I have only got one server and one client.

The servers configuration is:
  restrict default notrap nomodify nopeer noquery
  restrict 127.0.0.1
  driftfile /var/status/ntp.drift
  pidfile /var/run/ntpd.pid
  server 127.127.1.1
  fudge 127.127.1.1 stratum 7

The clients configuration is:
  restrict default notrap nomodify nopeer noquery
  restrict 127.0.0.1
  driftfile /var/status/ntp.drift
  pidfile /var/run/ntpd.pid
  server 10.9.94.165 iburst
  server 127.127.1.1
  fudge 127.127.1.1 stratum 13


To run into the problem that the client is not syncing to the server I
--> stopped the NTP service on both client and server
--> changed the time on the client back to january of 1975
--> started the NTP service on the client
--> started the NTP service on the server a little later


Hope that clarifies the situation...

--
Best regards,
   M. Giertzsch




___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Nickolay Orekhov]

You shouldn't use 127.127.1.1. as local backup clock.
Just set "tos orphan 13", remove 127.127.1.1 and orphan server would give
it's time to clients.
Then, you can remove "restrict" clauses and see what's happening - I think
you don't need them.

Without restrict you could use ntpq tools to query server and client state.
The most important and intresting commands on the client are "rv", "pe",
"ass" and rv [assoc id] of your server.
If you could show this commands output here people can answer your question
with ease.

2011/5/19 M. Giertzsch 

> Am 19.05.2011 16:01, schrieb Heiko Gerstung:
>
>
>> restrict default notrap nomodify nopeer noquery
> restrict 127.0.0.1
> driftfile /var/status/ntp.drift
> pidfile /var/run/ntpd.pid
> server 0.de.pool.ntp.org iburst
> server 1.de.pool.ntp.org iburst
> server 2.de.pool.ntp.org iburst
> server 127.127.1.1
> fudge 127.127.1.1 stratum 13
>
>
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[M. Giertzsch]

Am 19.05.2011 17:52, schrieb M. Giertzsch:

Am 19.05.2011 16:01, schrieb Heiko Gerstung:

Hi,

Am 18.05.2011 11:57, schrieb M. Giertzsch:

Hello together,

I want to synchronise a local network and there is no uplink to the
outside world.
So I have one dedicated ntp server and all other devices are client
of this server.
Now if there is a powerfail, there is no guarantee that the server
has finished the boot
before the clients have. In this case the time will not be synced.

Is anybody aware of options taking account to this? Does anyone know
threads
or howtos for further reading? Am I doing a mistake or do I have my
clients missconfigured?


Maybe I am missing something, but if you use ntpd on the client
machines, they will poll the server in intervals. So even if
they do not get a response the first time they ask, they should
receive the time on the second try (and all consecutive calls).

We have no chance to tell you whether you have misconfigured your
clients, because we do not know
- what OS your clients are running on
- what kind of NTP software you are using (ntpd version X or
something else?) on the clients and on the server
- how your current configuration looks like (ntp.conf?)

I could imagine that your clients probably use ntpdate or a similar
software to query the time once during startup, but that
is just me guessing your setup. If that would be the case, all you
could probably do is inserting a sleep before the ntpdate
call or some other ugly workaround like this.

Regards,
  Heiko

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions


Hello Heiko,

thanks for your help. You are totally right, I have forgotton to give
you all these informations required.
The NTP software in use is ntpd 4.2.0a on both client and server.
Well, I can't tell you exactly the OS in use,
but it's a linux like OS running on an embedded arm device.

The NTP configuration looks like follows:

restrict default notrap nomodify nopeer noquery
restrict 127.0.0.1
driftfile /var/status/ntp.drift
pidfile /var/run/ntpd.pid
server 0.de.pool.ntp.org iburst
server 1.de.pool.ntp.org iburst
server 2.de.pool.ntp.org iburst
server 127.127.1.1
fudge 127.127.1.1 stratum 13


ups, this is wrong of course
this config was taken from a wrong client.

restrict default notrap nomodify nopeer noquery
restrict 127.0.0.1
driftfile /var/status/ntp.drift
pidfile /var/run/ntpd.pid
server 10.8.0.171 iburst
server 127.127.1.1
fudge 127.127.1.1 stratum 13

And regarding the linux: It's kernel 2.6.37.6+.



May it be that iburst is the problem? Client gives up because of too
many non-responses, or will iburst
ignore these and send another bunch a little later?

If you need any more information please ask me.
Thank you in anticipation.



--
Best regards,
   M. Giertzsch
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[M. Giertzsch]

Am 19.05.2011 17:55, schrieb Chris Albertson:

On Wed, May 18, 2011 at 2:57 AM, M. Giertzsch  wrote:

   

Now if there is a powerfail, there is no guarantee that the server has
finished the boot
before the clients have. In this case the time will not be synced.
 

If the clients are running the standard ntpd they will continue poling
"forever" and the server can go up and down.  The clients can sync to
it when it is up and of course can't if it isn't.

BTW it helps to have more than one NTP server.  How do you know you
server is serving correct time without some kind of redundant check?


   


Hi Chris,
thank you for your reply.

This is of course true, I can't say that that one server serves the 
correct time.
But in a closed environment I can't guarantee that even when using more 
servers.

If real time is needed I'm in need of a GPS module or something like this.

But hmm, still it seems to me that the client does not sync when 
finished booting
before the server does. What about that iburst mentioned in my recent 
post and may it be that
I have to be more patient waiting for the next poll (but I waited half 
an hour).


--

Best regards,
   M. Giertzsch

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Chris Albertson]

On Wed, May 18, 2011 at 2:57 AM, M. Giertzsch  wrote:

> Now if there is a powerfail, there is no guarantee that the server has
> finished the boot
> before the clients have. In this case the time will not be synced.

If the clients are running the standard ntpd they will continue poling
"forever" and the server can go up and down.  The clients can sync to
it when it is up and of course can't if it isn't.

BTW it helps to have more than one NTP server.  How do you know you
server is serving correct time without some kind of redundant check?


-- 
=
Chris Albertson
Redondo Beach, California
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[M. Giertzsch]

Am 19.05.2011 16:01, schrieb Heiko Gerstung:

Hi,

Am 18.05.2011 11:57, schrieb M. Giertzsch:
   

Hello together,

I want to synchronise a local network and there is no uplink to the outside 
world.
So I have one dedicated ntp server and all other devices are client of this 
server.
Now if there is a powerfail, there is no guarantee that the server has finished 
the boot
before the clients have. In this case the time will not be synced.

Is anybody aware of options taking account to this? Does anyone know threads
or howtos for further reading? Am I doing a mistake or do I have my clients 
missconfigured?

 

Maybe I am missing something, but if you use ntpd on the client machines, they 
will poll the server in intervals. So even if
they do not get a response the first time they ask, they should receive the 
time on the second try (and all consecutive calls).

We have no chance to tell you whether you have misconfigured your clients, 
because we do not know
- what OS your clients are running on
- what kind of NTP software you are using (ntpd version X or something else?) 
on the clients and on the server
- how your current configuration looks like (ntp.conf?)

I could imagine that your clients probably use ntpdate or a similar software to 
query the time once during startup, but that
is just me guessing your setup. If that would be the case, all you could 
probably do is inserting a sleep before the ntpdate
call or some other ugly workaround like this.

Regards,
  Heiko

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
   


Hello Heiko,

thanks for your help. You are totally right, I have forgotton to give 
you all these informations required.
The NTP software in use is ntpd 4.2.0a on both client and server. Well, 
I can't tell you exactly the OS in use,

but it's a linux like OS running on an embedded arm device.

The NTP configuration looks like follows:

restrict default notrap nomodify nopeer noquery
restrict 127.0.0.1
driftfile /var/status/ntp.drift
pidfile /var/run/ntpd.pid
server 0.de.pool.ntp.org iburst
server 1.de.pool.ntp.org iburst
server 2.de.pool.ntp.org iburst
server 127.127.1.1
fudge 127.127.1.1 stratum 13


May it be that iburst is the problem? Client gives up because of too 
many non-responses, or will iburst

ignore these and send another bunch a little later?

If you need any more information please ask me.
Thank you in anticipation.

--
Best regards,
   M. Giertzsch

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Re: [ntp:questions] Ntp not syncing after powerfail of server

[Heiko Gerstung]

Hi,

Am 18.05.2011 11:57, schrieb M. Giertzsch:
> Hello together,
> 
> I want to synchronise a local network and there is no uplink to the outside 
> world.
> So I have one dedicated ntp server and all other devices are client of this 
> server.
> Now if there is a powerfail, there is no guarantee that the server has 
> finished the boot
> before the clients have. In this case the time will not be synced.
> 
> Is anybody aware of options taking account to this? Does anyone know threads
> or howtos for further reading? Am I doing a mistake or do I have my clients 
> missconfigured?
> 

Maybe I am missing something, but if you use ntpd on the client machines, they 
will poll the server in intervals. So even if
they do not get a response the first time they ask, they should receive the 
time on the second try (and all consecutive calls).

We have no chance to tell you whether you have misconfigured your clients, 
because we do not know
- what OS your clients are running on
- what kind of NTP software you are using (ntpd version X or something else?) 
on the clients and on the server
- how your current configuration looks like (ntp.conf?)

I could imagine that your clients probably use ntpdate or a similar software to 
query the time once during startup, but that
is just me guessing your setup. If that would be the case, all you could 
probably do is inserting a sleep before the ntpdate
call or some other ugly workaround like this.

Regards,
 Heiko

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] Ntp not syncing after powerfail of server

[M. Giertzsch]

Hello together,

I want to synchronise a local network and there is no uplink to the 
outside world.
So I have one dedicated ntp server and all other devices are client of 
this server.
Now if there is a powerfail, there is no guarantee that the server has 
finished the boot

before the clients have. In this case the time will not be synced.

Is anybody aware of options taking account to this? Does anyone know 
threads
or howtos for further reading? Am I doing a mistake or do I have my 
clients missconfigured?


--
Best regards,
   M. Giertzsch

___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

[ntp:questions] orphan mode

[Frank Alsop]

Hi,
   We have a relatively small network and are trying to use ntp peering and 
orphan mode and I have a couple of questions.  I have read the info at
http://www.eecis.udel.edu/~mills/ntp/html/orphan.html
but I am having trouble figuring out the correct "tos orphan" statement we 
should use.

We have a time source at stratum 1.
We have 4 "peers" at stratum 2
We have multiple nodes at stratum 3
We have multiple nodes at stratum 4

So, in our ntp.conf file for the 4 stratum 2 "peered" nodes, we have "tos 
orphan 
4".  At the website referred to above, we could infer that we need to use "tos 
orphan 5".  What stratum should we use in our orphan statement?

Also, we are using 4.2.4p7.  At the following website, you could infer that we 
need a newer rev of ntp.
http://support.ntp.org/bin/view/Support/OrphanMode

This page seems to indicate we need at least 4.2.5p101, but at least to me, 
isn't perfectly clear.

thanks for your help,

Frank 
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions