HP RP4530无故自动重启，间隔短则十几分钟，长则七八小时

mrtangy

Log Entry #   1 :
SYSTEM NAME: Zig2
DATE: 04/15/2015 TIME: 01:13:55
ALERT LEVEL: 13 = System hang detected via timer popping

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general   SOURCE ID: 0
PROBLEM DETAIL: 4 = timeout

CALLER ACTIVITY: F = display_activity() update   STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX   REPORTING ENTITY ID: 00

0x78E000D41100F000 00000003 00000001 type 15 = Activity Level/Timeout
0x58E008D41100F000 00007303 0F010D37 type 11 = Timestamp 04/15/2015 01:13:55
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry #   2 :
SYSTEM NAME: Zig2
DATE: 04/12/2015 TIME: 22:31:52
ALERT LEVEL: 13 = System hang detected via timer popping

SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general   SOURCE ID: 0
PROBLEM DETAIL: 4 = timeout

CALLER ACTIVITY: F = display_activity() update   STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX   REPORTING ENTITY ID: 00

0x78E000D41100F000 00000003 00000000 type 15 = Activity Level/Timeout
0x58E008D41100F000 00007303 0C161F34 type 11 = Timestamp 04/12/2015 22:31:52
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry #   3 :
SYSTEM NAME: Zig2
DATE: 04/12/2015 TIME: 22:12:42
ALERT LEVEL: 3 = System blocked waiting for operator input

SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated   SOURCE ID: 0
PROBLEM DETAIL: F = unexpected

CALLER ACTIVITY: 0 = unspecified   STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware   REPORTING ENTITY ID: 00

0x0000003F00000000 00000000 00000000 type  0 = Data Field Unused
0x5800083F00000000 00007303 0C160C2A type 11 = Timestamp 04/12/2015 22:12:42
Type CR for next entry, - CR for previous entry, Q CR to quit.



Log Entry #   4 :
SYSTEM NAME: Zig2
DATE: 04/12/2015 TIME: 22:12:40
ALERT LEVEL: 3 = System blocked waiting for operator input

SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated   SOURCE ID: 0
PROBLEM DETAIL: F = unexpected

CALLER ACTIVITY: 0 = unspecified   STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware   REPORTING ENTITY ID: 00

0x0000003F00000000 00000000 00000000 type  0 = Data Field Unused
0x5800083F00000000 00007303 0C160C28 type 11 = Timestamp 04/12/2015 22:12:40
Type CR for next entry, - CR for previous entry, Q CR to quit.

lbseraph

回复 1# mrtangy

主机重启的时候外部网络、机房温度是否异常？最好先看一下有没有crash dump生成出来，有的话要找HP分析一下原因（硬件没问题的话得查是什么导致kernel panic）。

参考：
http://h30499.www3.hp.com/t5/HP- ... 972010#.VTB0fPmUdOs
   

tangye

rp5430

我以前遇到过散热不佳导致重启的

mrtangy

但是两台在同一柜，另一台则无，而且应该不是温度过高所至，没有问题的报警，且风扇都是正常的。回复 3# tangye


   

cjhvslhb

1) Alert level 13 itself indicates GSP detected a system hang (System heart
beat timeout) and you can analyze TOC crash dump to determine the cause of
system hang if you need.
2) If the system is configured in the MC/SG clusters, system hang or lan
problem also causes that secondary cluster issues a TOC to switch the cluster.
In this case you need to check out the OLDsyslog (both systems) and cmcld log.