Sun Java Enterprise System 5 Installation Guide for UNIX

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: