https://bugzilla.novell.com/show_bug.cgi?id=344356#c1 Michael Skibbe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #1 from Michael Skibbe 2007-11-28 01:09:52 MST --- please attach /var/log/messages, /var/log/ntp output of ntpdc -c pe -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344356#c3 --- Comment #3 from Carlos Robinson 2007-11-28 13:17:25 MST --- Created an attachment (id=185160) --> (https://bugzilla.novell.com/attachment.cgi?id=185160) partial messages file -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344356#c5 --- Comment #5 from Carlos Robinson 2007-11-28 16:48:27 MST --- It is happening right now. The system local time is 00:19, and the real time is 00:23. nimrodel:~ # ntpdc -c pe remote local st poll reach delay offset disp ======================================================================= =192.33.214.57 192.168.1.12 2 1024 377 0.13571 290.59757 0.12036 =LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03049 =punk.kls.es 192.168.1.12 2 1024 377 0.08014 290.59311 0.12131 =96.Red-213-96-1 192.168.1.12 2 1024 377 0.22598 290.54091 0.12125 =srv1.m.faelix.n 192.168.1.12 2 1024 377 0.10805 290.62112 0.12129 =endor.ordrejedi 192.168.1.12 3 1024 377 0.10883 290.58992 0.12135 *time3.ethz.ch 192.168.1.12 2 1024 377 0.10649 290.60127 0.12126 nimrodel:~ # date ; ntpdc -c pe Thu Nov 29 00:21:34 CET 2007 remote local st poll reach delay offset disp ======================================================================= =192.33.214.57 192.168.1.12 2 1024 377 0.13612 295.28592 0.12125 =LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03038 =punk.kls.es 192.168.1.12 2 1024 377 0.08014 290.59311 0.12131 =96.Red-213-96-1 192.168.1.12 2 1024 377 0.22598 290.54091 0.12125 =srv1.m.faelix.n 192.168.1.12 2 1024 377 0.10805 290.62112 0.12129 =endor.ordrejedi 192.168.1.12 3 1024 377 0.10883 290.58992 0.12135 *time3.ethz.ch 192.168.1.12 2 1024 377 0.10649 290.60127 0.12126 nimrodel:~ # date ; ntpdc -c pe Thu Nov 29 00:28:04 CET 2007 remote local st poll reach delay offset disp ======================================================================= =192.33.214.57 192.168.1.12 2 1024 377 0.13612 295.28592 0.12125 =LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03075 =punk.kls.es 192.168.1.12 2 1024 377 0.08014 290.59311 0.12131 =96.Red-213-96-1 192.168.1.12 2 1024 377 0.22598 290.54091 0.12125 =srv1.m.faelix.n 192.168.1.12 2 1024 377 0.10805 290.62112 0.12129 =endor.ordrejedi 192.168.1.12 3 1024 377 0.10883 290.58992 0.12135 *time3.ethz.ch 192.168.1.12 2 1024 377 0.10649 290.60127 0.12126 nimrodel:~ # date ; ntpdc -c pe Thu Nov 29 00:32:08 CET 2007 remote local st poll reach delay offset disp ======================================================================= =192.33.214.57 192.168.1.12 2 1024 377 0.13612 295.28592 0.12125 *LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03075 =punk.kls.es 192.168.1.12 2 1024 377 0.08012 295.27988 0.12161 =96.Red-213-96-1 192.168.1.12 2 1024 377 0.11411 295.29405 0.12167 =srv1.m.faelix.n 192.168.1.12 2 1024 377 0.10986 295.30046 0.12164 =endor.ordrejedi 192.168.1.12 3 1024 377 0.10886 295.27848 0.12166 =time3.ethz.ch 192.168.1.12 2 1024 377 0.11043 295.28876 0.12169 (the error is 5 minutes now) nimrodel:~ # date ; ntpdc -c pe Thu Nov 29 00:37:07 CET 2007 remote local st poll reach delay offset disp ======================================================================= =192.33.214.57 192.168.1.12 2 1024 377 0.13612 295.28592 0.13649 *LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03065 =punk.kls.es 192.168.1.12 2 1024 377 0.08012 295.27988 0.12161 =96.Red-213-96-1 192.168.1.12 2 1024 377 0.11411 295.29405 0.12167 =srv1.m.faelix.n 192.168.1.12 2 1024 377 0.10986 295.30046 0.12164 =endor.ordrejedi 192.168.1.12 3 1024 377 0.10886 295.27848 0.12166 =time3.ethz.ch 192.168.1.12 2 1024 377 0.11043 295.28876 0.12169 nimrodel:~ # date ; ntpdc -c pe Thu Nov 29 00:41:30 CET 2007 remote local st poll reach delay offset disp ======================================================================= *192.33.214.57 192.168.1.12 2 1024 377 0.13612 295.28592 0.13649 =LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03084 =punk.kls.es 192.168.1.12 2 1024 377 0.08012 295.27988 0.12161 =96.Red-213-96-1 192.168.1.12 2 1024 377 0.11411 295.29405 0.12167 =ntp1.faelix.net 192.168.1.12 2 1024 377 0.10986 295.30046 0.12164 =endor.ordrejedi 192.168.1.12 3 1024 377 0.10886 295.27848 0.12166 =time3.ethz.ch 192.168.1.12 2 1024 377 0.11043 295.28876 0.12169 /var/log/ntp since last ntp restart (I enabled a hook to restart it every time I suspend to disk, thinking that might be the problem, but no): 28 Nov 16:30:24 ntpd[6148]: ntpd exiting on signal 15 28 Nov 16:30:24 ntpd[6148]: offset 0.000000 sec freq 78.416 ppm error 0.000001 poll 10 28 Nov 19:50:19 ntpd[19587]: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010) 28 Nov 19:50:19 ntpd[19587]: peer LOCAL(0) event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 28 Nov 19:50:19 ntpd[19587]: Deleting interface #2 lo, ::1#123, interface stats: received=0, sent=0, dropped=0, active_time=1 secs 28 Nov 19:50:19 ntpd[19587]: Deleting interface #3 eth0, fe80::240:f4ff:fe2e:b121#123, interface stats: received=0, sent=0, dropped=0, active_time=1 secs 28 Nov 19:50:25 ntpd[19587]: peer 212.9.75.245 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 28 Nov 19:50:25 ntpd[19587]: peer 193.142.245.196 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 28 Nov 19:50:25 ntpd[19587]: peer 213.161.194.93 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 28 Nov 19:50:25 ntpd[19587]: peer 192.33.98.103 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 28 Nov 19:50:26 ntpd[19587]: peer 192.33.214.57 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 28 Nov 19:53:32 ntpd[19587]: system event 'event_peer/strat_chg' (0x04) status 'sync_alarm, sync_local_proto, 2 events, event_restart' (0xc521) 28 Nov 19:53:32 ntpd[19587]: synchronized to LOCAL(0), stratum 10 28 Nov 19:53:32 ntpd[19587]: kernel time sync status change 0001 28 Nov 19:53:32 ntpd[19587]: system event 'event_sync_chg' (0x03) status 'leap_none, sync_local_proto, 3 events, event_peer/strat_chg' (0x534) 28 Nov 19:53:32 ntpd[19587]: system event 'event_peer/strat_chg' (0x04) status 'leap_none, sync_local_proto, 4 events, event_sync_chg' (0x543) 28 Nov 19:55:43 ntpd[19587]: synchronized to 192.33.214.57, stratum 2 28 Nov 20:03:19 ntpd[19587]: peer 213.96.197.96 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014) 28 Nov 20:06:24 ntpd[19587]: synchronized to 192.33.98.103, stratum 2 28 Nov 20:50:18 ntpd[19587]: offset -0.001408 sec freq 78.770 ppm error 0.001970 poll 7 28 Nov 21:01:16 ntpd[19587]: synchronized to 192.33.214.57, stratum 2 28 Nov 21:50:18 ntpd[19587]: offset -0.001597 sec freq 78.736 ppm error 0.004094 poll 9 28 Nov 22:38:00 ntpd[19587]: synchronized to 192.33.98.103, stratum 2 28 Nov 22:50:18 ntpd[19587]: offset 0.000773 sec freq 78.729 ppm error 0.005932 poll 10 28 Nov 23:50:18 ntpd[19587]: offset 0.002848 sec freq 78.946 ppm error 0.002366 poll 10 28 Nov 23:56:26 ntpd[19587]: synchronized to 192.33.214.57, stratum 2 29 Nov 00:02:53 ntpd[19587]: synchronized to LOCAL(0), stratum 10 29 Nov 00:13:29 ntpd[19587]: synchronized to 192.33.98.103, stratum 2 while I write this report, three more entries: 29 Nov 00:30:35 ntpd[19587]: synchronized to 212.9.75.245, stratum 2 29 Nov 00:31:30 ntpd[19587]: synchronized to LOCAL(0), stratum 10 29 Nov 00:37:39 ntpd[19587]: synchronized to 192.33.214.57, stratum 2 /var/log/kernel: Nov 28 19:49:49 nimrodel kernel: Restarting tasks ... done. Nov 28 19:49:53 nimrodel kernel: swsusp: Basic memory bitmaps freed Nov 28 19:49:56 nimrodel kernel: input: Power Button (FF) as /class/input/input9 Nov 28 19:49:56 nimrodel kernel: ACPI: Power Button (FF) [PWRF] Nov 28 19:49:56 nimrodel kernel: input: Power Button (CM) as /class/input/input10 Nov 28 19:49:56 nimrodel kernel: ACPI: Power Button (CM) [PWRB] Nov 28 19:49:56 nimrodel kernel: input: Sleep Button (CM) as /class/input/input11 Nov 28 19:49:56 nimrodel kernel: ACPI: Sleep Button (CM) [SLPB] Nov 28 23:55:29 nimrodel kernel: set_rtc_mmss: can't update from 0 to 55 Nov 28 23:55:29 nimrodel kernel: klogd 1.4.1, ---------- state change ---------- /var/log/messages: Nov 28 16:30:21 nimrodel gnome-power-manager: (cer) Hibernating computer because clicked tray Nov 28 19:49:49 nimrodel syslog-ng[3823]: STATS: dropped 0 Nov 28 19:49:54 nimrodel gnome-power-manager: (cer) Resuming computer Nov 28 19:49:56 nimrodel gnome-power-manager: (cer) hibernate failed Nov 28 19:50:18 nimrodel ntpdate[19502]: step time server 212.9.75.245 offset 4.583790 sec Nov 28 19:50:18 nimrodel ntpd[19586]: ntpd 4.2.4p3@1.1502-o Sat Sep 22 01:01:25 UTC 2007 (1) Nov 28 19:50:18 nimrodel ntpd[19587]: precision = 1.000 usec Nov 28 19:50:18 nimrodel ntpd[19587]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Nov 28 19:50:18 nimrodel ntpd[19587]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Nov 28 19:50:18 nimrodel ntpd[19587]: Listening on interface #1 wildcard, ::#123 Disabled Nov 28 19:50:18 nimrodel ntpd[19587]: Listening on interface #2 lo, ::1#123 Enabled Nov 28 19:50:18 nimrodel ntpd[19587]: Listening on interface #3 eth0, fe80::240:f4ff:fe2e:b121#123 Enabled Nov 28 19:50:18 nimrodel ntpd[19587]: Listening on interface #4 lo, 127.0.0.1#123 Enabled Nov 28 19:50:18 nimrodel ntpd[19587]: Listening on interface #5 eth0, 192.168.1.12#123 Enabled Nov 28 19:50:18 nimrodel ntpd[19587]: kernel time sync status 0040 Nov 28 19:50:19 nimrodel ntpd[19587]: frequency initialized 78.416 PPM from /var/lib/ntp/drift/ntp.drift Nov 28 20:00:01 nimrodel /usr/sbin/cron[21174]: (cer) CMD (/home/cer/bin/avisar_hablando time > /dev/null) Nov 28 20:19:29 nimrodel smartd[5218]: Device: /dev/hda, SMART Usage Attribute: 190 Temperature_Celsius changed from 73 to 74 Nov 28 20:19:29 nimrodel smartd[5218]: Device: /dev/hda, SMART Usage Attribute: 194 Temperature_Celsius changed from 27 to 26 Nov 28 20:19:29 nimrodel smartd[5218]: Device: /dev/hda, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 71 to 74 Nov 28 20:19:29 nimrodel smartd[5218]: Device: /dev/hdb, SMART Usage Attribute: 194 Temperature_Celsius changed from 26 to 24 Nov 28 20:19:29 nimrodel smartd[5218]: Device: /dev/hdd, SMART Usage Attribute: 194 Temperature_Celsius changed from 33 to 31 Nov 28 20:30:01 nimrodel /usr/sbin/cron[23322]: (cer) CMD (/home/cer/bin/avisar_hablando time > /dev/null) Nov 28 20:30:16 nimrodel smartd[5218]: Device: /dev/hda, SMART Usage Attribute: 190 Temperature_Celsius changed from 74 to 73 Nov 28 20:30:16 nimrodel smartd[5218]: Device: /dev/hda, SMART Usage Attribute: 194 Temperature_Celsius changed from 26 to 27 Nov 28 20:30:17 nimrodel smartd[5218]: Device: /dev/hdb, SMART Usage Attribute: 194 Temperature_Celsius changed from 24 to 25 Nov 28 20:30:17 nimrodel smartd[5218]: Device: /dev/hdd, SMART Usage Attribute: 194 Temperature_Celsius changed from 31 to 32 Nov 28 20:49:50 nimrodel syslog-ng[3823]: STATS: dropped 0 Nov 28 21:00:01 nimrodel /usr/sbin/cron[25777]: (cer) CMD (/home/cer/bin/avisar_hablando time > /dev/null) Nov 28 21:00:16 nimrodel smartd[5218]: Device: /dev/hda, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 74 to 73 Nov 28 21:00:16 nimrodel smartd[5218]: Device: /dev/hdb, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 59 to 60 Nov 28 21:00:16 nimrodel smartd[5218]: Device: /dev/hdb, SMART Usage Attribute: 194 Temperature_Celsius changed from 25 to 26 Nov 28 21:00:16 nimrodel smartd[5218]: Device: /dev/hdd, SMART Usage Attribute: 194 Temperature_Celsius changed from 32 to 33 Nov 28 21:24:21 nimrodel gconfd (root-27608): starting (version 2.20.0), pid 27608 user 'root' Nov 28 21:24:21 nimrodel gconfd (root-27608): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Nov 28 21:24:21 nimrodel gconfd (root-27608): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1 Nov 28 21:24:21 nimrodel gconfd (root-27608): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Nov 28 21:24:21 nimrodel gconfd (root-27608): Resolved address "xml:readonly:/etc/gconf/gconf.xml.schemas" to a read-only configuration source at position 3 Nov 28 21:30:01 nimrodel /usr/sbin/cron[28110]: (cer) CMD (/home/cer/bin/avisar_hablando time > /dev/null) Nov 28 21:30:17 nimrodel smartd[5218]: Device: /dev/hda, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 73 to 72 Nov 28 21:30:17 nimrodel smartd[5218]: Device: /dev/hdb, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 60 to 58 Nov 28 21:30:17 nimrodel smartd[5218]: Device: /dev/hdd, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 59 to 60 Nov 28 21:30:17 nimrodel smartd[5218]: Device: /dev/hdd, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 59 to 60 Nov 28 21:49:50 nimrodel syslog-ng[3823]: STATS: dropped 0 Nov 28 22:00:01 nimrodel /usr/sbin/cron[30265]: (cer) CMD (/home/cer/bin/avisar_hablando time > /dev/null) Nov 28 22:00:16 nimrodel smartd[5218]: Device: /dev/hdb, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 58 to 57 Nov 28 22:30:01 nimrodel /usr/sbin/cron[32324]: (cer) CMD (/home/cer/bin/avisar_hablando time > /dev/null) Nov 28 22:30:16 nimrodel smartd[5218]: Device: /dev/hdb, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 57 to 59 Nov 28 22:49:50 nimrodel syslog-ng[3823]: STATS: dropped 0 Nov 28 23:00:01 nimrodel /usr/sbin/cron[2188]: (cer) CMD (/home/cer/bin/avisar_hablando time > /dev/null) Nov 28 23:00:16 nimrodel smartd[5218]: Device: /dev/hda, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 72 to 71 Nov 28 23:00:17 nimrodel smartd[5218]: Device: /dev/hdb, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 59 to 60 Nov 28 23:30:01 nimrodel /usr/sbin/cron[4300]: (cer) CMD (/home/cer/bin/avisar_hablando time > /dev/null) Nov 28 23:45:02 nimrodel su: (to beagleindex) root on none Nov 28 23:45:02 nimrodel su: (to beagleindex) root on none Nov 28 23:45:18 nimrodel run-crons[5359]: beagle-crawl-system: OK Nov 28 23:45:32 nimrodel syslog-ng[3823]: SIGHUP received, restarting syslog-ng Nov 28 23:45:33 nimrodel syslog-ng[3823]: new configuration initialized Nov 28 23:45:42 nimrodel logrotate: ALERT exited abnormally with [1] Nov 28 23:45:42 nimrodel logrotate: /usr/bin/mysqladmin: connect to server at 'localhost' failed Nov 28 23:45:42 nimrodel logrotate: error: 'Access denied for user 'root'@'localhost' (using password: NO)' Nov 28 23:45:42 nimrodel logrotate: /etc/logrotate.d/mysql failed, probably because Nov 28 23:45:42 nimrodel logrotate: the root acount is protected by password. Nov 28 23:45:42 nimrodel logrotate: See comments in /etc/logrotate.d/mysql on how to fix this Nov 28 23:45:42 nimrodel logrotate: error: error running non-shared postrotate script for /var/lib/mysql/mysqld.log of '/var/lib/mysql/mysqld.log ' Nov 28 23:45:42 nimrodel logrotate: Reload syslog service..done Nov 28 23:45:42 nimrodel run-crons[5359]: logrotate: OK Nov 28 23:45:44 nimrodel run-crons[5359]: suse-clean_catman: OK Nov 28 23:47:36 nimrodel run-crons[5359]: suse-do_mandb: OK Nov 28 23:47:37 nimrodel su: (to nobody) root on none Nov 28 23:47:43 nimrodel syslog-ng[3823]: last message repeated 3 times Nov 28 23:47:43 nimrodel run-crons[5359]: suse-texlive: OK Nov 28 23:47:44 nimrodel run-crons[5359]: suse.de-backup-rc.config: OK Nov 28 23:47:47 nimrodel run-crons[5359]: suse.de-backup-rpmdb: OK Nov 28 23:47:47 nimrodel run-crons[5359]: suse.de-check-battery: OK Nov 28 23:47:49 nimrodel run-crons[5359]: suse.de-clean-tmp: OK Nov 28 23:47:49 nimrodel run-crons[5359]: suse.de-cron-local: OK Nov 28 23:47:49 nimrodel run-crons[5359]: suse.de-faxcron: OK Nov 28 23:47:49 nimrodel run-crons[5359]: suse.de-update-preload: OK Nov 28 23:47:49 nimrodel su: (to nobody) root on none Nov 28 23:48:34 nimrodel syslog-ng[3823]: last message repeated 2 times Nov 28 23:55:29 nimrodel syslog-ng[3823]: Cannot open file /dev/tty10 for writing (Permission denied) Nov 28 23:55:32 nimrodel run-crons[5359]: suse.de-updatedb: OK Nov 29 00:00:01 nimrodel /usr/sbin/cron[6804]: (root) CMD ( test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily &) Nov 29 00:00:01 nimrodel /usr/sbin/cron[6806]: (cer) CMD (/home/cer/bin/avisar_hablando time > /dev/null) Nov 29 00:00:17 nimrodel smartd[5218]: Device: /dev/hdb, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 60 to 59 Nov 29 00:00:17 nimrodel smartd[5218]: Device: /dev/hdd, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 60 to 59 Nov 29 00:00:17 nimrodel smartd[5218]: Device: /dev/hdd, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 60 to 59 While I write this Nov 29 00:30:01 nimrodel /usr/sbin/cron[9518]: (cer) CMD (/home/cer/bin/avisar_hablando time > /dev/null) Nov 29 00:30:16 nimrodel smartd[5218]: Device: /dev/hda, SMART Usage Attribute: 190 Temperature_Celsius changed from 73 to 72 Nov 29 00:30:16 nimrodel smartd[5218]: Device: /dev/hda, SMART Usage Attribute: 194 Temperature_Celsius changed from 27 to 28 Nov 29 00:30:16 nimrodel smartd[5218]: Device: /dev/hdb, SMART Usage Attribute: 194 Temperature_Celsius changed from 26 to 27 Nov 29 00:30:17 nimrodel smartd[5218]: Device: /dev/hdd, SMART Usage Attribute: 194 Temperature_Celsius changed from 33 to 34 I'll restart ntp in a while. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344356#c7 Michael Skibbe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #7 from Michael Skibbe 2007-11-29 01:38:12 MST --- to comment #2: why you have following entry? server pool.ntp.org server pool.ntp.org server pool.ntp.org server pool.ntp.org found somewhere in comment #7: [...] 29 Nov 00:31:30 ntpd[19587]: synchronized to LOCAL(0), stratum 10 [...] and [...] remote local st poll reach delay offset disp ======================================================================= =192.33.214.57 192.168.1.12 2 1024 377 0.13612 295.28592 0.13649 *LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03065 [...] looks like your hardware clock is broken. but ntp knows that the time difference between server and local is to huge and sync to the bad local. when you restart ntpdate is called which forces the time correction so ntp works fine until the time diffs to much... something in the system is wrong but it doesn't looks like ntp is the problem. you told this happens if you are at lunch. do you have a program which starts to run if the computer is idle? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344356 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=344356#c9 --- Comment #9 from Carlos Robinson 2007-12-04 14:10:08 MST --- I have more info. Doing this command: grep "time reset " /var/log/ntp | less I find interesting things. From last February (suse 10.2) till November 2nd, the resets are smaller than a second. From that point, which is the date when I upgraded to 10.3, the resets increase to several minutes! 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 to 10.3 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 .. 30 Nov 12:48:37 ntpd[11777]: time reset +28.109032 s 1 Dec 00:31:56 ntpd[8904]: time reset +403.049432 s 1 Dec 23:48:30 ntpd[10935]: time reset +74.982738 s 3 Dec 19:31:42 ntpd[29084]: time reset +309.343782 s 3 Dec 20:34:30 ntpd[29084]: time reset +220.290279 s 4 Dec 12:22:58 ntpd[5847]: time reset +0.168114 s 4 Dec 14:04:05 ntpd[5847]: time reset +243.829774 s 4 Dec 15:23:59 ntpd[5847]: time reset +173.514626 s 4 Dec 16:05:21 ntpd[5847]: time reset +4.773942 s That's a definite problem in the clock system / ntp client in 10.3! One could thing that the hybernation cycles could have something to do, but they didn't in 10.2; and recently (Nov 22) I installed a hook to reset the ntp client on every hybernation cycle. Yesterday I disabled these two lines in the ntp config: server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized And I can see the clock drifting fast when it loses the connection (without the message "synchronized to LOCAL(0), stratum 10"): 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 A 300" error in less than 20 minutes after "no servers reachable"! Before another 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 in 6' after the "no servers reachable" message. What is happening here? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344356 User mskibbe@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=344356#c11 Michael Skibbe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #11 from Michael Skibbe 2008-01-07 02:58:23 MST --- seems your hardware clock isn't working correct => invalid -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344356 User martin.burnicki@meinberg.de added comment https://bugzilla.novell.com/show_bug.cgi?id=344356#c13 --- Comment #13 from Martin Burnicki 2008-01-07 14:43:29 MST --- Michael, (In reply to comment #11 from Michael Skibbe)

