[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Computer shut down unexpectedly while unattended.



Adam Funk <a24061@yahoo.com> writes:
>
> When I got up this morning I found that my computer had 
> mysteriously powered down overnight around 02:50.

There's nothing the least bit suspicious in the logs you gave.  It was
probably just a power outage.  Do you have any reason to believe it
was something else?

> Here are are the last log entries before it happened.

If you really want to know what caused them...

> /var/log/syslog
> Mar 10 02:30:01 garcia /USR/SBIN/CRON[23159]: (root) CMD (test -x /usr/lib/atsar/atsa1 && /usr/lib/atsar/atsa1)
> Mar 10 02:40:01 garcia /USR/SBIN/CRON[23166]: (root) CMD (test -x /usr/lib/atsar/atsa1 && /usr/lib/atsar/atsa1)
> Mar 10 02:40:01 garcia /USR/SBIN/CRON[23167]: (root) CMD (nice -7 /usr/local/exim/bin/exim -q)
> Mar 10 02:50:01 garcia /USR/SBIN/CRON[23173]: (root) CMD (test -x /usr/lib/atsar/atsa1 && /usr/lib/atsar/atsa1)

Cron ran four jobs as root because:

1.  You have "atsar" installed.  I've never used it, but judging from
    the package description, it's no surprise that it runs
    periodically to collect system performance information.

2.  You have a custom Exim installion.  The above line is the usual,
    periodic queue run to retry sending messages that have temporary
    delivery failures.

> /var/log/messages
> Mar 10 01:50:46 garcia -- MARK --
> Mar 10 02:10:46 garcia -- MARK --
> Mar 10 02:30:46 garcia -- MARK --

These lines are inserted by "syslogd".  It's just to ensure a regular
message gets written to "messages".

> /var/log/auth.log
> Mar 10 02:40:01 garcia cron(pam_unix)[23165]: session closed for user root
> Mar 10 02:50:01 garcia cron(pam_unix)[23172]: session opened for user root by (uid=0)
> Mar 10 02:50:01 garcia cron(pam_unix)[23172]: session closed for user root

These are normal.  Cron generates these messages when it's running
jobs as root.  These specific messages correspond to cron running the
"atsar" and Exim cron jobs mentioned above.

-- 
Kevin <buhr@telus.net>



Reply to: