Sun ONE logo      Previous      Contents      Index      Next     

Sun ONE Application Server 7, Enterprise Edition Installation Guide

Chapter 6
Troubleshooting

This chapter describes how to solve common problems that might occur during installation of the Sun ONE Application Server 7, Enterprise Edition software.

The following topics are addressed here:

About Logs and Messages

Both the installation and uninstallation programs create log files and log all installation and uninstallation events to these files. The primary purpose of these log files is to provide troubleshooting information.

In addition to installation program messages and log files, operating system utilities such as pkginfo and showrev on Solaris can be used to gather system information.

Log file entries include information about the attempted action, the outcome of the action, and, if applicable, the cause of failure. The log files contain the following types of message entries:

For a full listing of the Sun ONE Application Server error messages, refer to the Enterprise Edition of the Sun ONE Application Server Error Messages Reference.

The following Application Server logs can be useful for troubleshooting:

J2SE Installation/Upgrade Issues

The installation program can only upgrade your J2SE installation when the following requirements are met:

  1. The following Solaris J2SE packages reside on the machine where you are performing installation:
    • SUNWj3rt
    • SUNWj3dev
    • SUNWj3man
    • SUNWj3dmo

      • Verify this by running the pkginfo -i -l command on these packages.

      Note

      The installation program can only upgrade a package-based J2SE installation, not a file-based J2SE installation.

  2. The version of the Solaris J2SE packages is greater than or equal to version 1.3 and less than version 1.4.1_03.
  3. The /usr/j2se (default) directory is writable by the user performing the installation.

The following types of errors may occur if you attempt to upgrade your J2SE during installation:

Incompatible J2SE version---cannot upgrade.

If you receive this type of error, the first or second requirements above have not been met.

Solution

Resolve your J2SE package or version issues by either fixing the Solaris packages or completely removing the Solaris packages (only if they are not used by any other application programs) using the pkgrm command.

If you remove the packages, you can then install the J2SE component using the installation program by selecting the Install Java 2 SDK (1.4.1_03) option in the Java Configuration panel.

Failure to install J2SE reported through install log file.

If you receive this type of error, the third requirement above has not been met.

Solution

Verify that your /usr/j2se directory is not read-only.

Forgotten User Name or Password

If you do not remember the administrative user name that was supplied during installation, try these solutions in this order:

  1. Enter the user name admin. This is the default user name specified in the server configuration dialog during installation.
  2. If this doesn’t work, look in the following file:

    3. domain_config_dir/domain1/admin-server/config/admpw

    This file contains the administrator's user name followed by the encrypted form of the administrative user's password. Seeing the user name may jog your memory.

  3. If this doesn’t work, delete the administrative domain and recreate it with a new password.
  4. As a last resort, uninstall and reinstall the Sun ONE Application Server.

Forgotten Admin Server Port Number

If you do not remember the HTTP server port number of the Admin Server, you can inspect the Admin Server's configuration file to determine the HTTP server port number:

  1. Navigate to domain_config_dir/domain1/admin-server/config/ and open the server.xml file in a text editor.
  2. Look for the following element:

    3. http-listener id="http-listener-1" address="0.0.0.0" port="4848"...

    In this case, port 4848 is the HTTP port number in use.

Connection Refused for Administration Interface

If the connection was refused when attempting to invoke the graphical Administration interface, it is likely that the Admin Server is not running. The Admin Server log file may be helpful in determining the reason the Admin Server is not running.

To start the Admin Server, use the command-line instructions in "Starting and Stopping the Server".

Server Won’t Start: CGI Error Occurs

If the Sun ONE Application Server won’t start, you may receive the following error:

The system may require additional resources. Possible solutions are described in the following sections:

Set Limits on File Descriptions

You can use the ulimit command to determine the number of available file descriptors or set limits on the system’s available file descriptors. The ulimit command displays the limits for the current shell and its descendants.

For the sh shell, the ulimit -a command lists all the current resource limits. The ulimit -n command lists the maximum file descriptors plus 1.

On Solaris: Change Kernel Parameters

On Solaris, increase the system resources by modifying the /etc/system file to include the following entries:

The system will require a reboot for the new kernel parameters to take effect.

After you have set the shell resources, the Sun ONE Application Server should start.

Uninstallation Failure Cleanup

If an uninstallation fails, you may need to clean up some leftover files or processes before attempting a new installation.

  1. Log in as root.
  2. Navigate to your installation directory and check the content of the /var/sadm/install/productregistry file for installed packages. That is, check for files having the SUNW string.

    3. cat /var/sadm/install/productregistry | grep SUNW

  3. Run pkgrm for the SUNW packages that were found in the product registry file. For example:

    4. pkgrm SUNWasaco

  4. Remove the following files, if they are present:

    5. /tmp/setupSDKNative

    /tmp/SolarisNativeToolkit_3.0_1

  5. After the packages have been removed, manually remove the Sun ONE Application Server-specific product registry file itself.

    6. rm /var/sadm/install/productregistry

  6. At the command line, find and kill all appservd processes that may be running by typing the following:

    7. ps -ef | grep appservd
    kill -9     PID

  7. Remove all remaining files under the Sun ONE Application Server installation directories.
  8. If present, remove the following log file:

    9. /var/sadm/install/logs/Sun_ONE_Application_Server_install.log

    This is necessary because every iteration of installation appends the log information to this file if it exists.



Previous      Contents      Index      Next     

Copyright 2003 Sun Microsystems, Inc. All rights reserved.