Sun Java Enterprise System 5 Installation Guide for UNIX

Chapter 9 Troubleshooting

This chapter provides suggestions on how to resolve Sun JavaTM Enterprise System (Java ES) installation and uninstallation problems.

This chapter includes the following sections:

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 

Installer 

Java_Enterprise_System_5_install.Atimestamp

Java_Enterprise_System_5_install.Btimestamp

JavaES_Install_log.timestamp

Java_Enterprise_System_5_Summary_Report_install.timestamp

Uninstaller 

Java_Enterprise_System_5_uninstall.Atimestamp

Java_Enterprise_System_5_uninstall.Btimestamp

JavaES_UnInstall_log.timestamp

Java_Enterprise_System_5_Summary_Report_uninstall.timestamp

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:

    Java_Enterprise_System5_Summary_Report_install.timestamp

    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:

    JavaES_Install_logtimestamp

    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.


    ./viewlog

    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.

Resolving Installation Problems

This section addresses the following problems you might encounter during installation.

Installation Fails Due to Files Left Behind During an Uninstallation

Uninstallation can leave behind product component files or packages. In such a case, you might need to manually remove the files or packages before you can reinstall Java ES. The installer reports that the product component is on the host, even though you thought you removed it.

The following might have occurred:

ProcedureTo Clean Up a Partial Installation

  1. Use the following command to determine whether any packages were partially installed.

    Solaris OS: pkginfo -p

    Linux: rpm -qa |grep —I ^sun | xargs rpm -V

    HP-UX: swlist -l product sun-*

    The command output lists any partially installed packages. Using the package names returned, refer to Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX to discover what product component the packages belong to.

  2. Remove components or packages.

    • On Solaris 9 or 10, use the prodreg tool.

      The prodreg tool manages the package-based components on your host. You can view product components and their packages, with full information, including interdependencies. You can use the prodreg tool to safely uninstall product components and remove packages. Once you have removed a product component with the prodreg tool, you can reinstall.

    • On Linux, use the rpm -e command.

      To edit the product registry file, open the file /var/opt/sun/install/productregistry. This XML file describes each product component. Each product component description starts with a <compid\> tag and ends with a </compid\> tag. Delete the entire entry for the product component.

    • On HP-UX, use the swremove command.

      To edit the product registry file, open the file /var/adm/swproductregistry. This XML file describes each product component. Each product component description starts with a <compid\> tag and ends with a </compid\> tag. Delete the entire entry for the product component.

  3. Verify that the following directories do not contain Java ES product components or packages:

    /opt

    /etc/opt

    /var/opt

  4. Run the installer again.

Installation Fails Due to Removed Shared Components in Product Registry After Uninstallation

As of the Java ES 5 release, shared components are listed in the product registry file after installation.

The Java ES uninstaller removes product components from the system but does not remove shared components. After an uninstallation, the product registry still contains entries for the shared components. If you manually remove any Java ES shared components after an uninstallation, these components are not removed from the product registry. Thus, the next Java ES 5 installation fails because the installer assumes that the manually deleted shared components are present (because they still have entries in the product registry file).


Tip –

Avoid manually removing Java ES shared components from your system.


Suggested Fix. Either remove the corresponding entries from the product registry file or remove the product registry file itself. Removing entries from the product registry file can cause the file to become corrupted, so you might prefer to remove the whole product registry. Before doing this, verify that products other than Java ES components are not using the product registry file.

On Linux and HP-UX there is no equivalent of the graphical product registry that exists on Solaris OS. If you manually removed files on Linux or HP-UX, you must manually edit the product registry file to remove those entries.

Cannot Configure IBM WebSphere as the Portal Server Web Container

WebSphere might not be running, or you might have specified a WebSphere value that does not match the WebSphere native configuration. There are two approaches to troubleshooting this issue. IBM WebSphere is only supported as a web container on Solaris OS.

Check the Configuration

One approach is to check the configuration of your WebSphere instance.

ProcedureTo Check the WebSphere Configuration

  1. Ensure that WebSphere is running.

  2. Examine the values for the following installer fields:

    • WebSphere Virtual Host (PS_IBM_VIRTUAL_HOST in the state file)

    • Application Server Name (PS_IBM_APPSERV_NAME in the state file)

  3. Use the WebSphere tools to check the configuration to make sure it matches the values you are entering.

  4. Try again.

Create New Instances

Another approach is to create new instances of the WebSphere entities.

