Applies to:

Oracle Directory Server Enterprise Edition - Version 5.2 SP6 and laterInformation in this document applies to any platform.

Symptoms

As this is a crash issue the last lines of the access log that would show the SASL bind are within the core file, and would therefore not show in the access log file.

If the Directory Server crashes but no core file is produced, you may need to change the coreadm settings on your operating system to allow core dumps. You also need to provide enough disk space for the core file. For help on coreadm settings, please see this document "Configuring the Operating System to Generate Core Files" which is part of the Gathering Debug Data for Directory Server documentation.

You can then use a crash enabled Dirtracer (Doc ID 1291443.1) or pkgapp (Doc ID 1274584.1) script to capture the core data. From this data there will be a pstack, grep in the pstack for a line that comes from the crashing thread.

For this problem, DS 5.2 crashes and generates a core file with the following stack trace: