Sun Java Enterprise System 2005Q4 Installation Guide for UNIX

Component Troubleshooting Tips

This section provides various quick tips on components, with 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: /etc/opt/sun/identity/config

Log and Debug Files

Log file directory: 

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

  • Linux: /var/opt/sun/identity/logs

    Debug file directory:

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

  • Linux: /var/opt/sun/identity/debug

Debug Mode

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

Administration Server Troubleshooting Tips

Table 9–3 Administration Server Troubleshooting Tips

Topic 

Details 

Log Files

Installation log directory:

Troubleshooting

Refer to the . 

Application Server Troubleshooting Tips

Table 9–4 Application Server Troubleshooting Tips

Topic 

Details 

Log Files

Log file directory: 

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

Linux: /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: /var/opt/sun/appserver/domains/domain1/logs

Message log file name: 

server.log, for each server instance

Configuration Files

Configuration file directory: /var

Troubleshooting

Refer to the Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Troubleshooting Guide.

Calendar Server Troubleshooting Tips

Table 9–5 Calendar Server Troubleshooting Tips

Topic 

Details 

Log Files

Administration Service (csadmind): admin.logDistributed

Database Service (csdwpd): dwp.logHTTP Service (cshttpd): http.log

Notification Service (csnotifyd): notify.logCalendar

Backup Service (csstored): store.log

Default log directory: /var/opt/SUNWics5/logs

For more information, refer to Sun Java System Calendar Server 6 2005Q4 Administration Guide.

Configuration File

/opt/SUNWics5/cal/config/ics.conf

Debug Mode

To use debug mode, a Calendar Server administrator sets the logfile.loglevel configuration parameter in the ics.conf file. For example:

logfile.loglevel = "debug"

For more information, refer to Sun Java System Calendar Server 6 2005Q4 Administration Guide.

Troubleshooting

Refer to Sun Java System Calendar Server 6 2005Q4 Administration Guide.

Communications Express Troubleshooting Tips

Table 9–6 Communications Express Troubleshooting Tips

Topic 

Details 

Log Files

Default log files: uwc-deployed-path/logs/uwc.log

Troubleshooting

Refer to the Chapter 6, Troubleshooting, in Sun Java System Communications Express 6 2005Q4 Administration Guide.

Delegated Administrator Troubleshooting Tips

Table 9–7 Delegated Administrator Troubleshooting Tips

Topic 

Details 

Log Files

Runtime log file: /opt/SUNWcomm/log

Troubleshooting

Refer to Appendix C, Debugging Delegated Administrator, in Sun Java System Communications Services 6 2005Q4 Delegated Administrator Guide.

Directory Proxy Server Troubleshooting Tips

Table 9–8 Directory Proxy Server Troubleshooting Tips

Topic 

Details 

Log Files

Default log file: DirectoryProxyServer-base/dps -hostname/logs/fwd.log

For more information, refer to the Sun Java System Directory Proxy Server 5 2005Q1 Administration Guide.

Troubleshooting

Refer to the Sun Java System Directory Proxy Server 5 2005Q1 Administration Guide.

Directory Server Troubleshooting Tips

Table 9–9 Directory Server Troubleshooting Tips

Topic 

Details 

Log Files

Installation log file: 

Solaris OS: /var/sadm/install/logs

Linux: /var/opt/sun/install/logs

Configuration log files: 

Directory_Server_install.Atimestamp

Directory_Server_install.Btimestamp

For information on managing log files, refer to the Sun Java System Directory Server 5 2005Q1 Administration Guide.

Troubleshooting

Refer to the Sun Java System Directory Server 5 2005Q1 Administration Guide.

Instant Messaging Troubleshooting Tips

For information on troubleshooting Instant Messaging, refer to the client online help and the Sun Java System Instant Messaging 7 2005Q1 Administration Guide.

Message Queue Troubleshooting Tips

Table 9–10 Messaging Server Troubleshooting Tips

Topic 

Details 

Troubleshooting

Refer to the Troubleshooting Problems chapter of the Sun Java System Message Queue Administration Guide and the MQ Forum, at: http://swforum.sun.com/jive/forum.jspa?forumID=24.

Performance

Refer to “Analyzing and Tuning a Message Service” Sun Java System Message Queue 3 2005Q4 Administration Guide.

Messaging Server Troubleshooting Tips

Table 9–11 Messaging Server Troubleshooting Tips

Topic 

Details 

Executable Location

/opt/SUNWmsgsr/sbin

Log Files

MessagingServer-base/data/log

Troubleshooting

Refer to the Sun Java System Messaging Server 6 2005Q4 Administration Guide.

Portal Server Troubleshooting Tips

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

Table 9–12 Portal Server Troubleshooting Tips

Topic 

Details 

Debug Files

Solaris OS: /var/opt/SUNWam/debug

Linux: /var/opt/sun/identity/debug

Log Files

Solaris OS: /var/opt/SUNWam/logs

Linux: /var/opt/sun/identity/logs

Troubleshooting

Refer to the Sun Java System Portal Server 6 2005Q4 Administration Guide.

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


Tip –

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.


Portal Server Secure Remote Access Troubleshooting Tips

Portal gateway debug logs are located in the following directories:


Note –

Logs for Portal Server services (such as NetFile) are in /var/opt/SUNWam/debug when logging is turned on from Access Manager Administration Console.


Service Registry Troubleshooting Tips

Table 9–13 Service Registry Troubleshooting Tips

Topic 

Details 

Log Files

Application Server instance log:  

Solaris OS: /var/opt/SUNWsoar/domains/registry/logs/server.log

Linux: /var/opt/sun/SUNWsoar/domains/registry/logs/server.log

Troubleshooting

Refer to the Service Registry 3 2005Q4 Administration GuideService Registry 3 2005Q4 Administration Guide.

Sun Cluster Software Troubleshooting Tips

Table 9–14 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 Server Troubleshooting Tips

Table 9–15 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, both located in the following directories:

  • Solaris OS: /opt/SUNWwbsvr/https-instancename/logs

  • Linux: /opt/sun/webserver/https-instancename/logs

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 6.1 SP4 Administrator’s Guide.

Troubleshooting

Refer to the Sun Java System Web Server 6.1 SP4 Installation and Migration Guide.

Configuration File Directory

/opt/SUNWwbsvr/https-instance-name /config

Debug Mode

The following options are available: 

Web Proxy Server Troubleshooting Tips

Table 9–16 Web Proxy Server Troubleshooting Tips

Topic 

Details 

Log Files

Default log location: /opt/SUNWproxy/proxy-instancename/logs

For more information, refer to the Sun Java System Web Proxy Server 4.0.2 Administration Guide.

Configuration File Directory

/opt/SUNWproxy/proxy-instancename /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.

Additional Troubleshooting Information

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