cancel
Showing results for 
Search instead for 
Did you mean: 

System reboot

SOLVED
Go to solution
Spark_2
Frequent Advisor

System reboot

Hi,

What all can I check to find the probable reason for my system reboot. what all files and logs

Also how can cstm help? Need steps for cstm please
5 REPLIES
Hakki Aydin Ucar
Honored Contributor

Re: System reboot

Check /var/adm/syslog for general and if needs for startup logs check /etc/rc.log , you can check also what time it rebooted with command uptime OR -w for details.

if you use cstm an example below:

You may get ( For example: memory ) status throught the CSTM .
/usr/sbin/cstm
cstm>map
it will list all the devices
cstm> sel dev 63 # for memory info
cstm>info
cstm>infolog

But easier way to use graphic interface of cstm :

just issue command stm


Johnson Punniyalingam
Honored Contributor

Re: System reboot

>>What all can I check to find the probable reason for my system reboot. what all files and logs<<

1. /etc/shutdownlog ?
2. /var/adm/syslog/OLDSyslog.log.


HTH,

Thanks,
Johnson

Problems are common to all, but attitude makes the difference
Johnson Punniyalingam
Honored Contributor

Re: System reboot

would also like check, any valid ts99 files has been created.

/var/tomstons/ts99.

Thanks,
Johnson
Problems are common to all, but attitude makes the difference
Michael Steele_2
Honored Contributor

Re: System reboot

Hi

/etc/shutdownlog - (* pri. log used by HP CE's, you'll see something like 'reboot after panic' and a chasis code. Post the code. *)

/var/tombstones - MCA's for Integrity, HPMCs for PA-Risc - Verify the time stamp inside the ts99 file

cstm - infolog (* useless *)

/var/adm/syslog/syslog.log (* often *)

/var/adm/crash (* after any crash, there will be a dump file and this is what HP will need *)

Note: If you didn't get a crash dump, and it hasn't been too long or if too much work hasn't been performed, then you can still recover the dump from the command line:

savecrash -r /tmp/crash (* or any place you select with enough space *)
Support Fatherhood - Stop Family Law
Matti_Kurkela
Honored Contributor
Solution

Re: System reboot

And if the logs of the OS tell you nothing, the problem may have been at the hardware level. In that case, the hardware log in the system's management processor might be helpful.

Accessing the management processor:
Go to the system console, so that you'll see the login prompt. Press Ctrl-B to switch to the management processor, if your hardware model has it (just about all non-obsolete ones have it). The "SL" command will display the hardware logs. "HE" gives help about using the management processor.

MK
MK