[ntp:questions] Stability problem on PowerEdge (SuSE 9.3)

Steve Kostecke kostecke at ntp.isc.org
Tue Feb 27 18:03:20 UTC 2007

On 2007-02-27, Till Wimmer <news-dfn at substring.ch> wrote:

> Steve Kostecke wrote:
>> You should comment out the LocalCLK until you fix your stability
>> problem. And then, you should only re-enable the LocalCLK if you
>> understand why you need it.
> Well i confess, i'm new to ntp problematics... i thought we need this
> because all other servers in the LAN are sync'ed to this one. We need,
> at least, the same time on every server.

Using the LocalCLK allows your NTP to claim to be synced when your real
time sources are unavailable. This can be useful, but is not required,
when you are serving to to others.

The problem right now is that ntpd is seeing the LocalCLK as better.
This is interfering with solving your problem.

>> Some people will tell you that this is a poor choice of servers (e.g.
>> due to excessive delay). That may be true but it's not germane to
>> your problem.
> I changed them to ch.pools... see follow ups

I know you changed them. And, as we saw, doing so had no effect on your

>> Disabling auth is not usually a good idea because it can allow
>> someone with ntpdc to tinker with your ntpd settings remotely. BUT
>> ... this has nothing to do with your problem.
> i disabled everything that could be restrective in some way.

Authentication has nothing to do with time service unless you have
explictly configured your ntpd to require authentication for certain
associations. But, you haven't done so.

>remote          refid    st t when poll reach  delay  offset jitter
>entry.verboten. 130...    2 u  296 1024  377 2110.41 906.197 30.261
>ns1.nexellent.n 193...    2 u   36 1024  377 2021.64 867.787  6.034
>bryan.solnet.ch 192...    2 u 1005 1024  377 2015.45 878.894  2.276
>idaixds2.unizh. 130...    3 u 1027 1024  376 2012.79 877.746  2.344
>*LOCAL(0)       LOCAL(0) 10 l    7   64  377   0.000   0.000  0.001

The jitter isn't bad.

> /var/log/ntp:

It looks like ntpd did not have to step your clock. That's a good sign.

> so the question remains...

I'd try running this ntpd without the LocalCLK to see ntpd is able to
sync with your remote time servers.

Steve Kostecke <kostecke at ntp.isc.org>
NTP Public Services Project - http://ntp.isc.org/

More information about the questions mailing list