- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Sever rebooted automatically
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
Discussions
Discussions
Discussions
Forums
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
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
тАО05-31-2009 10:18 PM
тАО05-31-2009 10:18 PM
Sever rebooted automatically
I need ur help. One of the Servers(Itanium Server) has got rebooted suddenly. I got the following error message. Server model is rx6600
Log Entry 154: 01 Jun 2009 06:11:15
Alert Level 3: Warning
Keyword: OS_MCA_NOT_REGISTERED
OS MCA address not registered
Logged by: System Firmware 0
Data: Implementation dependent data field
0x7680010700E00EA0 0000000000000000
Log Entry 153: 01 Jun 2009 06:11:14
Alert Level 3: Warning
Keyword: IO_PCI_PERR
PCI parity error detected.
Logged by: System Firmware 0
Data: Location - I/O Device (Local Bus Adapter): LBA 6
0x6480026900E00E80 FFFFFFFFFF06FF83
Please advise me on this issue
Regards,
Ameena SK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-31-2009 11:12 PM
тАО05-31-2009 11:12 PM
Re: Sever rebooted automatically
Can you check these files..
/var/adm/syslog/Oldsyslog.log
and
/var/opt/resmon/log/event.log
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-31-2009 11:14 PM
тАО05-31-2009 11:14 PM
Re: Sever rebooted automatically
It seems one of you PCI Card having issues,If you have a support contract with HP,Send the MP logs to HP and they can pin point the exact problem
Rgds
Johnson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-31-2009 11:23 PM
тАО05-31-2009 11:23 PM
Re: Sever rebooted automatically
I have logged a case with HP Team. Now they are working on it. Any ways Thanks alot.
Regards,
Ameena SK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2009 01:33 AM
тАО06-01-2009 01:33 AM
Re: Sever rebooted automatically
Please share the findings provided by HP here so that it will be helpful for others
Rgds
Johnson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2009 09:06 AM
тАО06-01-2009 09:06 AM
Re: Sever rebooted automatically
This means that the server crashed or had a panic condition. In this case, the crash condition appears to be related to a bad PCI I/O card. Generally, there will be nothing in syslog when there is a crash. The system halts and performs a crash dump in the /var/adm/crash directory (unless prohibited by savecrash settings). The primary file to look at after a panic is /etc/shutdownlog, then have the crash dump analyzed.
Bill Hassell, sysadmin