How to figure out why a computer rebooted?

From: Adam Funk (a24061_at_yahoo.com)
Date: 11/16/05

  • Next message: zaiskime kartu: "kvietimas" 
    To: debian-user@lists.debian.org
Date: Wed, 16 Nov 2005 11:34:27 +0000

    I'm disturbed that I've received a "Reboot" logcheck report from a
    computer to which I don't have physical access right now. I logged in
    by ssh and looked at /var/log/syslog, which shows routine stuff, then
    a 3-minute gap, then the restart log entries.

    Nov 16 08:02:01 argon /USR/SBIN/CRON[16445]: (logcheck) CMD ( if [ -x /usr/sbin/logcheck ]; then nice -n10 /usr/sbin/logcheck; fi)
    Nov 16 08:02:01 argon /USR/SBIN/CRON[16446]: (root) CMD (/root/bin/minute)
    Nov 16 08:03:01 argon /USR/SBIN/CRON[17248]: (root) CMD (/root/bin/minute)
    Nov 16 08:04:01 argon /USR/SBIN/CRON[17251]: (root) CMD (/root/bin/minute)
    Nov 16 08:05:01 argon /USR/SBIN/CRON[17255]: (root) CMD (/root/bin/minute)
    Nov 16 08:06:01 argon /USR/SBIN/CRON[17259]: (root) CMD (/root/bin/minute)
    Nov 16 08:09:15 argon syslogd 1.4.1#17: restart.
    Nov 16 08:09:16 argon kernel: klogd 1.4.1#17, log source = /proc/kmsg started.
    Nov 16 08:09:16 argon kernel: Inspecting /boot/System.map-2.4.27-2-386
    Nov 16 08:09:16 argon kernel: Loaded 18328 symbols from /boot/System.map-2.4.27-2-386.
    Nov 16 08:09:16 argon kernel: Symbols match kernel version 2.4.27.
    Nov 16 08:09:16 argon kernel: Loaded 787 symbols from 36 modules.

    A few days ago I deliberately shut the machine down for a while (with
    physical access) and produced the following bit of syslog.

    Nov 12 12:56:01 argon /USR/SBIN/CRON[21427]: (root) CMD (/root/bin/minute)
    Nov 12 12:57:01 argon /USR/SBIN/CRON[21430]: (root) CMD (/root/bin/minute)
    Nov 12 12:58:01 argon /USR/SBIN/CRON[21433]: (root) CMD (/root/bin/minute)
    Nov 12 12:58:19 argon gdm[3158]: Master halting...
    Nov 12 12:58:19 argon shutdown[3158]: shutting down for system halt
    Nov 12 12:58:19 argon init: Switching to runlevel: 0
    Nov 12 12:58:24 argon xfs[2254]: terminating
    Nov 12 12:58:25 argon xfs[2257]: terminating
    Nov 12 12:58:27 argon chronyd[30148]: chronyd exiting on signal
    Nov 12 12:58:27 argon rpc.statd[2457]: Caught signal 15, un-registering and exiting.
    Nov 12 12:58:27 argon exiting on signal 15
    Nov 12 13:16:21 argon syslogd 1.4.1#17: restart.
    Nov 12 13:16:22 argon kernel: klogd 1.4.1#17, log source = /proc/kmsg started.
    Nov 12 13:16:22 argon kernel: Inspecting /boot/System.map-2.4.27-2-386
    Nov 12 13:16:22 argon kernel: Loaded 18328 symbols from /boot/System.map-2.4.27-2-386.
    Nov 12 13:16:22 argon kernel: Symbols match kernel version 2.4.27.
    Nov 12 13:16:22 argon kernel: Loaded 787 symbols from 36 modules.

    Obviously if I get home and the digital clocks are flashing, I'll know
    there was a brief power cut. But is there any way to determine from
    the computer's own evidence why it restarted?

    Thanks,
    Adam 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: zaiskime kartu: "kvietimas"