HP-UX AAA Server A.08.00.01 Administrator's Guide

If the Tomcat server is not running, export the Java path and then use the Tomcat

startup script to start Tomcat, as follows:

# export JAVA_HOME=/opt/java1.4

# /opt/hpws/tomcat/bin/startup.sh

Verify that the Tomcat server is running after running the startup script.

If the Tomcat server is not running, check the Tomcat server logs, /opt/hpws/

tomcat/logs/catalina.out.

5. Use the lsof command to verify that the Tomcat port (usually 8081 for HTTP or

8443 for HTTPS) is in the LISTEN state and is used by the correct process. For

example:

# lsof -i :8081

The port must be in the LISTEN state used by a Java process with the same process

ID as the Tomcat bootstrap process displayed in Step 4.

NOTE: The lsof tool is an open source tool and is not available by default on

HP-UX operating systems.

6. If the problem persists, report it to HP after collecting the information listed in

Chapter 32: “Reporting Problems” (page 504).

Troubleshooting Remote Management Problems

This section describes how to troubleshoot remote management problems. If you are

unable to use the Server Manager to administer an HP-UX AAA Server, complete the

following steps:

1. Verify that the version number of the HP-UX AAA Server is same as that of the

Server Manager administration utility.

2. Verify that the RMI object is running, by entering the following command:

# ps -efx | grep RMIServerManagement | grep -v grep

If the RMI object is running, following is a portion of the output that is displayed:

root 23965 1 0 14:46:47 pts/ta 0:00 /opt/java1.4/bin/IA64N/java

If the RMI service is not displayed, start the RMI object by entering the following

command:

# /opt/aaa/remotecontrol/rmistart.sh

3. Verify that port 2099 is in the LISTEN state and that it is used by the correct process,

by entering the following command:

# lsof -i :2099

Port 2099 must be in the LISTEN state and used by a Java process with the same

PID as the RMI service displayed in Step 2.

Troubleshooting the Server Manager Administration Utility 467