HP-UX AAA Server A.08.02.10 Administrator's Guide HP-UX 11i v3 (T1428-90093, November 2013)

Table 98 Common Problems with the Server Manager (continued)
SolutionCauseProblem
Address’ do not correspond to the
same host. HP-UX AAA Server
Using HP-UX AAA Server Manager”
(page 200)
Manager has not validated theses
values because the RMI object was
not running when the server was
configured.
Error while parsing the group
configuration file.
Can launch the Server Manager, but
get ‘Parse Error’ in the HP-UX AAA
Server Status Frame.
1. Stop the HP-UX AAA Server
Manager and Tomcat.
2. Stop the RMI Objects running on all
the remote hosts.
3. Start the Tomcat and HP-UX AAA
Server Manager.
4. Start the RMI Objects on all the
remote hosts.
5. Modify all the Servers configured.
For more information, see
“Administering HP-UX AAA Servers
Using HP-UX AAA Server Manager”
(page 200).
Troubleshooting Server Manager Launch Problems
This section describes how to troubleshoot problems when you cannot launch the Server Manager
administration utility.
If you are unable to launch the Server Manager, complete the following steps:
1. Verify that you are using a supported browser. For a list of supported browsers, see HP-UX
AAA Server A.08.02.10 Release Notes at http:// www.hp.com/go/hpux-security-docs .
(Select HP-UX AAA Server (RADIUS) Software.)
2. Verify the port number specified in the URL. The default port number is 8081 (HTTP) or 8443
(HTTPS). This is configured in Tomcat’s /opt/hpws22/tomcat/conf/server.xml file. If
secure communication (HTTPS) is used, ensure that the SSL configuration matches that described
in Using Secure Socket Layer (SSL) for Secured Remote Server Manager Administration on
page 48.
3. Verify that the user name and password provided in the browser matches the user name and
password configured in /opt/hpws22/tomcat/conf/tomcat-users.xml.
4. Verify that the Tomcat server is running by entering the following command:
# ps -efx | grep tomcat | grep -v grep
If Tomcat is running, following is a portion of the output that is displayed:
root 15408 1 Mar 29 ? 10:10 /opt/java6/bin/IA64N/java
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/java6
# /opt/hpws22/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/hpws22/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.
352 Troubleshooting Procedures