- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- System reboot
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2009 02:00 AM
09-27-2009 02:00 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2009 02:15 AM
09-27-2009 02:15 AM
Re: System reboot
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2009 05:44 AM
09-27-2009 05:44 AM
Re: System reboot
1. /etc/shutdownlog ?
2. /var/adm/syslog/OLDSyslog.log.
HTH,
Thanks,
Johnson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2009 05:46 AM
09-27-2009 05:46 AM
Re: System reboot
/var/tomstons/ts99.
Thanks,
Johnson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2009 09:58 AM
09-27-2009 09:58 AM
Re: System reboot
/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 *)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-27-2009 10:24 AM
09-27-2009 10:24 AM
SolutionAccessing 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