-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi,

I'm investigating a problem I'm having with the clock getting very slow, and I have traced the problem to something new in opensuse 10.3.

I wonder if any body has the same problem - the check is simple, run this grep command:


grep "time reset " /var/log/ntp | less

I find:

  (opensuse 10.2)
23 Feb 02:05:45 ntpd[4617]: time reset +0.624127 s
23 Feb 14:28:52 ntpd[4617]: time reset +0.487172 s
23 Feb 14:49:00 ntpd[4617]: time reset +0.138037 s
23 Feb 22:26:08 ntpd[4617]: time reset +0.243491 s
24 Feb 11:54:28 ntpd[4674]: time reset +0.495337 s
25 Feb 11:56:40 ntpd[4674]: time reset +0.380593 s
27 Feb 11:39:30 ntpd[4674]: time reset -0.169734 s
 1 Mar 11:24:29 ntpd[4676]: time reset +0.574879 s

...

  1 Nov 11:28:02 ntpd[4669]: time reset +0.493571 s
  1 Nov 19:54:33 ntpd[6168]: time reset +0.324889 s
  2 Nov 11:56:25 ntpd[6168]: time reset +0.493251 s
  2 Nov 14:09:49 ntpd[6168]: time reset +0.761453 s
  2 Nov 18:57:50 ntpd[6168]: time reset +0.267648 s
  2 Nov 19:19:37 ntpd[6168]: time reset +0.633949 s
  3 Nov 15:04:26 ntpd[4993]: time reset +13.963114 s   <=== upgrade
  3 Nov 16:14:24 ntpd[4993]: time reset +126.365828 s
  3 Nov 19:12:32 ntpd[5051]: time reset +42.074367 s
  4 Nov 12:46:09 ntpd[5076]: time reset +22.996088 s
  4 Nov 13:32:56 ntpd[5076]: time reset +393.672856 s
  5 Nov 13:35:23 ntpd[5163]: time reset +351.141250 s
  5 Nov 14:00:25 ntpd[5163]: time reset +318.950445 s
  5 Nov 14:50:51 ntpd[5163]: time reset +0.164107 s
  5 Nov 19:55:07 ntpd[5163]: time reset +27.860709 s
  5 Nov 23:15:44 ntpd[5163]: time reset +436.175607 s



You see that the time resets are small when I had suse 10.2, but with 10.3 they jumped in size up to almost 400 seconds. If the error is larger than 1000 seconds, ntp quits:

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 delay was half an hour! I restarted the daemon when I noticed.

Nov 27 17:13:53 nimrodel ntpdate[18860]: step time server 212.13.... offset 
1677.937114 sec



Other events - here I have removed these two lines from the config, as a test:

 server 127.127.1.0              # local clock (LCL)
 fudge  127.127.1.0 stratum 10   # LCL is unsynchronized


  3 Dec 19:11:29 ntpd[29084]: synchronized to 88.191.43.2, stratum 2
  3 Dec 19:12:44 ntpd[29084]: synchronized to 213.96.197.96, stratum 2
  3 Dec 19:13:34 ntpd[29084]: no servers reachable
  3 Dec 19:20:14 ntpd[29084]: synchronized to 88.191.43.2, stratum 2
  3 Dec 19:21:32 ntpd[29084]: synchronized to 213.96.197.96, stratum 2
  3 Dec 19:22:36 ntpd[29084]: synchronized to 88.191.43.2, stratum 2
  3 Dec 19:31:42 ntpd[29084]: time reset +309.343782 s

300 seconds of error after being disconeected from servers for just 20 minutes!

Before an hour passes, it happens again:

  3 Dec 19:31:42 ntpd[29084]: system event 'event_clock_reset' (0x05) status 
'sync_alarm, sync_unspec, 15 events, event_peer/strat_chg' (0xc0f4)
  3 Dec 19:31:42 ntpd[29084]: system event 'event_peer/strat_chg' (0x04) status 
'sync_alarm, sync_unspec, 15 events, event_clock_reset' (0xc0f5)
  3 Dec 19:31:44 ntpd[29084]: peer 213.96.200.126 event 'event_reach' (0x84) 
