This section provides general guidelines for analyzing and identifying the source of problems during installation and uninstallation of Java ES.
This section contains the following subsections:
Solaris OS: /var/sadm/install/logsLinux: /var/opt/sun/install/logs
Examining the uninstall and installer log files (along with the Java ES configuration log and component logs) can help locate the source of problems. For example, you can compare the packages listed in the installation log to the packages listed in the uninstallation log.
Most logs have two versions:
An A version of the log file records completion.
A B version of the log file contains more detailed log messages.
The following table lists the formats of the log files.Table 9–1 Java ES Log File Name Formats
Log File Name Format
Java_Enterprise_System_Summary_Report_ uninstall. timestamp
To use the log files for troubleshooting, attempt to isolate the first problem that occurred. Often, the first problem leads to successive problems.
The log files can give you clues that determine your next steps, such as these:
If there was a configuration problem, look at the configuration summary to examine the settings you used.
If there was a directory conflict, check that you did not specify a directory that is reserved by a component.
Review the installation summary file, which provides a high-level description of what was installed and configured.
If a problem occurred, see what component caused the problem. If multiple problems occurred, isolate the first.
Review the detailed log files.
If a problem occurs starting a component, examine its log files. Locations of many component log files are listed in Component Troubleshooting Tips.
A number of components have installation-time interdependencies. Problems that affect one component can affect other components. First, you should familiarize yourself with the information in Sun Java Enterprise System 2005Q4 Installation Planning Guide
Review the summary file and log files to see whether related products have failed. These might provide a clue as to what to fix first.
Check that you have specified correct connection information. For example:
Does the information that you provided when configuring Directory Server match the directory information you provided for components that use Directory Server?
Does the Access Manager information that you provided for Portal Server or Portal Server SRA match the information you provided for Access Manager?
In addition to component interdependencies, some components depend on the existence of Solaris packages that might not be installed on the host, and their absence could cause installation failures. Read the “Software Requirements” section of the Release Notes for details.
The following host-level issues can cause installation problems.
Updates. Have you applied the recommended updates (patches)?
Disk Space. How is the disk partitioned, and to what partitions do installation directories point? The installation directories /var/sadm and /etc/opt, or the non-default directories that you specify, need sufficient disk space.
Network Ports. During configuration, you supply port numbers for Java ES components. Check the following:
Examine the standard port numbers in the file /etc/services .
Look at the summary log file to compare your settings with the standards. Did you mistype a port number or set one server to the port that is typically used for another?
Use the command netstat -a to view current port use on the system. Did you assign a port number that was already in use?
IP Addresses. During configuration, you specify IP addresses. Check that you entered the correct IP addresses. These are some questions to resolve:
Does this system have multiple network interfaces, each with its own IP address?
In a high availability configuration, did you specify the IP address of the logical host or the IP address of a cluster node?
If you are having problems starting components, verify that the procedures outlined in Chapter 6, Configuring Components After Installation were done correctly.
If you are installing from a DVD or CD, examine the media for dirt or damage. Dirty discs can result in installation problems.
If you are installing a component that relies on Directory Server, problems can be caused by one of these problems:
You specified an incorrect user ID and password for Directory Server.
You specified an incorrect LDAP port.
Directory Server is unreachable.
The interactive modes of the installer check for Directory Server connectivity during installation, but silent mode does not. If you perform a silent installation when Directory Server is not available, installation of Access Manager or Portal Server could fail.
To prevent the overwriting of customized files, such as edited configuration files, Web Server cannot be installed into a directory that contains files.
If you are reinstalling Web Server, check the installation directories to ensure that they are empty. If they are not empty, archive the files elsewhere and retry the installation.
The installer requires that you enter a number of passwords for components. If you are installing different components on different hosts, it is important to ensure that you supply matching passwords on each host.
To resolve password problems, you might need to uninstall and then reinstall. If the uninstall fails, refer to Installation Fails Due to Leftover Files During Uninstallation.
If you have installed components but are having problems and cannot reinstall or uninstall, check the packages installed using the Solaris pkginfo or the Linux rpm command. Compare the results with the Java ES packages listed in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 2005Q4 Installation Reference uninstalled. Additional information is in Installation Fails Due to Leftover Files During Uninstallation.
On Solaris 9 and Solaris 10, you can also use the prodreg tool which provides a graphical interface to the product registry that indexes both components and their packages, superseding the pkg utilities. To invoke prodreg, type the command name at the command line. For more information, refer to the prodreg(1) man page.
During uninstallation, you might need to grant administrator access to the uninstaller, as described in Granting Administrator Access for the Uninstaller.