cssdagent or cssdmonitor initiated node reboots in HP-UX servers
(Doc ID 1633478.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
HP-UX PA-RISC (64-bit)
Grid Infrastructure node eviction occurs. The cluster alert.log shows that cssdagent and/or cssdmonitor initiated node reboots because they did not get local heartbeats from the ocssd.bin.
The messages in the cluster alert log are like
[ohasd(29566)]CRS-8013:reboot advisory message text: Rebooting after limit 58173 exceeded; disk timeout 58173, network timeout 57822, last heartbeat from CSSD at epoch seconds 1390925745.311, 58204 milliseconds ago based on invariant clock value of 793608130
[ohasd(29566)]CRS-8013:reboot advisory message text: Rebooting after limit 58421 exceeded; disk timeout 57991, network timeout 58421, last heartbeat from CSSD at epoch seconds 1391700830.248, 58497 milliseconds ago based on invariant clock value of 3942103
Other nodes do not report any missing network heartbeat from the node that crashed. The missing network heartbeat messages start only after the problem node is rebooted as missing network heartbeats are expected when the node is down.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document