ProcedureTo Create New Instances of WebSphere Entities

  1. Use the adminclient.sh to start the WebSphere console.

  2. Create a new virtual host instance and a new Application Server instance name.

  3. Click the entry under Nodes (typically the host name), and select Regen WebServer Plugin.

    This process saves the new entries into the plugin configuration file, which the installer checks for the legal names.

  4. Return to the installer and enter the values you just created.

Unexpected External Error Occurs

A power failure or system failure might have occurred, or you might have entered CTRL/C to stop the installer process.

Suggested Fix. If the failure occurred during the installation or configuration process, you are probably left with a partial installation. Run the uninstaller. If the uninstaller fails, follow the instructions under Uninstallation Fails, Leaving Behind Files

Graphical Installer Seems Unresponsive

The installer sometimes creates an image on the screen before the image is ready for input. You cannot repeatedly click Next in the installation wizard without waiting.

Suggested Fix. The button that represents the default choice includes a blue rectangle. This rectangle sometimes appears after the button itself appears. Wait until you see the blue rectangle before clicking a button.

Silent Installation Fails: “State File is Incompatible or Corrupted”

If you are using a state file that was created on the same platform on which you are using it, the problem might be due to an unknown file corruption error. There are two approaches to troubleshooting this issue.

Generate a New State File

Create a New Platform-Appropriate ID

If the platform on which you created the state file is not the same as the platform on which you are running the silent installation, create a new, platform-appropriate ID for the file. For instructions on how to do this, refer to Creating a Platform-Appropriate State File ID.

Silent Installation Fails After Editing the State File

If you edited the state file, you might have introduced errors. Check the following and regenerate the state file as described in Creating a State File.

Suggested Fix. Resolve the problem and regenerate the state file.

Man Pages Do Not Display

The most likely reason for this is that your MANPATH environment variable is not set correctly for the components you installed.

Suggested Fix. Update /etc/MANPATH to point to the new man page directory. Refer to Verifying Man Pages .

Resolving Uninstallation Problems

This section addresses the following problems you might encounter during uninstallation.

Cannot Find Uninstaller

The Java ES installation program places the uninstaller on your system at the following location:

If the uninstaller is not in this directory, one of the following might have occurred:

Suggested Fix. Manually clean up your system as described in Uninstallation Fails, Leaving Behind Files.

Uninstallation Fails, Leaving Behind Files

If manual cleanup is necessary because the uninstaller left behind files or processes, perform the following procedure to remove packages from your system.

