In article <[EMAIL PROTECTED]>,
Peter Stickney <[EMAIL PROTECTED]> wrote:

> server us.pool.ntp.org
> server 127.127.1.1

This can be dangerous as the local clock may be assumed to be the
true chimer and exclude the real true chimer.

> restrict 192.168.0.1 mask 255.255.240.0 nomodify nopeer notrap
> restrict 127.0.0.1 nomodify

This is pretty pointless as you have unrestricted access from the 
internet.

> 12 Jul 20:15:47 ntpd[25341]: time reset +3.526547 s
> 12 Jul 20:42:47 ntpd[25341]: time reset +1.678287 s
> 12 Jul 21:36:28 ntpd[25341]: time reset +2.766987 s

You are losing clock interrupts.  Fix this (e.g. reduce HZ, use
better device drivers, reconfigure device drivers).

> fudge 127.127.1.0 stratum 10
> server 127.127.1.0

These may be order sensitive. In any case there is no value in having a local
clock configured on a leaf node and it may also cause problems by
excluding a true chimer.

> 15 Jul 16:39:25 ntpd[15930]: frequency error -512 PPM exceeds tolerance 500 
> PPM

This is end stop, probably because it tried to track the lost interrupts
on lovejoy.

> 15 Jul 16:43:42 ntpd[15930]: synchronized to LOCAL(0), stratum=5

It's abandonded lovejoy.  Because you have the fudge command in the
wrong place, it is ineffective, so the local clock is at its
default stratum.

> So it looks like it's synching to lovejoy [ 192.168.1.14 ]  but at a
> very low strat.  And those PPM errors go away afer a nice ntpdate on
> lovejoy.

That's because lovejoy is currently synchronised to its local clock.
If you don't want this to happen, don't configure a local clock on
lovejoy.

> The windows boxes, forget it, they dont want to synch at all.

Most of the time, lovejoy isn't synchronised.

You need to:
- fix your lost interrupt problem.
- remove the local server from the leaf nodes.
- seriously consider removing it from the LAN server (it is often
  not needed) or increase the number of servers with true time to be
  enough to outvote it.

(Note that having just one server will work, but you shouldn't configure 
a local clock at the same time.  It will give no protection against a
mis-operating server.)

_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions

Reply via email to