Operating System - HP-UX
1819803 Members
3172 Online
109607 Solutions
New Discussion юеВ

Re: Sever rebooted automatically

 
Ameena Shaik
Advisor

Sever rebooted automatically

Hi All,

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


5 REPLIES 5
SUDHAKAR_18
Trusted Contributor

Re: Sever rebooted automatically

Hi,

Can you check these files..

/var/adm/syslog/Oldsyslog.log

and

/var/opt/resmon/log/event.log

johnsonpk
Honored Contributor

Re: Sever rebooted automatically

HiAmreena,

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
Ameena Shaik
Advisor

Re: Sever rebooted automatically

Hi All,


I have logged a case with HP Team. Now they are working on it. Any ways Thanks alot.


Regards,

Ameena SK
johnsonpk
Honored Contributor

Re: Sever rebooted automatically

Hi Ameena,

Please share the findings provided by HP here so that it will be helpful for others

Rgds
Johnson
Bill Hassell
Honored Contributor

Re: Sever rebooted automatically

> 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