ProcedureTo Manually Clean Up Packages

  1. Determine which packages you want to remove.

    Compare the packages on your system with the Java ES packages listed in Chapter 5, List of Installable Packages, in Sun Java Enterprise System 5 Installation Reference for UNIX. (See also Installation Fails Due to Files Left Behind During an Uninstallation. You can use the following commands to determine which packages are installed:

    • Solaris OS pkginfo or prodreg utility

    • Linux rpm command

    • HP-UX swlist command

  2. Stop all running processes for Java ES product components.

    Brief instructions for stopping processes are contained in Chapter 6, Completing Postinstallation Configuration product component documentation.

  3. Back up all custom configuration and user data you plan to use in subsequent installations.

    Reviewing Uninstallation Behavior for Java ES Product Components provides some information on configuration and user data that should be backed up. For more information, refer to the product component documentation for each product component.

  4. Use the pkgrm, rpm -e, or swremove command to remove Java ES component packages.

  5. Remove any remaining product component directories and their content that you do not plan to use in subsequent installations. If you do plan to use these directories later, move them elsewhere.

  6. Update the product registry file, which is located here:

    • Solaris OS: /var/sadm/install/productregistry

    • Linux: /var/opt/sun/install/productregistry

    • HP-UX: /var/adm/sw/productregistry

    The uninstaller uses this registry to determine which product components are installed on a host. Both the installer and uninstaller update the product registry upon completion of an installation or uninstallation.


    Note –

    If you manually remove packages rather than using the uninstaller, then you must edit the product registry so it correctly reflects the software installed on your system.


  7. Clean up the log files for your system, which are located here:

    • Solaris OS: /var/sadm/install/logs

    • Linux and HP-UX: /var/opt/sun/install/logs

    The log files might not correctly reflect the state of your system after you manually remove packages.

Product Registry Is Corrupted

During uninstallation, the uninstaller uses the product registry file to determine what needs to be uninstalled:

Resolving Common Agent Container Problems

This section addresses the following problems that might arise in relation to the common agent container shared component:

Port Number Conflicts

The common agent container (V2.0) included with Java ES reserves the following port numbers by default:

If you are troubleshooting an installation of Sun Cluster software, the port assignments are different because Sun Cluster software uses a different version of common agent container. In this case, default ports are as follows:

If your installation already reserves any of these port numbers, change the port numbers used by the common agent container as described in the following procedure.

Checking Port Numbering

For further information on the common agent container cacaoadm command, see the cacaoadm man page. If you cannot see this man page at the command line, verify that your MANPATH is set correctly. Refer to Verifying Man Pages .

ProcedureTo Verify Port for Solaris OS

  1. As root, stop the common agent container management daemon:


    /usr/sbin/cacaoadm stop
  2. Change the port number using the following syntax:

    /usr/sbin/cacaoadm set-param param=value

    For example, to change the port occupied by the SNMP Adaptor from the default 11161 to 11165:


    Note –

    For Sun Cluster software, use previously-specified ports.



    /usr/sbin/cacaoadm set-param snmp-adaptor-port=11165
  3. Restart the common agent container management daemon:


    /usr/sbin/cacaoadm start

ProcedureTo Verify Port For Linux or HP-UX

  1. As root, stop the common agent container management daemon:


    /opt/sun/cacao/bin/cacaoadm stop
  2. Change the port number using the following syntax:

    /opt/sun/cacao/bin/cacaoadm set-param param=value

    For example, to change the port occupied by the SNMP Adaptor from 11161 to 11165:


    /opt/sun/cacao/bin/cacaoadm set-param snmp-adaptor-port=11165
  3. Restart the common agent container management daemon:


    /opt/sun/cacao/bin/cacaoadm start

Compromised Security Around the Root Password

It might be necessary to regenerate security keys on a host running Java ES. For example, if there is a risk that a root password has been exposed or compromised, you should regenerate security keys. The keys used by the common agent container services are stored in the following locations:

Solaris OS: /etc/opt/SUNWcacao/securityLinux and HP-UX: /etc/opt/sun/cacao/security

Under normal operation, these keys can be left in their default configuration. If you need to regenerate the keys due to a possible key compromise, you can regenerate the security keys using the following procedure.

ProcedureTo Generate Keys for Solaris OS

  1. As root, stop the common agent container management daemon.


    /usr/sbin/cacaoadm stop
  2. Regenerate the security keys.


    /usr/sbin/cacaoadm create-keys --force
  3. Restart the common agent container management daemon.


    /usr/sbin/cacaoadm start

    Note –

    In the case of Sun Cluster software, you must propagate this change across all nodes in the cluster. For more information, see How to Finish a Rolling Upgrade to Sun Cluster 3.1 8/05 Software in Sun Cluster Software Installation Guide for Solaris OS.


ProcedureTo Generate Keys for Linux and HP-UX

  1. As root, stop the common agent container management daemon.


    /opt/sun/cacao/bin/cacaoadm stop
  2. Regenerate the security keys.


    /opt/sun/cacao/bin/cacaoadm create-keys --force
  3. Restart the common agent container management daemon.


    /opt/sun/cacao/bin/cacaoadm start

    For more information on the cacaoadm(1M) command, see the cacaoadm man page.

Resolving Postinstallation Start/Restart Problems

This section addresses various problems that might arise after installation.

Monitoring Rules Stop Working (status Unknown)

If you have restarted Application Server, the communication between Application Server and Monitoring Console has been disrupted and needs to be reactivated. Monitoring rules that were previously working, no longer work and are in a status of Unknown. If you have restarted the common agent container on the Application Server host, the problem will still exist because the common agent container must also be restarted on the Monitoring Console host.

ProcedureTo Reestablish Application Server Communication to Monitoring Console

  1. As root, restart the common agent container on the host where Application Server resides. For example:


    /usr/sbin/cacaoadm start
  2. Then go to the host where Monitoring Console resides and restart the common agent container. For example:

    If common agent container is already running, stop it, then start it with these commands.

    On Solaris OS:


    /usr/sbin/cacaoadm stop
    /usr/sbin/cacaoadm start

    On Linux and HP-UX:


    /opt/sun/cacao/bin/cacaoadm stop
    /opt/suncacao/bin/cacaoadm start

Portal Database Not Found After Java DB Restart

This can occur when you deploy an Application Server sample that uses Java DB after running the default Application Server command to restart Java DB (asadmin stop-databsse then asadmin start-database). Portal Server samples are no longer be accessible.

Suggested Fix. There are a number ways to approach this problem

  1. Do not stop Java DB.

  2. If Java DB was stopped, restart Java DB with the following command allowing the Application Server database to be created in an alternate location.

    Solaris OS: /asadmin start-database --dbhome /var/opt/SUNWportal/derby

    Linux and HP-UX: /asadmin start-database --dbhome /var/opt/sun/portal/derby

    If you want the database to be located in the default location, start a second instance of Java DB using a non-default port, then specify the correct Derby port in the Application Server samples common.properties file. For example: asadmin start-database --dbport 1528

Product Component Troubleshooting Tips

The tables in this section provide various quick tips on troubleshooting product component problems, including references to useful documentation. This section contains the following subsections:

Access Manager Troubleshooting Tips

Table 9–2 Access Manager Troubleshooting Tips

Topic 

Details 

Configuration File

AMConfig.properties

  • Solaris OS: /etc/opt/SUNWam/config

  • Linux and HP-UX: /etc/opt/sun/identity/config

Log and Debug Files

Log file directory: 

  • Solaris OS: /var/opt/SUNWam/logs

  • Linux and HP-UX: /var/opt/sun/identity/logs

Debug file directory: 

  • Solaris OS: /var/opt/SUNWam/debug

  • Linux and HP-UX: /var/opt/sun/identity/debug

Debug Mode

Refer to the Auditing Features chapter in the Sun Java System Access Manager 7.1 Developer’s Guide.

Application Server Troubleshooting Tips

Table 9–3 Application Server Troubleshooting Tips

Topic 

Details 

Log Files

Log file directory: 

  • Solaris OS: /var/sadm/install/logs/

  • Linux and HP-UX: /var/opt/sun/install/logs/

Application Server instance log directory (default location for the initially created instance): 

  • Solaris OS: /var/opt/SUNWappserver/domains/domain1/logs

  • Linux and HP-UX: /var/opt/sun/appserver/domains/domain1/logs

Message log file name: 

server.log, for each server instance

Configuration Files

  • Solaris OS: /opt/SUNWappserver/appserver/config/asenv.conf

  • Linux and HP-UX: /opt/sun/appserver/config/asenv.conf

Troubleshooting

Refer to the Sun Java System Application Server Enterprise Edition 8.2 Troubleshooting Guide.

Directory Server Troubleshooting Tips

Table 9–4 Directory Server Troubleshooting Tips

Topic 

Details 

Log Files

Installation log file: 

  • Solaris OS: /var/sadm/install/logs

  • Linux and HP-UX: /var/opt/sun/install/logs

Troubleshooting

Refer to Part I, Directory Server Administration, in Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide

Refer to Part II, Directory Proxy Server Administration, in Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide.

Message Queue Troubleshooting Tips

Table 9–5 Message Queue Troubleshooting Tips

Topic 

Details 

Log Files

Installation log file: 

  • For Solaris OS: /var/sadm/install/logs

  • For Linux and HP-UX: /var/opt/sun/install/logs

Broker log file: 

  • For Solaris OS: /var/mq/instances/instance-name/log

  • For Linux and HP-UX: /var/opt/sun/mq/instances/instance-name/log

Troubleshooting

Refer to the Troubleshooting Problems chapter of the Sun Java System Message Queue 3 2005Q4 Administration Guide.

For performance problems, refer to “Analyzing and Tuning a Message Service” in the Sun Java System Message Queue 3 2005Q4 Administration Guide.

Monitoring Console Troubleshooting Tips

Table 9–6 Monitoring Console Troubleshooting Tips

Topic 

Details 

Configuration Files

For Monitoring Console: 

  • For Solaris OS: /opt/SUNWjesmc/WEB-INF/web.xml

  • For Linux and HP-UX: /opt/sun/jesmc/WEB-INF/web.xml

  • For Solaris OS: /etc/opt/SUNWmfwk/config/mfwk.properties

  • For Linux and HP-UX: /etc/opt/sun/mfwk/config/mfwk.properties

  • For Solaris OS: /etc/opt/SUNWmfwk/config/masteragent.properties

  • For Linux and HP-UX: /etc/opt/sun/mfwk/config/masteragent.properties

Log Files

For Monitoring Console: 

  • /var/log/webconsole/console/console_config_log (all platforms)

  • /var/log/webconsole/console/console_debug_log (all platforms)

For Monitoring Framework: 

  • For Solaris OS: /var/opt/SUNWmfwk/logs

  • For Linux and HP-UX: /var/opt/sun/mfwk/logs

Troubleshooting

If you cannot access Monitoring Console, refer to Troubleshooting the Monitoring Console in Sun Java Enterprise System 5 Monitoring Guide. If you cannot see your monitored components in the Monitoring Console, refer to Troubleshooting the Monitoring Framework in Sun Java Enterprise System 5 Monitoring Guide

Portal Server Troubleshooting Tips

Portal Server uses the same log files and debug files as Access Manager.

Table 9–7 Portal Server Troubleshooting Tips

Topic 

Details 

Debug Files

Solaris OS: /var/opt/SUNWam/debug

Linux and HP-UX: /var/opt/sun/identity/debug

Portal Server Desktop debug files: 

Solaris OS: /var/opt/SUNWam/debug/desktop and /var/opt/SUNWam/debug/desktop.dpadmin.debug

Linux and HP-UX: /var/opt/sun/identity/debug/desktop and /var/opt/sun/identity/debug/desktop.dpadmin.debug

The dpadmin, par, rdmgr, and sendrdm Portal Server command line utilities have options to generate debugging messages. They are described in the Portal Server Administration Guide.

Log Files

Solaris OS: /var/opt/SUNWam/logs

Linux and HP-UX: /var/opt/sun/identity/logs

Troubleshooting

Refer to the Sun Java System Portal Server 7.1 Administration Guide.

Portal Server Secure Remote Access Troubleshooting Tips

Portal gateway debug logs are located in the following directories:


Note –

For Solaris OS, logs for Portal Server services (such as NetFile) are in /var/opt/SUNWam/debug when logging is turned on from the Access Manager Administration Console.


Service Registry Troubleshooting Tips

Table 9–8 Service Registry Troubleshooting Tips

Topic 

Details 

Log Files

Instance log directory: 

  • Solaris OS: /var/opt/SUNWsrvc-registry/domains/registry/logs

  • Linux and HP-UX: /var/opt/sun/srvc-registry/domains/registry/logs

Message log file name is server.log.

Configuration File Location

Solaris OS: /opt/SUNWsrvc-registry/install/install.properties

Linux and HP-UX: /opt/sun/srvc-registry/install/install.properties

Troubleshooting

Refer to the Service Registry 3.1 Administration Guide.

Sun Cluster Software Troubleshooting Tips


Note –

HP-UX and Linux do not support Sun Cluster components.


Table 9–9 Sun Cluster Software Troubleshooting Tips

Topic 

Details 

Log Files

Default log directory: /var/cluster/logs/install

Error messages: /var/adm/messages

Troubleshooting

Refer to the Sun Cluster Software Installation Guide for Solaris OS.

Web Proxy Server Troubleshooting Tips

Table 9–10 Web Proxy Server Troubleshooting Tips

Topic 

Details 

Log Files

Default log location:

  • Solaris OS: /opt/SUNWproxy/proxy-instance-name/logs

  • Linux and HP-UX: /opt/sun/webproxyserver//proxy-instance-name/logs

The errors log file lists all the errors the server has encountered. The access log file records the information about requests to the server and the responses from the server. For more information, refer to the Sun Java System Web Proxy Server 4.0.4 Administration Guide.

Configuration File Directory

For Solaris OS: /opt/SUNWproxy/proxy-instance-name /config

For Linux and HP-UX: /opt/sun/webserver/proxy-instance-name /config

Debug Mode

You can set the value of the loglevel attribute of the LOG element in the /server-root/proxy-instance-name /config/server.xml file: info, fine, finer, finest.

Web Server Troubleshooting Tips

Table 9–11 Web Server Troubleshooting Tips

Topic 

Details 

Log Files

There are two types of Web Server log files: the errors log file and the access log file. The errors log file lists all the errors a server has encountered. The access log records information about requests to the server and the responses from the server. For more information, refer to the Sun Java System Web Server 7.0 Administrator’s Guide

These logs are located in the following directories: 

  • Solaris OS: /var/opt/SUNWwbsvr7/https-instancename/logs

  • Linux and HP-UX: /var/opt/sun/webserver7/https-instancename/logs

If Web Server configuration fails during Configure Now installation, refer to the following logs for additional information: 

  • Solaris OS: /var/opt/SUNWwbsvr7/setup/WebServer_Install.log

  • Linux and HP-UX: /var/opt/sun/webserver7/setup/WebServer_Install.log

Admin Server errors logs can be found here: 

  • Solaris OS: /var/opt/SUNWwbsvr7/admin-server/logs/errors

  • Linux and HP-UX: /var/opt/sun/webserver7/admin-server/logs/errors

Configuration File Directory

  • Solaris OS:/var/opt/SUNWwbsvr7/https-instance-name/config

  • Linux and HP-UX:/var/opt/sun/webserver7/https-instance-name/config

Additional Troubleshooting Information

The following information in this guide is also useful for troubleshooting: