How To
ForgeRock Identity Platform
Does not apply to Identity Cloud

How do I find network errors in the logs for the configuration store in AM (All versions)?

Last updated Apr 13, 2021

The purpose of this article is to provide information on finding network errors in the logs for the configuration store in AM. This is useful if you suspect network errors are causing connection issues with the configuration store.


1 reader recommends this article

Finding network errors (AM 7 and later)

AM 7 uses Logback for configuration of debug logging. 

You can enable message level debugging for all logs as described in Maintenance Guide › Debug Logging or you can just set it for the Configuration appender as described in Maintenance Guide › To Temporarily Enable Debug Logging with Logback.jsp.

Finding network errors (Pre-AM 7)

The Configuration debug log shows network errors when the debug level is set to Warning or Message (default is Error). You can set this debug level for all logs as described in How do I enable Message level debugging in AM (All versions) debug files? or you can just set it for the amEventService instance as follows: 

  1. Log into AM as the admin user (called amadmin by default).
  2. Navigate to: <protocol>://host.fqdn:port/openam/Debug.jsp, for example: http://host1.example.com:8080/openam/Debug.jsp.
  3. Select amEventService from the Debug Instances field.
  4. Select Warning or Message from the Level field and click Submit to change the debug level.
Note

The Debug.jsp page always shows the debug level as Error, regardless of its actual setting.

If you have network based errors, you will see errors such as the following in your Configuration log (located in the /path/to/openAM/debug directory by default):

amEventService WARNING: EventService.run() LDAPException received:  com.sun.identity.ldap.LDAPException: Server or Network error (81) at com.sun.identity.shared.ldap.LDAPConnThread.networkError(LDAPConnThread.java:910) at com sun.identity.shared.ldap.LDAPConnThread.networkError(LDAPConnThread.java:895) at com.sun.identity.shared.ldap.LDAPConnThread.run(LDAPConnThread.java:676) at java.lang.Thread.run(Thread.java:745) ...

Once you have reproduced the problem and captured the debug logs, you should revert the debug level to Error to avoid filling up the disks where the debug logs are stored.

See Also

Attempting to access AM (All versions) fails with ConfigurationException: Configuration store is not available

How do I check if AM (All versions) is up and running?

How do I record troubleshooting information in AM (All versions)?

Related Training

N/A

Related Issue Tracker IDs

N/A


Copyright and Trademarks Copyright © 2021 ForgeRock, all rights reserved.