Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
HP 9000 and HP e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

Server crashed. Came back up. Don't know why.

Ravi S. Banda
Regular Advisor

Server crashed. Came back up. Don't know why.

Attached, please find the /var/tombstones/ts99.

Nothing under /var/adm/crash this year. Nothing from the date of the crash or after in /etc/shutdownlog. The last line is from Mon Jan 25, 2010. No error messages in /var/adm/syslog/OLDsyslog.log file.

But, the server crashed and came back up, though. Any input is greatly appreciate!!!
6 REPLIES
Robert_Jewell
Honored Contributor

Re: Server crashed. Came back up. Don't know why.

A few things to ask...

First, nothing was attached, try again!

Second, what is the system model?

Last, how do you know there was a "crash"? Do you have any console logs to share?


-Bob
----------------
Was this helpful? Like this post by giving me a thumbs up below!
Ravi S. Banda
Regular Advisor

Re: Server crashed. Came back up. Don't know why.

I'm trying to attach. let's see if it really does attach this time.

9000/800/L3000-8x

The uptime shows 'up 2 days'.

This is all I see in the Console logs for that date:

Log Entry # 0 :
SYSTEM NAME: hpbackupgsp
DATE: 02/09/2010 TIME: 16:34:24
ALERT LEVEL: 2 = Non-Urgent operator attention required

SOURCE: 3 = PDH
SOURCE DETAIL: 6 = interconnect medium SOURCE ID: 0
PROBLEM DETAIL: 3 = non-responding, may need GSP reset.

CALLER ACTIVITY: 2 = operation STATUS: 0
CALLER SUBACTIVITY: 02 = platform internal interconnect
REPORTING ENTITY TYPE: 1 = service processor REPORTING ENTITY ID: 00

0x5810082336002020 00006E01 09102218 type 11 = Timestamp 02/09/2010 16:34:24
Type CR for next entry, Q CR to quit.
Ravi S. Banda
Regular Advisor

Re: Server crashed. Came back up. Don't know why.

looks like, the attachments are not working. it takes me to a blank page once I attach anything. :(

can I upload to any ftp site?
Robert_Jewell
Honored Contributor

Re: Server crashed. Came back up. Don't know why.

Well, to quickly see if the tombstone file is valid you can do this:

# head /var/tombstones/ts99

Look at the timestamp. If it reflects the time of the crash then the system crashed with an HPMC. If the timestamp is not valid, then its not worth reviewing.

The L class does have a console log, you can run CL from the GSP and keep pressing ENTER to see if you can capture the actual panic.

Aside from that there will not be anything to go by and not much you can do except hope it doesnt happen again!


-Bob
----------------
Was this helpful? Like this post by giving me a thumbs up below!
Michael Steele_2
Honored Contributor

Re: Server crashed. Came back up. Don't know why.

Hi

Save your attachement as txt. The ts99 file never over writes itself, only appends to it. So only the top of the file for the first thousand or so lines are needed.
Support Fatherhood - Stop Family Law
Michael Steele_2
Honored Contributor

Re: Server crashed. Came back up. Don't know why.

Hi

check these files

/etc/shutdownlog (* last line *)
/etc/opt/resmon/log/*

control b
cm
event logs from GSP

/var/adm/crash

Either an MCA or an HPMC will appear in /var/tombstones ( Ia64 / Pa Risc ). Grep for them.
Support Fatherhood - Stop Family Law