LDAPSync log files

Use the LDAPSync log files to troubleshoot the synchronization operations.

The LDAPSync solution creates a set of log files in the LDAPSync/logs folder and displays console messages during operation. Other log files are created when an exception occurs. For example, if members of a group cannot be found in the target or broken references to group members are encountered, the messages are written to the GroupMembersMissing.log file.

System log files

System log files are written by the IBM® Security Verify Directory Integrator. These files are in the sdi_solution_dirlogs folder.

ibmdi.log: Contains all messages that the IBM Security Verify Directory Integrator AssemblyLines write to their own solution logs and server-level messages.
ibmditk.log: Contains log entries that are produced by the IBM Security Verify Directory Integrator development environment, which is the Configuration Editor.

Solution log files

Solution logs are written by AssemblyLines and are part of the design of a solution.

The LDAPSync solution writes its log files in the sdi_solution_dir/LDAPSync/logs folder. When you run an AssemblyLine, such as LDAPMigrate or LDAPSync, a log file with the same name as the AssemblyLine is created.

The LDAPSync solution creates the following log files:

EntriesNotMigrated.ldif: Contains entries that were not successfully written to the target during a migration.; Previous versions of this file are renamed to EntriesNotMigrated.old.timestamp.ldif, where timestamp is the date and time that file was modified.; The name of this log starts with the flow ID and an underscore character. If no flows are defined, then M_ precedes the file name.
EntriesNotSynchronized.ldif: Contains entries that were not successfully written to the target during synchronization.; Previous versions of this file are renamed to EntriesNotSychronized.old.timestamp.ldif, where timestamp is the date and time that file was modified.; The name of this log starts with the flow ID and an underscore character. If no flows are defined, then S_ precedes the file name.
GroupMembersMissing.log: Contains the list of group members that were not skipped during migration or synchronization. The member attribute of a group entry contains a list of DNs. Each attribute refers to either a person or a group entry for that member. If a referenced entry is not in the target directory, then it is skipped, and the DN is logged to this file.; Previous versions of this log are renamed to GroupMembersMissing.old.timestamp.log, where timestamp is the date and time that file was modified.; The name of this log starts with the flow ID and an underscore character. If no flows are defined, then M_ precedes the file name for logs that are created during migration, and S_ precedes the file name for logs that are created during synchronization.
LDAPMigrate: Contains messages that come from the flow, each time that LDAPMigrate is run. Another log file is also written for each flow that is run, with the flow ID prefixed to the file name, for example SunFlow_LDAPMigrate.; This log contains messages that come from only the specified flow, while the LDAPMigrate.log includes messages from all flows. If containers are migrated, then MigrateContainers.log is also created. If person or group entries are processed, then MigrateUsers.log and MigrateGroups.log are also written.; Previous versions of this log are renamed by using a counter. The maximum counter value is specified by the global.maxLogFiles property.
LDAPSync: Contains messages that come from the flow, each time that LDAPSync is run. Another log file is also written for each flow that is run, with the flow ID prefixed to the file name, for example SunFlow_LDAPSync.; This log contains messages that come from only the specified flow, while the LDAPSync.log includes messages from all flows. In addition, a WriteToLDAP.log file is also created.; Previous versions of this log are renamed by using a counter. The maximum counter value is specified by the global.maxLogFiles property.
MigrateContainers.log: Contains messages that are logged when containers are migrated. If you run LDAPMigrate and container entries are processed, then this log file is created. A WriteToLDAP.log file also is created.; The name of this log starts with the flow ID and an underscore character. If no flows are defined, then M_ precedes the file name.; Previous versions of this log are renamed by using a counter. The maximum counter value is specified by the global.maxLogFiles property.
MigrateUsers.log: Contains messages that are logged when person (user) entries are migrated. If you run LDAPMigrate and person entries are processed, then this log file is created. A WriteToLDAP.log file also is created.; The name of this log starts with the flow ID and an underscore character. If no flows are defined, then M_ precedes the file name.; Previous versions of this log are renamed by using a counter. The maximum counter value is specified by the global.maxLogFiles property.
MigrateGroups.log: Contains messages that are logged when group entries are migrated. If you run LDAPMigrate and group entries are processed, then this log file is created. A WriteToLDAP.log file also is created.; The name of this log starts with the flow ID and an underscore character. If no flows are defined, then M_ precedes the file name.; Previous versions of this log are renamed by using a counter. The maximum counter value is specified by the global.maxLogFiles property.
ResetChangeState: Contains a log of when the change state information is reset. This log file is created when ResetChangeState is run.; The name of this log starts with the flow ID and an underscore character. If no flows are defined, then M_ precedes the file name.
TestConnections.log: Contains the results of verification of connection settings. This log file is written whenever TestConnections is run.; Previous versions of this log are renamed by using a counter. The maximum counter value is specified by the global.maxLogFiles property.
WriteToLDAP.log: Logs all operations that update the target directory. It is written when AssemblyLines like LDAPMigrate and LDAPSync are run.; Previous versions of this log are renamed by using a counter. The maximum counter value is specified by the global.maxLogFiles property.; The name of this log starts with the flow ID and an underscore character. If no flows are defined, then M_ precedes the file name for logs that are created during migration and S_ precedes the file name for logs that are created during synchronization.