root.sh Fails to Start ora.cssd due to Inconsistent Jumbo Frames Setting
(Doc ID 1085638.1)
Last updated on DECEMBER 31, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database 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
Information in this document applies to any platform.
Symptoms
While installing Oracle Clusterware or Oracle Grid Infrastructure, running root.sh on second node (or other than first node) fails.
CSSD is first started in exclusive mode and then recognizes that CSSD is running on the first node and so it is then started in clustered mode.
After 10 minutes, the startup attempt is aborted waiting on an answer from node 1.
The output of root.sh or the rootcrs_node.log shows:
2010-04-09 11:35:34: Start of resource "ora.gpnpd -init" Succeeded
2010-04-09 11:35:34: Successfully started requested Oracle stack daemons
2010-04-09 11:35:34: Starting CSS in clustered mode
2010-04-09 11:45:53: CRS-2672: Attempting to start 'ora.cssdmonitor' on '<HOSTNAME2>'
2010-04-09 11:45:53: CRS-2676: Start of 'ora.cssdmonitor' on '<HOSTNAME2>' succeeded
2010-04-09 11:45:53: CRS-2672: Attempting to start 'ora.cssd' on '<HOSTNAME2>'
2010-04-09 11:45:53: CRS-2672: Attempting to start 'ora.diskmon' on '<HOSTNAME2>'
2010-04-09 11:45:53: CRS-2676: Start of 'ora.diskmon' on '<HOSTNAME2>' succeeded
2010-04-09 11:45:53: CRS-2674: Start of 'ora.cssd' on '<HOSTNAME2>' failed
2010-04-09 11:45:53: CRS-2679: Attempting to clean 'ora.cssd' on '<HOSTNAME2>'
2010-04-09 11:45:53: CRS-2681: Clean of 'ora.cssd' on '<HOSTNAME2>' succeeded
2010-04-09 11:45:53: CRS-2673: Attempting to stop 'ora.diskmon' on '<HOSTNAME2>'
2010-04-09 11:45:53: CRS-2677: Stop of 'ora.diskmon' on '<HOSTNAME2>' succeeded
2010-04-09 11:45:53: CRS-4000: Command Start failed, or completed with errors
2010-04-09 11:35:34: Successfully started requested Oracle stack daemons
2010-04-09 11:35:34: Starting CSS in clustered mode
2010-04-09 11:45:53: CRS-2672: Attempting to start 'ora.cssdmonitor' on '<HOSTNAME2>'
2010-04-09 11:45:53: CRS-2676: Start of 'ora.cssdmonitor' on '<HOSTNAME2>' succeeded
2010-04-09 11:45:53: CRS-2672: Attempting to start 'ora.cssd' on '<HOSTNAME2>'
2010-04-09 11:45:53: CRS-2672: Attempting to start 'ora.diskmon' on '<HOSTNAME2>'
2010-04-09 11:45:53: CRS-2676: Start of 'ora.diskmon' on '<HOSTNAME2>' succeeded
2010-04-09 11:45:53: CRS-2674: Start of 'ora.cssd' on '<HOSTNAME2>' failed
2010-04-09 11:45:53: CRS-2679: Attempting to clean 'ora.cssd' on '<HOSTNAME2>'
2010-04-09 11:45:53: CRS-2681: Clean of 'ora.cssd' on '<HOSTNAME2>' succeeded
2010-04-09 11:45:53: CRS-2673: Attempting to stop 'ora.diskmon' on '<HOSTNAME2>'
2010-04-09 11:45:53: CRS-2677: Stop of 'ora.diskmon' on '<HOSTNAME2>' succeeded
2010-04-09 11:45:53: CRS-4000: Command Start failed, or completed with errors
Clusterware alert.log reports communication failure messages:
$GRID_HOME/log/<node>/alert<node>.log
[cssd (32521)] CRS-1636: The CSS daemon (cssd) was started in exclusive mode, but a demon CSS (CSSD) has been detected on active node oweb-b6-h. Current interruption; level details (: CSSNM00006 :) in / u01/oracle/grid/11.2.0.3/log/oweb-b7-h/cssd/ocssd.log
2010-04-09 11:35:52.851
[cssd (32829)] CRS-1612: Network communication with the node oweb-b6-h (1) is missing for 50% of the timeout interval. Remove this node in the cluster 14,890 seconds
2010-04-09 11:35:53.454
[cssd (32829)] CRS-1611: Network communication with the node oweb-b6-h (1) is missing for 75% of the timeout interval. Remove this node in the cluster 6880 seconds
2010-04-09 11:35:54.458
[cssd (32829)] CRS-1610: Network communication with the node oweb-b6-h (1) is missing for 90% of the timeout interval. Remove this node in the cluster 2880 seconds
2010-04-09 11:35:52.851
[cssd (32829)] CRS-1612: Network communication with the node oweb-b6-h (1) is missing for 50% of the timeout interval. Remove this node in the cluster 14,890 seconds
2010-04-09 11:35:53.454
[cssd (32829)] CRS-1611: Network communication with the node oweb-b6-h (1) is missing for 75% of the timeout interval. Remove this node in the cluster 6880 seconds
2010-04-09 11:35:54.458
[cssd (32829)] CRS-1610: Network communication with the node oweb-b6-h (1) is missing for 90% of the timeout interval. Remove this node in the cluster 2880 seconds
Changes
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 |