Grid Infrastructure May Reboot Nodes If Information Must Be Printed To The Serial Console
(Doc ID 2295141.1)
Last updated on FEBRUARY 08, 2020
Applies to:Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
The system reboot suddenly. Sometime from lastgasp we can find it is css or cssmoniter rebooted the node because lost interconnection:
Network communication with node hpnplppmdb12 (2) missing for 90% of timeout interval. Removal of this node from cluster in 2.320 seconds
Cluster Synchronization Service daemon (CSSD) clssnmvKillBlockThread_0 not scheduled for 21140 msecs.
In kdump-dmessage or os message file file we can find:
In OSW -- general CPU usage is low but some time we can find system CPU spike.
sysctl -a|grep printk
kernel.printk = 3 4 1 7
and iptables enabled.
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