This morning between 07:10 or so and 08:10 I discovered that my PC had shut itself off. I thought it was due to a power failure becuase I never turn it off without a good reason, and it had been running (and playing sounds) until it wasn't. My roommate/landlord tells me that the only anomaly he observed was that our router had lost its internet connection (via a cable modem, which was still running fine), and his computer, a laptop, and clocks all seemed to be running normally.
I checked all the logs in /var/log and there's nothing in there other than the restart - no temp warnings or anything. The machine has been up and running smoothly since the last time I shut it off (to move), a week ago last Friday (8/6).
I don't have a UPS or BB, so is there any way that I can diagnose this further?
Here's another weird thing - 'dmesg | grep Aug' shows this:
Linux version 2.6.18-194.11.1.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Aug 10 19:05:06 EDT 2010 EDAC MC: Ver: 2.0.1 Aug 10 2010 EDAC amd64_edac: Ver: 3.2.0 Aug 10 2010
That's probably when I last restarted after installing the new kernel. But:
$ date Wed Aug 18 11:52:23 PDT 2010
And /var/log/messages shows this:
: Aug 18 06:35:57 marichter dhclient: DHCPREQUEST on eth0 to 192.168.0.2 port 67 Aug 18 06:35:57 marichter dhclient: DHCPACK from 192.168.0.2 Aug 18 06:35:57 marichter dhclient: bound to 192.168.0.100 -- renewal in 5154 se conds. Aug 18 06:44:28 marichter smartd[3829]: Device: /dev/sdb, 4294967295 Currently u nreadable (pending) sectors Aug 18 06:44:28 marichter smartd[3829]: Device: /dev/sdb, 4294967295 Offline unc orrectable sectors Aug 18 08:10:45 marichter syslogd 1.4.1: restart. Aug 18 08:10:45 marichter kernel: klogd 1.4.1, log source = /proc/kmsg started. Aug 18 08:10:45 marichter kernel: Linux version 2.6.18-194.11.1.el5 (mockbuild@b uilder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Aug 10 19:05:06 EDT 2010 :
What's up with that??? (Not the disk issue - that's a Seagate problem that, fortunately, means nothing, and yes, I've gone through that one before....) Why doesn't dmesg show the most recent boot?
marichter 2.6.18-194.11.1.el5 #1 SMP Tue Aug 10 19:05:06 EDT 2010 x86_64 GNU/Linux centos-release-5-5.el5.centos.x86_64
Thanks.
Mark
On Wed, 18 Aug 2010, Mark wrote:
Here's another weird thing - 'dmesg | grep Aug' shows this:
Linux version 2.6.18-194.11.1.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Aug 10 19:05:06 EDT 2010 EDAC MC: Ver: 2.0.1 Aug 10 2010 EDAC amd64_edac: Ver: 3.2.0 Aug 10 2010
That's probably when I last restarted after installing the new kernel.
I don't think so. The Aug 10 date is the *build date* for the kernel, not a boot date.
On Wed, Aug 18, 2010 at 12:06 PM, Paul Heinlein heinlein@madboa.com wrote:
On Wed, 18 Aug 2010, Mark wrote:
Here's another weird thing - 'dmesg | grep Aug' shows this:
Linux version 2.6.18-194.11.1.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Aug 10 19:05:06 EDT 2010 EDAC MC: Ver: 2.0.1 Aug 10 2010 EDAC amd64_edac: Ver: 3.2.0 Aug 10 2010
That's probably when I last restarted after installing the new kernel.
I don't think so. The Aug 10 date is the *build date* for the kernel, not a boot date.
Yeah - senior moment....
Thanks.
On Wed, 18 Aug 2010, Mark wrote:
Yeah - senior moment....
/me looks in the mirror and nods sadly...
On Wed, 18 Aug 2010, Paul Heinlein wrote:
On Wed, 18 Aug 2010, Mark wrote:
Yeah - senior moment....
/me looks in the mirror and nods sadly...
hmmm -- I'll not ask, with a mug like mine http://a0.twimg.com/profile_images/73126828/boar-twitter.png
-- R
On Wed, 2010-08-18 at 11:57 -0700, Mark wrote:
This morning between 07:10 or so and 08:10 I discovered that my PC had shut itself off. I thought it was due to a power failure becuase I never turn it off without a good reason, and it had been running (and playing sounds) until it wasn't. My roommate/landlord tells me that the only anomaly he observed was that our router had lost its internet connection (via a cable modem, which was still running fine), and his computer, a laptop, and clocks all seemed to be running normally.
I checked all the logs in /var/log and there's nothing in there other than the restart - no temp warnings or anything. The machine has been up and running smoothly since the last time I shut it off (to move), a week ago last Friday (8/6).
I don't have a UPS or BB, so is there any way that I can diagnose this further?
Here's another weird thing - 'dmesg | grep Aug' shows this:
Linux version 2.6.18-194.11.1.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Aug 10 19:05:06 EDT 2010 EDAC MC: Ver: 2.0.1 Aug 10 2010 EDAC amd64_edac: Ver: 3.2.0 Aug 10 2010
That's probably when I last restarted after installing the new kernel. But:
$ date Wed Aug 18 11:52:23 PDT 2010
And /var/log/messages shows this:
: Aug 18 06:35:57 marichter dhclient: DHCPREQUEST on eth0 to 192.168.0.2 port 67 Aug 18 06:35:57 marichter dhclient: DHCPACK from 192.168.0.2 Aug 18 06:35:57 marichter dhclient: bound to 192.168.0.100 -- renewal in 5154 se conds. Aug 18 06:44:28 marichter smartd[3829]: Device: /dev/sdb, 4294967295 Currently u nreadable (pending) sectors Aug 18 06:44:28 marichter smartd[3829]: Device: /dev/sdb, 4294967295 Offline unc orrectable sectors Aug 18 08:10:45 marichter syslogd 1.4.1: restart. Aug 18 08:10:45 marichter kernel: klogd 1.4.1, log source = /proc/kmsg started. Aug 18 08:10:45 marichter kernel: Linux version 2.6.18-194.11.1.el5 (mockbuild@b uilder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Aug 10 19:05:06 EDT 2010 :
What's up with that??? (Not the disk issue - that's a Seagate problem that, fortunately, means nothing, and yes, I've gone through that one before....) Why doesn't dmesg show the most recent boot?
marichter 2.6.18-194.11.1.el5 #1 SMP Tue Aug 10 19:05:06 EDT 2010 x86_64 GNU/Linux centos-release-5-5.el5.centos.x86_64
Thanks.
Mark _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Mark,
You can look through the output of the 'last' command. last may tell you what the state of the system was before it rebooted/crashed and also the time it happened. 'last -x' will tell you more detailed information regarding system shutdowns and run level changes.
Example of a crash:
runlevel (to lvl 2) 2.6.32-24-server Wed Aug 18 10:10 - 15:44 (05:34) reboot system boot 2.6.32-24-server Wed Aug 18 10:10 - 15:44 (05:34) user1 pts/6 10.10.10.10 Wed Aug 18 09:37 - crash (00:33)
On Wed, 2010-08-18 at 15:51 -0400, Preston Connors wrote:
Mark,
You can look through the output of the 'last' command. last may tell you what the state of the system was before it rebooted/crashed and also the time it happened. 'last -x' will tell you more detailed information regarding system shutdowns and run level changes.
Example of a crash:
runlevel (to lvl 2) 2.6.32-24-server Wed Aug 18 10:10 - 15:44 (05:34) reboot system boot 2.6.32-24-server Wed Aug 18 10:10 - 15:44 (05:34) user1 pts/6 10.10.10.10 Wed Aug 18 09:37 - crash (00:33)
--- who :0 Tue Jun 1 09:48 - 09:48 (00:00) who pts/3 foo Tue Jun 1 09:46 - crash (5+00:06) who pts/2 foo Tue Jun 1 09:46 - crash (5+00:06) who :0 Tue Jun 1 09:22 - 09:45 (00:22)
Hmm looks like mine keep on getting it... I wonder why? ""reboot system boot 2.6.24.7-148.JonE2 Sun Jun 6 09:52 (00:20) ""
Only the names have been scrubbed. Point being crash does not mean the machine died, rebooted or shutdown. Load Avg was 13.0 - 53.0.
John
-
JohnS -
Mark -
Paul Heinlein -
Preston Connors -
R P Herrold