CLEANACCESS Archives

October 2006

CLEANACCESS@LISTSERV.MIAMIOH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Rajesh Nair (rajnair)" <[log in to unmask]>
Reply To:
Perfigo SecureSmart and CleanMachines Discussion List <[log in to unmask]>
Date:
Thu, 5 Oct 2006 12:29:23 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (63 lines)
Simon,

Can you send me the output of lspci -vv from the machine?

-Rajesh. 

-----Original Message-----
From: Perfigo SecureSmart and CleanMachines Discussion List
[mailto:[log in to unmask]] On Behalf Of Simon Bell
Sent: Thursday, October 05, 2006 5:50 AM
To: [log in to unmask]
Subject: Re: CAS Lockup

Rajesh,

Thanks for the reply. The only information I can discern from
/var/log/messages is that at 6:32am it locked up and at 9:01am when I
restarted it, it booted back up. I looked at the kernel messages and
didn't see anything alarming (granted I'm not real familiar with what's
typically in these messages), just some ACPI Warming messages which are
in the logs for all our HP DL140 CASs.

The server was hard locked. No keyboard, video, ping, ssh, etc. I
physically went to the server room, held down the power button for a few
sec, then to ensure the RAM had cleared out disconnected power for
10-15sec, then powered it up.

Simon

>>> 
From: 	"Rajesh Nair (rajnair)" <[log in to unmask]>
To:	<[log in to unmask]>
Date: 	10/4/2006 8:56 PM
Subject: 	Re: CAS Lockup

Simon,

Did the CAS logs (primarily /var/log/messages)have any clues around the
time that the lock up happened?  

Also, what do you mean by lock up?  Unreachable via network?  Or even
the keyboard/monitor/console not working? 

-Rajesh.

-----Original Message-----
From: Perfigo SecureSmart and CleanMachines Discussion List
[mailto:[log in to unmask]] On Behalf Of Simon Bell
Sent: Wednesday, October 04, 2006 7:44 AM
To: [log in to unmask]
Subject: CAS Lockup

I was curious if others ever experience one or more of their CASs hard
lock? That's what I found this morning on one of my CAS running 4.0.2 in
standalone. I bounced the box, came back up w/o problems, but it got me
thinking: where should I look for an underlying problem? I started snmp
monitoring it yesterday (coincidence?) and didn't see a CPU spike or
burst in traffic (granted it's snmp so it's possible I just didn't get
the packet), but what else should I look for? I openly admit I'm not
proficient in Linux, so any advice would be great.

Simon

ATOM RSS1 RSS2