Sun ONE Application Server 7, Enterprise Edition Installation Guide |
Chapter 6
TroubleshootingThis 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 MessagesBoth 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:
- INFO—These messages mark normal completion of a particular installation tasks.
- WARNING—These messages mark non-critical failures. Warning messages generally contain information about the cause and the nature of the failure, and also provide possible remedies.
- ERROR—These messages mark critical failures that cause installation or uninstallation status to be reported as Failed. Error messages generally provide detailed information about the nature and the cause of the problem that occurred.
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:
- For problems you may have with the installation or uninstallation process:
/var/sadm/install/logs/Sun_ONE_Application_Server_install.log
/var/sadm/install/logs/Sun_ONE_Application_Server_uninstall.log
- In addition to these log files, low-level installation and uninstallation log files are created at these locations:
/var/sadm/install/logs/Sun_ONE_Application_Server_install.<timestamp>
/var/sadm/install/logs/Sun_ONE_Application_Server_uninstall.<timestamp>
- For problems with the clsetup command:
/var/tmp/clsetup.log
- For problems with the cladmin command:
/var/tmp/cladmin.log
J2SE Installation/Upgrade IssuesThe installation program can only upgrade your J2SE installation when the following requirements are met:
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 PasswordIf you do not remember the administrative user name that was supplied during installation, try these solutions in this order:
- Enter the user name admin. This is the default user name specified in the server configuration dialog during installation.
- If this doesn’t work, look in the following file:
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.
- If this doesn’t work, delete the administrative domain and recreate it with a new password.
- As a last resort, uninstall and reinstall the Sun ONE Application Server.
Forgotten Admin Server Port NumberIf 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:
Connection Refused for Administration InterfaceIf 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 OccursIf 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 CleanupIf an uninstallation fails, you may need to clean up some leftover files or processes before attempting a new installation.
- Log in as root.
- 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.
cat /var/sadm/install/productregistry | grep SUNW
- Run pkgrm for the SUNW packages that were found in the product registry file. For example:
pkgrm SUNWasaco
- Remove the following files, if they are present:
/tmp/setupSDKNative
/tmp/SolarisNativeToolkit_3.0_1
- After the packages have been removed, manually remove the Sun ONE Application Server-specific product registry file itself.
rm /var/sadm/install/productregistry
- At the command line, find and kill all appservd processes that may be running by typing the following:
ps -ef | grep appservd
kill -9 PID- Remove all remaining files under the Sun ONE Application Server installation directories.
- If present, remove the following log file:
/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.