Product Component Troubleshooting Tips

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.1 Developer’s Guide.

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

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

• Linux: /var/opt/sun/appserver/config/asenv.conf

Troubleshooting

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

Log Files

Administration Service (csadmind): admin.log

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

Notification Service (csnotifyd): notify.logCalendar

Backup Service (csstored): store.log

Default log directory:  

• Solaris: /var/opt/SUNWics5/logs

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

For more information, refer to Sun Java System Calendar Server 6.3 Administration Guide.

Configuration File

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

Linux: /opt/sun/calendar/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.3 Administration Guide.

Troubleshooting

Refer to Sun Java System Calendar Server 6.3 Administration Guide.

Log Files

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

Instance Directory

Solaris OS: /var/opt/SUNWuwc

Linux: /var/opt/sun/uwc

Troubleshooting

Refer to the Chapter 5, Troubleshooting, in Sun Java System Communications Express 6.3 Administration Guide.

Log Files

Runtime log file: 

Solaris: /opt/SUNWcomm/log

Troubleshooting

Refer to Appendix C, Debugging Delegated Administrator, in Sun Java System Delegated Administrator 6.4 Administration Guide.

Log Files

Installation log file: 

• Solaris: /var/sadm/install/logs

• Linux: /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.

Log Files

Server log: xmppd.log

Agent calendar log: agent-calendar.log

WatchDog log: iim_wd.log

Multiplexor log: mux.log.log

Default log directory: 

• Solaris: /var/opt/SUNWiim/default/log

• Linux: /var/opt/sun/im/default/log

For more information, refer to Sun Java System Instant Messaging 7.2 Administration Guide

Configuration File

Solaris: /opt/SUNWiim/config/iim.conf

Linux: /opt/sun/im/config/iim.conf

Debug Mode

To use debug mode, an Instant Messaging administrator sets the iim.log.iim_server.severity configuration parameter in the iim.conf file.

Example for the server component: 

iim.log.iim_server.severity = "DEBUG"

Example for the multiplexor component: 

iim.log.iim_mux.severity = "DEBUG"

Example for the watchdog component: 

iim.log.iim_wd.severity = "DEBUG"

Troubleshooting

For further specifics and additional information on troubleshooting, refer to Sun Java System Instant Messaging 7.2 Administration Guide.

Post-Uninstallation Tasks

Instant Messaging configuration directories and Instant Messages resources deployed in the web container are not removed during uninstallation and should be removed after uninstallation.  

To completely remove Instant Messaging from a host, unnecessary directories such as the following should be removed: /opt/SUNWiim/, /var/opt/SUNWiim/, and /etc/opt/SUNWiim/.

In addition, resources should be undeployed from the web container using the undeploy all command.

Log Files

Installation log file: 

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

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

Broker log file: 

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

• Linux: /var/opt/sun/imq/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.

Executable Location

Process log files: 

• For Solaris OS: /opt/SUNWmsgsr/sbin

• For Linux: /opt/sun/messaging/sbin

Configure log files: 

• MessagingServer-base/install

Log Files

• For Solaris OS: MessagingServer-base/data/log

• For Linux: /opt/sun/messaging/log

Troubleshooting

Refer to the Sun Java System Messaging Server 6.3 Administration Guide.

Configuration Files

For Monitoring Console: 

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

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

For Monitoring Framework: 

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

• For Linux: /etc/opt/sun/mfwk/config/mjwk.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: /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

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: /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: /var/opt/sun/webserver7/setup/WebServer_Install.log

Configuration File Directory

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

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