Re: [cobalt-users] Qube2 Crashes without obvious cause

[Mike Vanecek <nospam99@xxxxxxxxxxxx>]

On Thu, 07 Dec 2000 23:23:34 +1100, Malcolm McLeary <mmcleary@xxxxxxx> wrote:

:>Hi Guys,
:>
:>I have a Qube2 which was doing fine, but is now "crashing" for no apparent
:>reason.
:>
:>Looking in the current and previous logs (i.e /var/log/messages) it would
:>appear that this server has been restarted a few times in recent weeks,
:>however the owner only told me about it today after it was DOA (dead on
:>arrival at work).
:>
:>Nov 14 09:21:32 microserver syslogd 1.3-3: restart.
:>
:>Nov 17 13:12:05 microserver kernel: IPX Portions Copyright (c) 1995 Caldera
:>Nov 17 15:06:37 microserver syslogd 1.3-3: restart.
:>
:>Nov 17 15:15:13 microserver proftpd[684]: FTP session closed.
:>Nov 17 15:46:35 microserver syslogd 1.3-3: restart.
:>
:>Nov 21 01:36:16 microserver kernel: IPX Portions Copyright (c) 1995 Caldera
:>Nov 21 09:22:30 microserver syslogd 1.3-3: restart.
:>
:>Nov 21 15:30:13 microserver proftpd[5048]: FTP session closed.
:>Nov 21 16:05:18 microserver syslogd 1.3-3: restart.
:>
:>Nov 23 11:25:28 microserver kernel: IPX Portions Copyright (c) 1995 Caldera
:>Nov 23 12:50:54 microserver syslogd 1.3-3: restart.
:>
:>Nov 27 14:00:12 microserver proftpd[26905]: FTP session closed.
:>Nov 27 15:34:01 microserver syslogd 1.3-3: restart.
:>
:>Dec  4 01:45:18 microserver proftpd[3334]: FTP session closed.
:>Dec  4 09:18:11 microserver syslogd 1.3-3: restart.
:>
:>Dec  7 01:21:17 microserver kernel: IPX Portions Copyright (c) 1995 Caldera
:>Dec  7 09:18:25 microserver syslogd 1.3-3: restart.
:>
:>These entries are simply the last line in messages prior to the actual
:>restart entries (not just any syslogd  1.3-3: restart entries).
:>
:>Unfortunately there is nothing unusual in the log up to the point when it
:>stops responding to give me any hints as to why it has "stopped".
:>
:>As you will note, few have been during business hours, the others sometime
:>after 1am and then getting power cycled when the office opens for the day.
:>
:>Any suggestions as to how to track down the real problem?
:>

Power failures?  Cleaning crew pulling the plug out?  Anything in the
/var/cobalt/ monitor logs (since they get updated every 15 minutes - unless
you have changed crontab like I have to do a monitor every 6 hours)? You can
check memory and disk usage there. What changes have been made to the system
or the environment that might suggest a cause? 

Ain't computers fun?

Mike.