帮我看看这条syslog

dksgqbj

Mar 13 17:12:33 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 17:12:33 pcg_x_1 EMS [2684]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/adapters/events/TL_adapter/0_4_2_0"     (Threshold:  >= " 3")    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 175898631 -r /adapters/events/TL_adapter/0_4_2_0 -n 175898625 -a
Mar 13 17:13:44 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 17:27:26 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 17:27:51 pcg_x_1  above message repeats 12 times
Mar 13 17:28:32 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 17:47:46 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 17:47:51 pcg_x_1  above message repeats 17 times
Mar 13 17:48:51 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 18:06:52 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 18:07:51 pcg_x_1  above message repeats 16 times
Mar 13 18:07:58 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 18:15:52 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 18:27:51 pcg_x_1  above message repeats 7 times
Mar 13 21:08:03 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 21:27:30 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 21:27:52 pcg_x_1  above message repeats 17 times
Mar 13 21:28:39 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 21:47:42 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 21:47:52 pcg_x_1  above message repeats 17 times
Mar 13 21:48:48 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 22:06:46 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 22:07:52 pcg_x_1  above message repeats 16 times
Mar 13 22:07:57 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.
Mar 13 22:11:22 pcg_x_1 vmunix: 0/4/2/0: Unable to access previously accessed device at nport ID 0x105e8.

Mar 29 12:36:17 pcg_x_1 sshd[6664]: Accepted password for root from 192.168.5.37 port 3402 ssh2
Apr 13 16:56:39 pcg_x_1 EMS [3001]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/system/events/ia64_corehw/core_hw"     (Threshold:  >= " 3")    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 196673538 -r /system/events/ia64_corehw/core_hw -n 196673537 -a
Apr 13 16:56:40 pcg_x_1 EMS [3001]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/system/events/ia64_corehw/core_hw"     (Threshold:  >= " 3")    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 196673538 -r /system/events/ia64_corehw/core_hw -n 196673538 -a
Apr 13 17:18:28 pcg_x_1 EMS [3001]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/system/events/ia64_corehw/core_hw"     (Threshold:  >= " 3")    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 196673538 -r /system/events/ia64_corehw/core_hw -n 196673539 -a
Apr 13 17:18:29 pcg_x_1 EMS [3001]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/system/events/ia64_corehw/core_hw"     (Threshold:  >= " 3")    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 196673538 -r /system/events/ia64_corehw/core_hw -n 196673540 -a

dksgqbj

我想知道。。为什么要执行/opt/resmon/bin/resdata -R 196673538 -r /system/events/ia64_corehw/core_hw -n 196673540 -a

dksgqbj

我执行咯。。。出现下面的内容。。但是我还是看不懂

# /opt/resmon/bin/resdata -R 193921026 -r /system/events/ipmi_fpl/ipmi_fpl -n 193921025 -a

ARCHIVED MONITOR DATA:

Event Time..........: Mon Mar  5 21:17:08 2012
Severity............: CRITICAL
Monitor.............: fpl_em
Event #.............: 4552               
System..............: pcg_x_1

Summary:
     INIT initiated


Description of Error:

This is the equivalent of a TOC event in the PA RISC Architecture. On IPF
systems, this event is called an INIT.
This event can be triggered by the "tc" command from the MP, or from the button
labeled "TOC" or "Transfer of Control" on the Management card or bezel of the
system. There are also other causes of an INIT generated by software.
Data: Local CPU Number

Probable Cause / Recommended Action:


Software has requested an INIT or the INIT button has been pressed.

No action is required.


Additional Event Data:
     System IP Address...: 192.168.5.230
     Event Id............: 0x4f54bcd400000000
     Monitor Version.....: A.01.00
     Event Class.........: System
     Client Configuration File...........:
     /var/stm/config/tools/monitor/default_fpl_em.clcfg
     Client Configuration File Version...: A.01.00
          Qualification criteria met.
               Number of events..: 1
     Associated OS error log entry id(s):
          None
     Additional System Data:
          System Model Number.............: ia64 hp server rx4640
          EMS Version.....................: A.04.20
          STM Version.....................: C.56.00
          System Serial Number............: SGH44382D2
     Latest information on this event:
          http://docs.hp.com/hpux/content/hardware/ems/fpl_em.htm#4552

v-v-v-v-v-v-v-v-v-v-v-v-v    D  E  T  A  I  L  S    v-v-v-v-v-v-v-v-v-v-v-v-v


IPMI event hex: 0xf480007900e01e90 000000000000000000
Time Stamp: Mon Mar  5 11:39:47 2012
Event keyword: INIT_INITIATED
Alert level name: Fatal
Reporting vers: 1
Data field type: Major change in system state
Decoded data field: System State       =   0(Boot Start)
State Change Event =   0(At BIB)
LED Command Valid  =   0(LED state is not updated)
LED Run            =   0(off (default))
LED Attention      =   0(reserved)
LED Stopped        =   0(off (default))
Reporting entity ID: 0 ( Cab 0 Cell 0 CPU 0 )
Reporting entity Full Name: System Firmware
IPMI Event ID : 121 (0x79)
     :TR@

uriyliu_cu

软件要系统重启做dump,可能是硬件故障,也可能是软件故障,需要更多的信息才能判断.

lbseraph

syslog.log看到以下字样的log都是EMS的event，让你执行那个命令是查看详细的内容，或者查看EMS的日志/var/opt/resmon/log/event.log，内容是一样的。

Apr 13 17:18:28 pcg_x_1 EMS [3001]: ------ EMS Event Notification

INIT是有人手动触发（通过INIT按钮或MP里面tc命令）或软件触发的（比如cluster\Oracle RAC等），要查的话先查MP日志看看是否硬件触发的，不是的话就要查/var/adm/crash里面生成的dump了。

dksgqbj

# pwd
/var/adm/crash
# ls -al
total 16
drwxr-xr-x   2 root       root            96 Oct 15  2009 .
drwxr-xr-x  17 adm        adm           8192 Mar  5 21:06 ..


里面没有东西啊

lbseraph

没有生成dump有2种情况，没配置好crash dump或其他原因导致dump没保存下来。