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

[cobalt-users] Many crashes after updating XTR to 550



I have updated my RaQ XTR to use the RaQ 550 OS. Now, I seem to be getting
at least one crash a day. (Sometimes two or three.) It only seems to
happen at periods of high activity. I would love to be able to verify
that my disks, fans, memory, roms, etc, are as they should be. The
only thing that all the times have in common is that I always had a
ssh connection up. Can someone tell me how to procede to fix the
problems!


Her are the number of times it has crashed since Mon Dec 1 08:18:15
2003

bash-2.04$ last -x | grep 'crash'
josh     pts/1        flatterer.librar Wed Dec  3 09:23 - crash  (02:19)    
josh     pts/0        flatterer.librar Wed Dec  3 09:06 - crash  (02:36)    
josh     pts/2        gw-josh-dsl.heav Tue Dec  2 21:07 - crash  (00:26)    
josh     pts/1        gw-josh-dsl.heav Tue Dec  2 20:21 - crash  (01:11)    
josh     pts/0        flatterer.librar Tue Dec  2 17:52 - crash  (03:41)    
josh     pts/1        flatterer.librar Tue Dec  2 10:38 - crash  (04:42)    
josh     pts/0        flatterer.librar Tue Dec  2 10:37 - crash  (04:42)    
josh     pts/0        alb-66-65-239-18 Mon Dec  1 09:40 - crash  (00:56)    

[12:02:14:war-admiral:~]sudo grep 'syslogd' /var/log/messages
Nov 30 04:02:00 war-admiral syslogd 1.3-3: restart.
Nov 30 04:02:01 war-admiral syslogd 1.3-3: restart.
Nov 30 04:02:01 war-admiral syslogd 1.3-3: restart.
Nov 30 04:02:04 war-admiral syslogd 1.3-3: restart.
Nov 30 04:02:04 war-admiral syslogd 1.3-3: restart.
Nov 30 04:02:04 war-admiral syslogd 1.3-3: restart.
Dec  1 04:02:04 war-admiral syslogd 1.3-3: restart.
Dec  1 10:36:34 war-admiral syslogd 1.3-3: restart.
Dec  2 04:02:10 war-admiral syslogd 1.3-3: restart.
Dec  2 15:20:02 war-admiral syslogd 1.3-3: restart.
Dec  2 21:33:34 war-admiral syslogd 1.3-3: restart.
Dec  3 04:03:49 war-admiral syslogd 1.3-3: restart.
Dec  3 11:43:16 war-admiral syslogd 1.3-3: restart.


-- 
Josh Kuperman                       
josh@xxxxxxxxxxxxxxxxxx