CRSD Not Starting With Exception: GroupEntry constructor failed to validate group name with error

(Doc ID 2293349.1)

Last updated on AUGUST 15, 2017

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.


After restarting clusterware on node 1, ora.crsd resource is not starting.

The crsd.log on the node shows below messages repeatedly for each database resource:

2017-08-02 18:46:18.631721 : AGFW:2231269120: {1:32872:2} Creating the resource: ora.orcl.db 1 1
2017-08-02 18:46:18.632456 : AGFW:2231269120: {1:32872:2} Initializing the resource ora.orcl.db 1 1 for type ora.database.type
2017-08-02 18:46:18.632518 : AGFW:2231269120: {1:32872:2} SR: acl = owner:oracle:rwx,pgrp:oinstall:r--,other::r--,group:dba:r-x,group:racoper:r-x,user:oracle:r-x
2017-08-02 18:46:18.632670 : CRSSEC:2231269120: {1:32872:2} Exception: GroupEntry constructor failed to validate group name with error: 1 groupId: 0x7f4b2411c270 acl_string: group:racoper:r-x

The key error above is  "failed to validate group name" followed by the name of the group.

Shortly after above errors, crsd.bin aborts with the following message:


2017-08-02 18:46:18.646208 : AGFW:2231269120: {1:32872:2} 1 1 marked as deleted.
CLSB:2231269120: Oracle Clusterware infrastructure error in CRSD (OS PID 46621): Fatal signal 11 has occurred in program crsd thread 2231269120; nested signal count is 1



racoper group was removed from /etc/group on problem node


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