Mailinglist Archive: opensuse (3156 mails)

< Previous Next >
Re: [opensuse] ntp can not manage to put the clock in sync.
  • From: Aaron Kulkis <akulkis00@xxxxxxxxxx>
  • Date: Fri, 07 Dec 2007 03:31:23 -0500
  • Message-id: <475904DB.2020202@xxxxxxxxxx>
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



The Thursday 2007-12-06 at 12:20 -0500, Aaron Kulkis wrote:

Your logs says that when NTP looses the network connection,

Yes.

it is syncing to the CMOS clock.

No.

You are confusing the system clock with the CMOS clock - which is running fine, by the way. I checked.


Your original posting has part of a log which
clearly indicates a sync to a strata 10 source, and
all of your problems started right after that.



+ 27 Nov 15:31:56 ntpd[12905]: synchronized to 91.121...., stratum 2
+ 27 Nov 15:38:31 ntpd[12905]: synchronized to 192.33...., stratum 2
+ 27 Nov 15:39:25 ntpd[12905]: synchronized to 195.55...., stratum 2
+ 27 Nov 15:39:40 ntpd[12905]: synchronized to LOCAL(0), stratum 10
+ 27 Nov 16:22:22 ntpd[12905]: synchronized to 84.88...., stratum 2
+ 27 Nov 16:22:22 ntpd[12905]: time correction of 1678 seconds
exceeds sanity limit (1000); set clock manually to the correct
UTC time.



The CMOS clock is defined as a strata 10 time source
in the ntp.conf file in the RPM package.


More symptoms: the problem started the very same day I installed 10.3. it's in the logs.

interesting.

Was your your ntp.conf file change at that time -- either
by the upgrade or by you?



--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups