Sun Java Enterprise System 5 Installation Guide for UNIX

How to Troubleshoot Problems

This section provides guidelines for analyzing and identifying the source of problems during installation and uninstallation of Java ES.

This section contains the following subsections:

Examining Installation Log Files

If a problem occurs during installation or uninstallation, the first place to look for information on what happened is the installation logs. Informational, warning, and error messages are issued after such operations as user choices, package manipulations, and installation or uninstallation steps. Messages on installation, uninstallation, and install-time configuration are gathered into the source log files. Information that is displayed for each message includes date and time, log level, module ID, and the message text. Passwords are never included.

Log File Formats

There are four types of log files that capture installation or uninstallation information:

The log messages are stored in a Sun standard format called Unified Logging Format (ULF). If you find ULF difficult to read, you can use the Java ES Log Viewer to view the log messages.

Source log files can be edited with a text editor. The following table lists the formats of the source log files.

Table 9–1 Log File Formats

Logged Entity 

Log File Name Format 











After an uninstallation, the uninstaller removes the installer, the Log Viewer , and itself. However, source log files are not removed and are stored in the following locations:

ProcedureTo Use Log Files for Troubleshooting

  1. Examine the summary file. For example:


    If a problem occurred, determine which component caused the problem. Determine if multiple problems occurred. You will probably need to look at one or both of the detail logs.

  2. Examine the detail log. For example:


    Look for the first error or warning that occurred and resolve it. Sometimes resolving one error resolves a number of seemingly unrelated errors that follow.

Using the Log Viewer

The Java ES Log Viewer provides a graphical display for viewing the ULF log messages from the JavaES_Install_log.timestamp file or the JavaES_UnInstall_log.timestamp file. You display a log file by selecting Open in the File menu on the Log Viewer main page. If the file you specify already exists or cannot be opened for writing, a Log Viewer error occurs and you are returned to the Log Viewer main page. Such a file cannot exist in the directory used by the installer to store source logs.

The messages that meet your filtering criteria are displayed in a single log table when you click the Search button. After the log table is displayed, an individual row in the log table can then be selected for detailed display, including display in multiple-line format.

How Filtering Works

To tailor your logging output, you indicate your display preferences and search criteria on the Log Viewer main page after you have selected a ULF log file. Display Preferences indicate what language you want your selection displayed in, and what limitations to apply in displaying the filtered records.

There are three ways to filter messages so that the messages displayed are of sufficient importance or interest: by log level, by logger, and by content.

Some typical search criteria:

ProcedureTo Run the Log Viewer

Because the Log Viewer operates in read-only mode, multiple users can run the Log Viewer at the same time.

  1. On the command line, navigate to the location of the Log Viewer:

    • Solaris SPARC: /var/sadm/prod/SUNWentsys5i/Solaris_sparc

    • Solaris x86: /var/sadm/prod/SUNWentsys5i/Solaris_x86

    • Linux: /var/sadm/prod/sun-entsys5i/Linux_x86

    • HP-UX: /var/sadm/prod/sun-entsys5i/HPUX_PA-RISC

  2. Start the Log Viewer.


    The Log Viewer main page is displayed.

  3. In the File menu, select a log file for display.

    If the file you select is not ULF, you receive a message saying the selected file is not ULF and cannot be selected. Only ULF files can be displayed using the Log Viewer.

    If no ULF log files are available, the installation or uninstallation might not be completed yet. Wait and try again.

  4. Choose Display Preferences and Search Criteria for your scenario.

  5. Click Search.

    The log table displays the records that match your filtering criteria.

Verifying Product Dependencies

A number of product components have installation-time interdependencies. Problems that affect one product component can affect other product components. First, you should familiarize yourself with the information in Sun Java Enterprise System 5 Installation Planning Guide.

In addition to product component interdependencies, some product components depend on the existence of Solaris packages that might not be installed on the host. The absence of these packages could cause installation failures. Read the “Software Requirements” section of the Release Notes for details.

If a problem occurs starting a product component, examine that product component's log files. Locations of many product component log files are listed in Product Component Troubleshooting Tips.

Checking Resources and Settings

The following host-level issues can cause installation problems.

Checking Postinstallation Configuration

If you are having problems starting product components, verify that the procedures outlined in Chapter 6, Completing Postinstallation Configuration were followed correctly.

Checking the Distribution Media

If you are installing from a DVD or CD, examine the media for dirt or damage. Dirty discs can result in installation problems.

Checking Directory Server Connectivity

If you are installing a product component that relies on Directory Server, problems can be caused by one of these problems:

Removing Web Server Files and Directory

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.

Verifying Passwords

The installer queries you to supply a number of passwords for product components. If you are installing different product 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 Files Left Behind During an Uninstallation.

Examining the Installed or Uninstalled Product Components

If you have installed product components but are having problems and cannot reinstall or uninstall, check the installed component packages using the Solaris pkginfo command, the Linux rpm command, or the HP-UX swlist command. Compare the results with the Java ES packages listed in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX. Additional troubleshooting information is in Installation Fails Due to Files Left Behind During an Uninstallation.

Tip –

On Solaris 9 and Solaris 10, you can also use the product registry (prodreg tool) which provides a graphical interfaces that indexes components and their packages, superseding the pkg utilities. To invoke the product registry, type prodreg at the command prompt. For more information, refer to the prodreg(1) man page.

Verifying Administrator Access for Uninstallation

During uninstallation, you might need to grant administrator access to the uninstaller, as described in Granting Administrator Access for the Uninstaller.