HTTP 500 Errors

If you receive an internal server error or servlet container error (either unavailable or being upgraded), iManager is having problems with Tomcat:

Wait a few minutes and try again to access iManager. If you still receive the same errors, you need to verify the status of Tomcat and if the error persists, the status of Apache.


Checking the Status of Tomcat

  1. Restart Tomcat.

  2. Check the Tomcat logs for any errors.

    The log file is located in the $TOMCAT_HOME$/logs directory on the Unix/Linux and Windows platforms. On Unix/Linux, the logs are named catalina.out or localhost_log.<date>.txt, and on Windows, the log files are named stderr and stdout.

    On NetWare, any errors are sent to the logger screen.


Checking the Status of Apache

  1. Restart Apache.

  2. Check the Apache log files for errors.

    The files are located in the $APACHE_HOME$/logs directory.