My Oracle Support Banner

CSSD Agent Reboots the Node After CRS-1690: The CRS Home File System is not Responsive (Doc ID 2639784.1)

Last updated on MAY 15, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 19.1.0.0.0 to 19.6.0.0.0 [Release 19]
Information in this document applies to any platform.

Symptoms

CSSD agent reboots the node after seeing that CRS Home file system is not accessible. Following messages report in Clusterware alert log of the node going down

020-01-22 11:55:01.011 [CSSDAGENT(30438)]CRS-1690: The CRS home file system is not responsive. If this persists, a reboot occurs in 29550 milliseconds; details are at (:CLSN00111:) in <ORACLE_BASE>/diag/crs/<HOSTNAME1>/crs/trace/ohasd_cssdagent_root.trc.
2020-01-22 11:55:16.013 [CSSDAGENT(30438)]CRS-1690: The CRS home file system is not responsive. If this persists, a reboot occurs in 14550 milliseconds; details are at (:CLSN00111:) in <ORACLE_BASE>/diag/crs/<HOSTNAME1>/crs/trace/ohasd_cssdagent_root.trc.

Working node clusterware alert log report following Reboot Advisory messages:

2020-01-22 11:55:31.016 [OHASD(16515)]CRS-8011: reboot advisory message from host: <HOSTNAME1>, component: cssagent, with time stamp: L-2020-01-22-11:55:31.016
2020-01-22 11:55:31.017 [OHASD(16515)]CRS-8013: reboot advisory message text: oracssdagent is rebooting this node because the file system for path <19c GRID_HOME>/log/<HOSTNAME1> did not respond in 60460 milliseconds.
2020-01-22 11:55:33.587 [OCSSD(29631)]CRS-1632: Node <HOSTNAME1> is being removed from the cluster in cluster incarnation 423325599 

Changes

File system full on the Cluster node 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.