Error Returned When Authenticating to Event Source Manager for Sentinel Log Manager

-The operating system is configured with a bonded network interface (ie. bond0) for physical network card failover
-When attempting to log in to the Event Source Manager (ESM) for Sentinel Log Manager (SLM), the following error is returned:

"The login process timed out. The most likely causes are: 1) Sentinel Server is not fully initialized: Try again later. 2) Sentinel Server is not running: Start Sentinel Server. 3) Misconfiguration: Check that your configuration is set to the correct Sentinel Server."

When this occurs, SLM (specifically Tomcat) may not have properly detected the server's bonded IP address, and ESM is attempting to authenticate to an alternate IP address. This situation can be verified by downloading the ESMWebStart.jnlp file from the SLM Web UI and viewing it's contents with a text editor.

Line 4 of ESMWebStart.jnlp file:
"<jnlp spec="1.0+" codebase="https://192.168.1.1:8443/novellsiemdownloads" href="ESMWebStart.jnlp">"

To work around the issue, the SERVER_IP value in the start_tomcat.sh script must be manually set with the proper IP address for the server.

This issue has been reported to engineering, and will be addressed in a future release of Sentinel Log Manager.