This article has been archived and is no longer maintained by ForgeRock.
The Errors and Replication logs for embedded OpenDJ are no longer available in the $HOME/[openam_instance]/opends/logs directory or are empty. The Access log is still available and populated.
Upgraded to, or installed OpenAM 13.0.
Changes were introduced in OpenDJ 3.0 to make use of SL4J logging (this is the embedded OpenDJ version shipped with OpenAM) and OpenAM was changed to accommodate this. As a result of these changes, content from the Errors and Replication logs for embedded OpenDJ is now included in the OpenAM EmbeddedDJ debug log (located in the $HOME/[openam_instance]/openam/debug directory) when message level is enabled.
OpenDJ messages such as the following default to error level unless OpenAM is set to message level; this means they are not displayed in the EmbeddedDJ log since this maps to message level in the OpenAM logging system:[10/Nov/2016:09:03:51 +1200] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.21 msg=Installation Directory: /Users/jdoe/work/forgerock/opendj [10/Nov/2016:09:03:51 +1200] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.23 msg=Instance Directory: /Users/jdoe/work/forgerock/opendj [10/Nov/2016:09:03:51 +1200] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.17 msg=JVM Information: 1.7.0_80-b15 by Oracle Corporation, 64-bit architecture, 3817865216 bytes heap size [10/Nov/2016:09:03:51 +1200] category=UTIL severity=NOTICE msgID=org.opends.messages.runtime.18 msg=JVM Host: 192.168.42.152, running Mac OS X 10.11.3 x86_64, 17179869184 bytes physical memory size, number of processors available 8
This issue can be resolved by upgrading to OpenAM 13.5 or later; you can download this from BackStage.
The EmbeddedDJ debug log has been renamed OpenDJ-SDK in OpenAM 13.5.
Alternatively, you can increase the debug level to message for the JVM as described in How do I enable message level debugging for install and upgrade issues with AM (All versions)? to include the content from the old Errors and Replication logs in the OpenAM EmbeddedDJ debug log.
Increasing the debug level to message will generate large debug logs, so you are advised to look at log rotation to stop disks filling up: How do I rotate AM 5.x and 6.x debug logs?In OpenAM 13.0, there is a known issue that causes the EmbeddedDJ debug log to grow excessively: OPENAM-8696 (OpenAM 13 EmbeddedDJ log spam ). This is fixed in OpenAM 13.5.