Troubleshooting
Use the following event log and trace file to troubleshoot IBM® Verify Bridge for Directory Sync.
Windows™ Event Log
When an error occurs, it is logged in the Windows Event Log. Use this initial method for problem determination.
For IBM Directory Server only. The
changelog number and timestamp is added to relevant Windows events of failed Cloud
Directory operations so the changelog entries can be examined.
The op_log directory
This directory contains zero or more files in a comma-separated value format. It lists the modifications that were applied to users and groups in the Cloud Directory as they are synchronized from Active Directory.
For IBM Directory Server only. The
changelog number and timestamp is embedded at the start of the DN entry in the
op_log CSV file. This action allows monitoring tools to determine which
changelog entries Directory Sync processed and how far it is behind the most recent
LDAP changelog entry.
<UTC Date>,<Operation>,<Active Dir DN>,<Cloud Directory ID>,<Status>Example
entries might look
like:"Thu Sep 19 21:07:20 2019","PATCH","CN=testgroup,CN=Users,DC=home2,DC=com","650004ZZHI","RequestError"
"Fri Sep 20 20:07:39 2019","DELETE","CN=testgroup 0ADEL:c2d9a7a5-96b4-4e40-bffc-3066831ca06b,CN=Deleted Objects,DC=home2,DC=com","650004ZZHI","204"
"Fri Sep 20 20:16:16 2019","POST","CN=testgroup,CN=Users,DC=home2,DC=com","65000503CA","201"The cloud-bridge trace file
The IcbLdapSync.json configuration file provides the option “trace-file” that when set outputs a detailed trace on all the operations that occur in the IcbLdapSync.exe process. Set this option and restart the process to obtain detailed information on issues that might be occurring. After the issue is fixed, ensure that this option is disabled. Depending on the amount of activity that occurs in the Active Directory server, it can quickly generate a large file.