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]