Trying to configure a new Gateway with a new Synchronization group and getting an error when running an ldap sync:
LDAPSync 0 0 0 "actor=LDAPSyncService,text=<< \" {\"_status\":{\"statusCode\":24635\,\"statusMessage\":\"Resource limit reached.\"}\,\"keyValuePairs\": [{\"keyValuePair\":{\"key\":\"EG-93698eb0-e043-11e9-93f3- cb14f9240108\"\,\"value\":\"Waiting###1569567900###10.36.0.4###VIP_EG_CAN\"}}]}\",op=Synchronization"
SPLUNK logs show the same: [2019-09-27 09:00:30.439][INFO][TID:vipusEF9A7D6F5DAEA488][RID:cea0546a5f82f3a53213d324899ae6ff] [OP:KeyValuePairs][IP:x.x.x.x][PORT:][JH:xxxxxxx] [REQUEST_ID:EG_984_IP_10_36_0_4_SID_xxxxxx] Max allowed [25] key-value pair count reached.
The VIP Service supports a combined maximum of 24 Enterprise Gateway LDAP Synchronization instances from the same JHash.
25 exceeds the maximum allowed instances.
To remove the dead Sync Groups, access the VIP Enterprise Gateway console on the new server and go to Settings>System Settings and assign the dead sync group to the new Gateway. Restart the Ldap DirSync Service, then change the Synchronization Cluster back to the new name you wish to use and restart the Ldap DirSync Service again. This assigns the dead cluster name to that VIP EG, then removed is when that same VIP EG changes the name to something else.