HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- system crash
Operating System - HP-UX
1833869
Members
1640
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
11-03-2005 08:15 AM
11-03-2005 08:15 AM
Hello,
We have just had a system crash and wanted to know a couple of things:
1> I have checked syslog and the below error displayed:
Nov 3 21:06:56 spbe895a vmunix: DIAGNOSTIC SYSTEM WARNING:
Nov 3 21:06:56 spbe895a vmunix: The diagnostic logging facility has started receiving excessive
Nov 3 21:06:56 spbe895a vmunix: errors from the I/O subsystem. I/O error entries will be lost
Nov 3 21:06:56 spbe895a vmunix: until the cause of the excessive I/O logging is corrected.
Nov 3 21:06:56 spbe895a vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
Nov 3 21:06:56 spbe895a vmunix: in stm to start it.
Nov 3 21:06:56 spbe895a vmunix: If the diaglogd daemon is active, use the logtool utility in stm
Nov 3 21:06:56 spbe895a vmunix: to determine which I/O subsystem is logging excessive errors.
What is the best way to determine the error through stm as the server has much I/O devices.
2> other than checking /var/tombstones and syslog and dmesg - where else i good to investigate for errors etc?
Thanks
We have just had a system crash and wanted to know a couple of things:
1> I have checked syslog and the below error displayed:
Nov 3 21:06:56 spbe895a vmunix: DIAGNOSTIC SYSTEM WARNING:
Nov 3 21:06:56 spbe895a vmunix: The diagnostic logging facility has started receiving excessive
Nov 3 21:06:56 spbe895a vmunix: errors from the I/O subsystem. I/O error entries will be lost
Nov 3 21:06:56 spbe895a vmunix: until the cause of the excessive I/O logging is corrected.
Nov 3 21:06:56 spbe895a vmunix: If the diaglogd daemon is not active, use the Daemon Startup command
Nov 3 21:06:56 spbe895a vmunix: in stm to start it.
Nov 3 21:06:56 spbe895a vmunix: If the diaglogd daemon is active, use the logtool utility in stm
Nov 3 21:06:56 spbe895a vmunix: to determine which I/O subsystem is logging excessive errors.
What is the best way to determine the error through stm as the server has much I/O devices.
2> other than checking /var/tombstones and syslog and dmesg - where else i good to investigate for errors etc?
Thanks
hello
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2005 08:24 AM
11-03-2005 08:24 AM
Solution
Hi Lawrenzo,
1.
You can find good information in /var/adm/crash/crash.0 if its first crash, or crash.1 or so.
log a call to HP , they will give a script collection.sh and crashinfo (binary executable file).
Copy the crashinfo in /var/adm/crash/ and run collection.sh and send the tar.gz file to HP. They will say quickly the reason for the crash.
2. Also check /var/opt/resmon/log/event.log file for any error log.
3. Check /etc/shutdownlog
Hope this will help.
Cheers,
Raj.
1.
You can find good information in /var/adm/crash/crash.0 if its first crash, or crash.1 or so.
log a call to HP , they will give a script collection.sh and crashinfo (binary executable file).
Copy the crashinfo in /var/adm/crash/ and run collection.sh and send the tar.gz file to HP. They will say quickly the reason for the crash.
2. Also check /var/opt/resmon/log/event.log file for any error log.
3. Check /etc/shutdownlog
Hope this will help.
Cheers,
Raj.
" If u think u can , If u think u cannot , - You are always Right . "
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2005 08:37 AM
11-03-2005 08:37 AM
Re: system crash
great stuff - just what I was looking for
Thanks
Thanks
hello
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP