Grid Infrastructure May Reboot Nodes If Information Must Be Printed To The Serial Console (Doc ID 2295141.1)

Last updated on SEPTEMBER 29, 2017

Applies to:

Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

 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.

Changes

 sysctl -a|grep printk
kernel.printk = 3 4 1 7

and iptables enabled.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms