Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Troubleshooting

This section contains the following topics:

You can also use the log files to identify issues with the product. See the Troubleshooting section of the BMC Dashboards for Business Service Management Installation Guide for information about using the support utility to help you collect the log files.

The following logs are enabled by default and set to the INFO level:

Log files

Location

Purpose

BMC Dashboards for BSM logs

DashboardsInstallationDirectory\BMCDashboardsForBSM\
BSMDashboards\logs

The bsmdashboards.log and bsmdashboards-stdout.log files have calls from the BMC Dashboards for BSM user interface to the application server. These logs files provide authentication details and information about the BMC Atrium Data Integation Layer (BMC Atrium DIL) connectivity and the Derby database.

Application server logs

DashboardsInstallationDirectory\BMCDashboardsForBSM\
BSMDashboards\tomcat\logs

These logs provide information about application server activities.

BMC Atrium DIL logs

DashboardsInstallationDirectory\BMCDashboardsForBSM \DIL\CIS\logs

These logs provide information about all BMC Atrium DIL-related activities (for example, caches, calls from the application server to BMC Atrium DIL).

If you need to change the logging level to provide more details, you can change the application server logs and the BMC Atrium DIL logs to DEBUG.

To change the application server log to DEBUG, navigate to DashboardsInstallationDirectory\BMCDashboardsForBSM\
BSMDashboards\tomcat\webapps\bsmdashboards\WEB-INF\classes\log4j-config.xml file, change the priority value to debug, and restart the application server.

To change the BMC Atrium DIL logs to DEBUG, use the following steps:

  1. Navigate to the DashboardsInstallationDirectory\BMCDashboardsForBSM\DIL\CIS\conf\server\log4j.properties file.

  2. Scroll to the end of the file and update the following WARN values to DEBUG:

    log4j.logger.com.bmc.dil.proc=WARN
    log4j.logger.com.bmc.dil.config=WARN
    log4j.logger.com.bmc.dil.shared.config=WARN
    log4j.logger.com.bmc.dil.util=WARN

    The updated values are shown below:

    log4j.logger.com.bmc.dil.proc= DEBUG
    log4j.logger.com.bmc.dil.config= DEBUG
    log4j.logger.com.bmc.dil.shared.config= DEBUG
    log4j.logger.com.bmc.dil.util=DEBUG

  3. Edit the DashboardsInstallationDirectory\BMCDashboardsForBSM\CIS\conf\dil\dil.propertiesfile and add the following line to it:

    dil.logging=true
  4. Restart the BMC Atrium DIL service.

Using the DEBUG value causes the log file to fill quickly, so you should clean up the logs by using the following steps.

  1. Stop the application server service and the BMC Atrium DIL services.
  2. Archive the old log files.
  3. Delete the log files manually.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*