The HP-UNIX system goes down

HP-UNIX system downtime in the morning when db routine inspection found a node 2 down. First, check the alter of Checkpoint 2. no discovery is found, and the crs resources are in offline status. it can be determined that the system is down and there is no record. Www.2cto.com...
HP-UNIX system downtime in the morning when db routine inspection found a node 2 down. First, check the alter of Checkpoint 2 without any discovery, and the crs resources are in offline status.
Because the system is down, there is no record. Www.2cto.com: # last | grep Decroot pts/1 Mon Dec 17 still logged inroot pts/0 Mon Dec 17 still logged inreboot system boot Sun Dec 16 still logged inreboot system boot Sat Dec 15) but I just don't know if the system will record the information here, and check 3rd records, and still logged in this
It can only be handed over to HP engineers. Check/etc/shutdownlog and find the following new: 00: 03 Sun Dec 16 2012. reboot after panic: MCA, IIP: 0xe0000000008a1a40 IFA: 0xc000000006dae00008: 18 Sun Dec 16 2012. reboot after panic: MCA, IIP: 0xe000000000d0000a0 IFA: 0x20000000777db0cc www.2cto.com check the alter log of node 1 and find the following information: sat Dec 15 23:55:30 2012 Errors in file/opt/oracle/product/admin/xxx/udump/xxxw.ora_4074.trc: Sat Dec 15 23:55:31 2012 Errors in file/opt/oracle/product/admin /Xxx/udump/xxx1_ora_4074.trc: Sat Dec 15 23:55:34 2012 Reconfiguration started (old inc 100, new inc 102) List of nodes: 0 check crs log as follows: 23:55:16. 183 [cssd (4229)] CRS-1612: node xxx2 (0) at 50% heartbeat fatal, eviction in 0.000 seconds2012-12-15 23:55:23. 183 [cssd (4229)] CRS-1611: node xxx2 (0) at 75% heartbeat fatal, eviction in 0.000 seconds2012-12-15 23:55:24. 181 [cssd (4229)] CRS-1611: node xxx2 (0) At 75% heartbeat fatal, eviction in 0.000 seconds2012-12-15 23:55:28. 183 [cssd (4229)] CRS-1610: node xxx2 (0) at 90% heartbeat fatal, eviction in 0.000 seconds2012-12-15 23:55:29. 180 [cssd (4229)] CRS-1610: node xxx2 (0) at 90% heartbeat fatal, eviction in 0.000 seconds2012-12-15 23:55:30. 183 [cssd (4229)] CRS-1610: node xxx2 (0) at 90% heartbeat fatal, eviction in 0.000 seconds2012-12-15 23:55:30. 682 [cssd (4229)] CRS-1607: CSSD evicting node xxx2. Details in/opt/oracle/product/crs/log/xxx1/cssd/ocssd. log. [cssd (4229)] CRS-1601: CSSD Reconfiguration complete. active nodes are xxx1. check the cssd log as follows: [CSSD] 23:55:16. 183 [18]> WARNING: clssnmPollingThread: node xxx2 (2) at 50 2.000000e + 00 artbeat fatal, eviction in 14.489 seconds [CSSD] 23:55:16. 183 [18]> TRACE: clssnmPollingThread: node xxx 2 (2) is impending reconfig, flag 1037, misstime 15511 [CSSD] 23:55:16. 183 [18]> TRACE: clssnmPollingThread: diskTimeout set to (27000) MS impending reconfig status (1) [CSSD] 23:55:23. 183 [18]> WARNING: clssnmPollingThread: node xxx2 (2) at 75 2.000000e + 00 artbeat fatal, eviction in 7.489 seconds [CSSD] 23:55:24. 181 [18]> WARNING: clssnmPollingThread: node xxx2 (2) at 7 5 2.20.00e + 00 artbeat fatal, eviction in 6.490 seconds [CSSD] 23:55:28. 183 [18]> WARNING: clssnmPollingThread: node xxx2 (2) at 90 2.000000e + 00 artbeat fatal, eviction in 2.489 seconds [CSSD] 23:55:29. 180 [18]> WARNING: clssnmPollingThread: node xxx2 (2) at 90 2.000000e + 00 artbeat fatal, eviction in 1.491 seconds [CSSD] 23:55:30. 183 [18]> WARNING: clssnmPollingThread: n Ode xxx2 (2) at 90 2.000000e + 00 artbeat fatal, eviction in 0.489 seconds, you can know that node 2 is re-configuring the cluster at this time point, removing node 2 from the cluster. After the storage is active, the cluster automatically starts at node 2 and resumes normal production. Through/var/adm/syslog. the log and old logs show that the node system has restarted. The strange thing is that there is no log information before the restart, you can only package the system crash information in the/var/adm/crash Directory (you can check it using the q4 crash file) to HP support staff. -The End-