VIP Enterprise LDAP sync error: Current sync time conflicting with instance. Instance not synching

Products

• VIP Service

Issue/Introduction

VIP LDAP synchronization failing with the following warnings:

WARN  "2023-11-26 11:45:19.669 GMT+0300" 10.10.10.10 LDAPSync 0 0 0  "actor=LDAPSyncService,op=Synchronization,text=[SyncInstanceManager:createInstanceInfo] Current sync time conflicting with instance EG-11e5-8231-3bba72d997af1. Updating instance state to: Sleeping"
...
WARN  "2023-11-26 11:45:19.669 GMT+0300" 10.10.10.10 LDAPSync 0 0 0  "actor=LDAPSyncService,op=Synchronization,text=[LDAPSyncMgr] <<WARNING>> Instance not synching."

Cause

When an LDAP sync service is initially configured, a unique instanceId is assigned to that particular VIP Enterprise Gateway server by the VIP Cloud (and to each VIP Enterprise Gateway LDAP sync instance within your environment on the same JHash). When a scheduled LDAP sync job begins, the VIP Cloud will prevent the job from completing if it detects the frequency (start) time for that instanceId is within 4 hours of another instanceId. This is to prevent simultaneous synchronizations from trampling on each other.

(note: Each instanceId, status, and corresponding IP address reported from the VIP Cloud can be seen in the LDAP sync logs.)

Resolution

Configure the Frequency values for each VIP Enterprise Gateway in your environment to be 4 hours apart.