seems your hardware clock isn't working correct => invalid

From what I've read here and in the mailing list I'm also pretty sure this is a kernel problem. Maybe the latest kernel changes have broken the kernel's support for this particular hardware.

Anyway, where do you see a clue that the hardware might be faulty? Martin -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344356 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=344356#c15 --- Comment #15 from Carlos Robinson 2008-01-08 05:29:41 MST --- No, you are confused. As shown in Bug 350981#4, it is not the hardware clock that is bad, it is the kernel managing the hardware clock that is faulty. I repeat, I booted suse 10.2 (on request) the other day to test this, and it run fine. It is 10.3 that is faulty. I agree that the fault is not ntpd, but I never claimed that it was: ntpd simply "discovered" the problem. The ntpd quiting was the symptom. It is a software problem in the kernel included with 10.3. It is absolutely not a hardware problem, but perhaps a software problem in handling a particular hardware. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344356 User mskibbe@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=344356#c17 Michael Skibbe changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mskibbe@novell.com AssignedTo|mskibbe@novell.com |bnc-team-screening@forge.provo.novell.com Status|REOPENED |NEW --- Comment #17 from Michael Skibbe 2008-01-08 05:47:36 MST --- please assign bug to someone who knows more about kernel time management. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=344356 User martin.burnicki@meinberg.de added comment https://bugzilla.novell.com/show_bug.cgi?id=344356#c19 --- Comment #19 from Martin Burnicki 2008-01-08 06:37:57 MST --- Just FYI, I fully agree with Carlos. Martin -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.