status 'unreach, conf, 2 events, event_reach' (0x8024)
  3 Dec 19:31:45 ntpd[29084]: peer 81.19.16.225 event 'event_reach' (0x84) 
status 'unreach, conf, 2 events, event_reach' (0x8024)
  3 Dec 19:32:23 ntpd[29084]: peer 88.191.43.2 event 'event_reach' (0x84) 
status 'unreach, conf, 2 events, event_reach' (0x8024)
  3 Dec 19:32:24 ntpd[29084]: peer 195.92.137.112 event 'event_reach' (0x84) 
status 'unreach, conf, 2 events, event_reach' (0x8024)
  3 Dec 19:32:30 ntpd[29084]: peer 193.138.215.60 event 'event_reach' (0x84) 
status 'unreach, conf, 2 events, event_reach' (0x8024)
  3 Dec 19:32:34 ntpd[29084]: peer 213.96.197.96 event 'event_reach' (0x84) 
status 'unreach, conf, 2 events, event_reach' (0x8024)
  3 Dec 19:36:40 ntpd[29084]: synchronized to 88.191.43.2, stratum 2
  3 Dec 19:36:40 ntpd[29084]: system event 'event_sync_chg' (0x03) status  
'leap_none, sync_ntp, 15 events, event_peer/strat_chg' (0x6f4)
  3 Dec 19:36:40 ntpd[29084]: system event 'event_peer/strat_chg' (0x04) status 
 'leap_none, sync_ntp, 15 events, event_sync_chg' (0x6f3)
  3 Dec 20:01:13 ntpd[29084]: offset 0.002029 sec freq 79.654 ppm error 
0.002737 poll 6
  3 Dec 20:15:34 ntpd[29084]: synchronized to 213.96.197.96, stratum 2
  3 Dec 20:28:15 ntpd[29084]: no servers reachable
  3 Dec 20:30:41 ntpd[29084]: synchronized to 88.191.43.2, stratum 2
  3 Dec 20:34:30 ntpd[29084]: time reset +220.290279 s

220" delay.

Today, again:

  4 Dec 12:00:18 ntpd[5847]: kernel time sync status change 0001
  4 Dec 12:00:18 ntpd[5847]: system event 'event_sync_chg' (0x03) status
  'leap_none, sync_ntp, 3 events, event_peer/strat_chg' (0x634)
  4 Dec 12:00:18 ntpd[5847]: system event 'event_peer/strat_chg' (0x04) status
  'leap_none, sync_ntp, 4 events, event_sync_chg' (0x643)
  4 Dec 12:04:41 ntpd[5847]: synchronized to 193.39.78.2, stratum 2
  4 Dec 12:12:18 ntpd[5847]: synchronized to 212.13.194.71, stratum 2
  4 Dec 12:22:58 ntpd[5847]: time reset +0.168114 s

A small one. Two hours later:

  4 Dec 12:42:57 ntpd[5847]: synchronized to 212.13.194.71, stratum 2
  4 Dec 12:42:59 ntpd[5847]: synchronized to 193.39.78.2, stratum 2
  4 Dec 12:45:59 ntpd[5847]: synchronized to 212.13.194.71, stratum 2
  4 Dec 12:55:59 ntpd[5847]: offset 0.110640 sec freq -21.718 ppm error 
0.005097 poll 6
  4 Dec 13:53:34 ntpd[5847]: no servers reachable
  4 Dec 13:55:59 ntpd[5847]: offset 0.104618 sec freq 0.315 ppm error 0.003384 
poll 6
  4 Dec 13:59:02 ntpd[5847]: synchronized to 212.13.194.71, stratum 2
  4 Dec 14:04:05 ntpd[5847]: time reset +243.829774 s

Ouch!


I believe there must be a kernel problem or ntp problem in 10.3.


Ah! Yes, I opened a bugzilla, too:

https://bugzilla.novell.com/show_bug.cgi?id=344356


- -- Saludos
       Carlos E.R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFHVeXftTMYHG2NR9URAg8wAJ9p6BWm3KWzgmHh55g/3co4Gm7fqwCfbhJ5
C8UoOm8Fq4bMrXV1nIR/RGI=
=hDaT
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to