User Sync
Problem : User sync not getting triggered/failing
Solution Sync fail:
- Check sync user on Author and verify user is valid on publish and able to login with credentials stored
- on Author : Check "Apache Sling Distribution Agent - Sync Agents Factory" and ensure it is enabled.
- If Author not triggering sync job despite having correct configuration
- Possible scheduler stopped or given up after failed attempts
- Restart scheduler / restart instance. (Could over load servers, so ideally disable user sync before restarts and perform controlled sync explained below)
Solution performing controlled Sync :
If users sync been failing for some time there can be huge backlog and could affect servers if complete sync re-enabled. Following instructions to perform controlled sync
Avoid large number of Publishers sync together. Add servers gradually, mix the publish combination to establish cross sync before adding all server back in service.
On Author
- Go to /system/console/configMgr
- Search for "Apache Sling Distribution Agent - Sync Agents Factory"
- Make note of "Exporter" and "Importer" Endpoints
- Keep 1 server in each region and remove rest of the servers
- Increase pull items to 1000.
- Save and wait for sync across servers to complete.
- Repeat process with maximum 2 servers until all servers are in sync
- Once done, add single server at a time to Sync job and let it complete cross sync.
- Once all servers are in sync, reduce Pull Items to 100 or what ever was before start.
Some Useful information.
Disabling User sync on Publish. (Generally not required.)
On Publish instances,
Go to /system/console/configMgr
Search for "Diff Observer Factory"
Uncheck "Enabled" field
Search for Queue Agents Factory
Uncheck enable box
Useful fields in Author
- Sync User details: CryptoDistributionTransportSecretProvider.name
- Sync Schedule (Should not be 30Sec due to bug) : DistributionTransportSecretProvider
- Transport Configuration : Apache Sling Distribution Agent - Sync Agents Factory