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:
Topic |
Details |
---|---|
Configuration File |
AMConfig.properties
|
Log and Debug Files |
Log file directory:
|
Debug Mode |
Refer to the Auditing Features chapter in the Sun Java System Access Manager 7.1 Developer’s Guide. |
Topic |
Details |
---|---|
Log Files |
Log file directory:
Application Server instance log directory (default location for the initially created instance):
Message log file name: server.log, for each server instance |
Configuration Files |
|
Troubleshooting |
Refer to the Sun Java System Application Server Enterprise Edition 8.2 Troubleshooting Guide. |
Topic |
Details |
---|---|
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:
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. |
Topic |
Details |
---|---|
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. |
Topic |
Details |
---|---|
Log Files |
Runtime log file: Solaris: /opt/SUNWcomm/log |
Troubleshooting |
Topic |
Details |
---|---|
Log Files |
Installation log file:
|
Troubleshooting |
Topic |
Details |
---|---|
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:
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. |
Topic |
Details |
---|---|
Log Files |
Installation log file:
Broker log file:
|
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. |
Topic |
Details |
---|---|
Executable Location |
Process log files:
Configure log files:
|
Log Files |
|
Troubleshooting |
Refer to the Sun Java System Messaging Server 6.3 Administration Guide. |
Topic |
Details |
---|---|
Configuration Files |
For Monitoring Console:
For Monitoring Framework:
|
Log Files |
For Monitoring Console:
For Monitoring Framework:
|
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 |
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:
If Web Server configuration fails during Configure Now installation, refer to the following logs for additional information:
|
Configuration File Directory |
|
The following information in this guide is also useful for troubleshooting:
Chapter 6, Completing Communications Suite Postinstallation Configuration contains instructions for performing post-installation configuration.
Chapter 9, Uninstalling Communications Suite Product Components contains information on problems that might occur while uninstalling the software.