CSSD failing to join cluster :GIPC ssl_Handshake failed to perform operation on handshake with NZERROR
(Doc ID 2851994.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 19.13.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
CSSD is failing to join cluster . it is failing with private Network issue .
alert.log
========
[OCSSD(9814)]CRS-7500: The Oracle Grid Infrastructure process 'ocssd' failed to establish Oracle Grid Interprocess Communication (GIPC) high availability connection with remote node '<node2>'.
[OCSSD(9814)]CRS-1609: This node is unable to communicate with other nodes in the cluster and is going down to preserve cluster integrity; details at (:CSSNM00086:) in <$GRID_BASE>/diag/crs/<NODE1>/crs/trace/ocssd.trc.
[CSSDAGENT(9797)]CRS-5818: Aborted command 'start' for resource 'ora.cssd'. Details at (:CRSAGF00113:) {0:5:3} in <$GRID_BASE>/diag/crs/<NODE1>/crs/trace/ohasd_cssdagent_root.trc.
[OHASD(7341)]CRS-2757: Command 'Start' timed out waiting for response from the resource 'ora.cssd'. Details at (:CRSPE00221:) {0:5:3} in <$GRID_BASE>/diag/crs/<NODE1>/crs/trace/ohasd.trc.
[OCSSD(9814)]CRS-1656: The CSS daemon is terminating due to a fatal error; Details at (:CSSSC00012:) in <$GRID_BASE>/diag/crs/<NODE1>/crs/trace/ocssd.trc
[OCSSD(9814)]CRS-1603: CSSD on node <NODE1> has been shut down.
[OCSSD(9814)]CRS-1609: This node is unable to communicate with other nodes in the cluster and is going down to preserve cluster integrity; details at (:CSSNM00086:) in <$GRID_BASE>/diag/crs/<NODE1>/crs/trace/ocssd.trc.
2022-02-20T05:40:13.110973+00:00
Errors in file <$GRID_BASE>/diag/crs/<NODE1>/crs/trace/ocssd.trc (incident=33):
GIPC.trc
======
2022-02-20 05:28:39.500 :GIPCXCPT:3028412160: gipcmodTlsAuthStart: ssl_Handshake() failed with nzosErr : 28860, ret gipcretTlsErr (49)
Changes
The issue mostly happens when we are rolling back the patches like RHP or Grid zero downtime patching or OOP or downgrading the grid binaries . In all these cases the cluster has to run from old home which causes this issue .
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 |