Re: time messed up since last kernel update
On Tue, Feb 12, 2008 at 05:49:29PM -0500, Joey Hess wrote: KS wrote: Is it the same as [EMAIL PROTECTED] ? Joey replied to a similar query about kernel clock yesterday. I'd need to see hwclock output to know for sure. Probably though. Give me a command to run and I'll run it and send the output. I manually ran the /etc/init.d/hwclock.sh stop, then did a system reboot, into single-user mode, verified that the time was correct, then exited and allowed the system to go to RL 2, logged in and did a shutdown -h. System powered off. I powered-off the PSU and waited 1 minute. I then powered up the PSU and the computer, as it should, restarted. The time seemed correct. I pon'd internet, ntp sync'd and reset the time by about 1s. I then manually entered the run-parts command for cron.daily. Thanks, Doug. --- In case it helps, here's: $ ls -l /var/log total 5.3M -rw--- 1 rootroot32K Feb 11 23:28 Xorg.0.log -rw--- 1 rootroot32K Feb 11 17:33 Xorg.0.log.old -rw-r--r-- 1 rootroot32K Feb 9 13:06 Xorg.1.log -rw-r--r-- 1 rootroot32K Feb 9 12:46 Xorg.1.log.old -rw-r- 1 rootroot274 Feb 12 19:55 acpid -rw-r- 1 rootroot 64 Dec 31 2005 acpid.1.gz -rw-r- 1 rootroot819 Dec 31 2005 acpid.2.gz -rw-r- 1 rootroot 2.3K Feb 10 07:13 acpid.3.gz -rw-r- 1 rootroot 1.5K Feb 3 10:37 acpid.4.gz drwxr-xr-x 2 rootroot 4.0K Aug 26 2006 afbackup/ -rw-r--r-- 1 rootroot 0 Dec 31 2005 aptitude -rw-r--r-- 1 rootroot830 Feb 11 23:04 aptitude.1.gz -rw-r--r-- 1 rootroot 1.3K Jan 31 21:13 aptitude.2.gz -rw-r--r-- 1 rootroot988 Dec 28 22:52 aptitude.3.gz -rw-r--r-- 1 rootroot680 Nov 27 23:06 aptitude.4.gz -rw-r--r-- 1 rootroot 1.4K Oct 26 21:41 aptitude.5.gz -rw-r--r-- 1 rootroot 1.1K Sep 30 00:04 aptitude.6.gz -rw-r- 1 rootadm 445 Feb 12 20:32 auth.log -rw-r- 1 rootadm 58K Feb 12 20:01 auth.log.0 -rw-r- 1 rootadm6.7K Feb 7 07:58 auth.log.1.gz -rw-r- 1 rootadm7.3K Jan 31 08:45 auth.log.2.gz -rw-r- 1 rootadm8.4K Jan 24 09:26 auth.log.3.gz -rw-r- 1 rootadm4.2K Feb 12 19:55 boot -rw-r- 1 rootadm2.5K Feb 12 19:53 boot.0 -rw-r- 1 rootadm1.4K Dec 31 2005 boot.1.gz -rw-r- 1 rootadm1.3K Feb 11 16:04 boot.2.gz -rw-r- 1 rootadm1.3K Feb 11 15:15 boot.3.gz -rw-r- 1 rootadm1.4K Feb 11 15:03 boot.4.gz -rw-rw-r-- 1 rootutmp 0 Feb 12 08:12 btmp -rw-rw-r-- 1 rootutmp 0 Dec 31 2005 btmp.1 -rw-r- 1 rootadm3.3K Feb 12 21:14 daemon.log -rw-r- 1 rootadm382K Feb 12 19:55 daemon.log.0 -rw-r- 1 rootadm 30K Feb 7 07:51 daemon.log.1.gz -rw-r- 1 rootadm 44K Jan 31 08:38 daemon.log.2.gz -rw-r- 1 rootadm 38K Jan 24 09:20 daemon.log.3.gz -rw-r- 1 rootadm 0 Feb 12 20:05 debug -rw-r- 1 rootadm 81K Feb 12 19:55 debug.0 -rw-r- 1 rootadm6.2K Feb 7 07:51 debug.1.gz -rw-r- 1 rootadm5.9K Jan 31 08:38 debug.2.gz -rw-r- 1 rootadm3.4K Jan 24 09:20 debug.3.gz -rw-r- 1 rootadm 22K Feb 12 19:55 dmesg -rw-r- 1 rootadm 23K Feb 12 19:53 dmesg.0 -rw-r- 1 rootadm6.3K Dec 31 2005 dmesg.1.gz -rw-r- 1 rootadm6.3K Feb 11 16:04 dmesg.2.gz -rw-r- 1 rootadm6.2K Feb 11 15:15 dmesg.3.gz -rw-r- 1 rootadm6.2K Feb 11 15:03 dmesg.4.gz -rw-r- 1 rootadm 0 Dec 31 2005 dpkg.log -rw-r- 1 rootadm 16K Feb 11 23:04 dpkg.log.1 -rw-r- 1 rootadm2.9K Jan 31 21:13 dpkg.log.2.gz -rw-r- 1 rootadm2.2K Dec 28 22:52 dpkg.log.3.gz -rw-r- 1 rootadm 916 Nov 27 23:06 dpkg.log.4.gz -rw-r- 1 rootadm3.7K Oct 26 21:41 dpkg.log.5.gz -rw-r- 1 rootadm2.4K Sep 30 00:42 dpkg.log.6.gz -rw-r- 1 rootadm 34K Aug 30 21:35 dpkg.log.7.gz drwxr-s--- 2 Debian-exim adm4.0K Feb 12 08:12 exim4/ -rw-r--r-- 1 rootroot32K Feb 12 20:01 faillog drwxrwx--- 2 rootbackup 4.0K Sep 23 2006 flexbackup/ -rw-r--r-- 1 rootroot 1.7K Aug 21 20:13 fontconfig.log drwxr-xr-x 2 rootroot 4.0K Aug 17 13:06 fsck/ -rw-r- 1 rootadm 300 Feb 12 20:32 kern.log -rw-r- 1 rootadm410K Feb 12 19:55 kern.log.0 -rw-r- 1 rootadm 97K Feb 7 07:51 kern.log.1.gz -rw-r- 1 rootadm 90K Jan 31 08:38 kern.log.2.gz -rw-r- 1 rootadm 47K Jan 24 09:20 kern.log.3.gz -rw-rw-r-- 1 rootutmp 287K Feb 12 20:01 lastlog -rw-r- 1 rootadm 0 Feb 12 08:12 logaudit.log -rw-r- 1 rootadm1.2K Feb 12 08:12
Re: time messed up since last kernel update
KS wrote: Is it the same as [EMAIL PROTECTED] ? Joey replied to a similar query about kernel clock yesterday. I'd need to see hwclock output to know for sure. Probably though. -- see shy jo signature.asc Description: Digital signature
Re: time messed up since last kernel update
Douglas A. Tutty wrote: follow-up, see below On Tue, Feb 12, 2008 at 08:21:26AM -0500, dtutty wrote: I'm running Etch-amd64 and updated the kernel yesterday. I shutdown the computer nightly. Today, when I booted up and read the daily report from anacron, I get lots of message from logrotate about logs being rotated are in the future. The new logs are dated 2005. I pon'ed the internet and ntp reset the clock. Here's a segment of syslog. You can see that prior to ntp setting the clock, the computer thought that it was Dec 31. Is it the same as [EMAIL PROTECTED] ? Joey replied to a similar query about kernel clock yesterday. HTH. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: time messed up since last kernel update
follow-up, see below On Tue, Feb 12, 2008 at 08:21:26AM -0500, dtutty wrote: I'm running Etch-amd64 and updated the kernel yesterday. I shutdown the computer nightly. Today, when I booted up and read the daily report from anacron, I get lots of message from logrotate about logs being rotated are in the future. The new logs are dated 2005. I pon'ed the internet and ntp reset the clock. Here's a segment of syslog. You can see that prior to ntp setting the clock, the computer thought that it was Dec 31. Dec 31 19:44:54 titan ntpd[5610]: ntpd exiting on signal 15 Dec 31 19:44:56 titan ntpd[6973]: ntpd [EMAIL PROTECTED] Sun Mar 4 13:05:22 UTC 2007 (1) Dec 31 19:44:56 titan ntpd[6974]: precision = 1.000 usec Dec 31 19:44:56 titan ntpd[6974]: Listening on interface wildcard, 0.0.0.0#123 Disabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface wildcard, ::#123 Disabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface lo, ::1#123 Enabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface eth1, fe80::217:31ff:fecb:efeb#123 Enabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface lo, 127.0.0.1#123 Enabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface eth1, 192.168.1.1#123 Enabled Dec 31 19:44:56 titan ntpd[6974]: Listening on interface ppp0, 209.29.44.1#123 Enabled Dec 31 19:44:56 titan ntpd[6974]: kernel time sync status 0040 Dec 31 19:44:56 titan ntpd[6974]: frequency initialized -35.886 PPM from /var/lib/ntp/ntp.drift Dec 31 19:45:06 titan ntpd_initres[5629]: parent died before we finished, exiting Feb 12 08:06:47 titan ntpd[6974]: synchronized to 132.246.168.164, stratum 2 Feb 12 08:06:47 titan ntpd[6974]: time reset +66745300.210157 s Feb 12 08:06:47 titan ntpd[6974]: kernel time sync enabled 0001 Did anybody else have this problem? I guess I'll see if there's a problem tomorrow. In case it matters, this is an Athlon64 3800+, socket AM2, on an Asus M2N-SLI Deluxe MB (nVidia chipset uses Forcedeth driver) with 1 GB ram. Doug. Here's a segment from my logaudit output: Logaudit run Tue Feb 12 08:12:30 2008 Tue Feb 12 08:12:30 2008: Using /etc/logaudit/exclude. Tue Feb 12 08:12:30 2008: Using /etc/logaudit/checklogs. Tue Feb 12 08:12:30 2008: Unable to open log file: /var/log/warning.log for reading. Skipping. From log :/var/log/auth.log Feb 11 20:07:47 titan login[6445]: FAILED LOGIN (1) on 'tty1' FOR `dtutty', Authentication failure Dec 31 19:06:34 titan su[5796]: (pam_unix) account nobody has password changed in future Dec 31 19:06:35 titan su[5800]: (pam_unix) account nobody has password changed in future Dec 31 19:06:35 titan su[5803]: (pam_unix) account nobody has password changed in future Dec 31 19:07:53 titan su[5987]: (pam_unix) account proxy has password changed in future Dec 31 19:17:01 titan CRON[6831]: (pam_unix) account root has password changed in future Dec 31 19:43:53 titan sshd[6840]: (pam_unix) account dtutty has password changed in future Feb 12 08:12:28 titan su[7191]: + pts/0 root:nobody From log :/var/log/syslog Dec 31 19:11:35 titan lpd[6115]: restarted Dec 31 19:44:54 titan ntpd[5610]: ntpd exiting on signal 15 Dec 31 19:45:06 titan ntpd_initres[5629]: parent died before we finished, exiting Feb 12 08:06:47 titan ntpd[6974]: synchronized to 132.246.168.164, stratum 2 Feb 12 08:06:47 titan ntpd[6974]: time reset +66745300.210157 s So the time was changed to Dec 31 some time after 20:07 (-0500) last evening which was some time around when the kernel was updated. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
