CRS-01717
The CSS daemon has detected a voting file add during startup and is waiting for the add to complete; Details at string in string
Cause
A voting file add started on another node is in progress while this CSS daemon is starting. To avoid the potential for data corruption, the CSS daemon on this node must wait for the add to complete.
Action
This is normally a temporary condition that is automatically resolved. If the clusterware stack cannot start on any node, this condition may be corrected by starting the clusterware stack in exclusive mode using 'crsctl start crs -excl' followed by 'crsctl stop crs' on one node. This will automatically correct the condition and the clusterware can be started normally on all nodes.
CRS-01717
The CSS daemon has detected a voting file add during startup and is waiting for the add to complete; Details at string in string
Cause
A voting file add started on another node is in progress while this CSS daemon is starting. To avoid the potential for data corruption, the CSS daemon on this node must wait for the add to complete.
Action
This is normally a temporary condition that is automatically resolved. If the clusterware stack cannot start on any node, this condition may be corrected by starting the clusterware stack in exclusive mode using 'crsctl start crs -excl' followed by 'crsctl stop crs' on one node. This will automatically correct the condition and the clusterware can be started normally on all nodes.
CRS-01717
The CSS daemon has detected a voting file add during startup and is waiting for the add to complete; Details at string in string
Cause
A voting file add started on another node is in progress while this CSS daemon is starting. To avoid the potential for data corruption, the CSS daemon on this node must wait for the add to complete.
Action
This is normally a temporary condition that is automatically resolved. If the clusterware stack cannot start on any node, this condition may be corrected by starting the clusterware stack in exclusive mode using 'crsctl start crs -excl' followed by 'crsctl stop crs' on one node. This will automatically correct the condition and the clusterware can be started normally on all nodes.
