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.

Key log files for troubleshooting


 

The following table lists the key log files to use for troubleshooting, by product component.

A typical installation directory is <Drive>\Program Files\BMC Software on Microsoft Windows or /opt/bmc on UNIX and Linux.

Component

Log file

Location

BMC Cloud Lifecycle Management installation program

planner_install_log.txt

The BMC Cloud Lifecycle Management log file for the installation program. This log file records all installer activities during the entire solution installation. See Tracking installation progress.

Created under the temporary directory on the installer host.

Windows: %temp%

Linux: /tmp

ProductRegistry.xml

Stores list of Products installed on the host

Windows: C:\Windows

Linux: /opt/bmc

PlannerInstalledConfiguration.xml

Stores state of Planner Installation

<plannerInstallDirectory>

BMC Cloud Lifecycle Management preanalyzer

preanalyzer.log

The BMC Cloud Lifecycle Management log file for the installation preanalyzer. This log file records the environment analysis activities performed before installing or upgrading Cloud LifeCycle Management. See Launching-the-installer-and-pre-analyzing-your-environment.

<plannerInstallDirectory>/planner/logs

<planner_installer>/Disk1/

preanalyzer_report.html

Stores results of PreAnalyzer run

<plannerInstallDirectory>/reports

ProductConfig.properties

Stores input details for PreAnalyzer

<planner_installer>/Disk1/files/preanalyzer

Platform Manager

Capture all logs under ..\Platform_Manager\Logs, especially:

csm.log

The BMC Cloud Lifecycle Management log file for the Platform Manager.

<installDirectory>\BMC Cloud LifeCycle Management\Platform_Manager\Logs

BMC Cloud Lifecycle Management Core components

All Cloud_DB and Cloud_Portal logs

...\BMCCloudLifeCycleManagement\Cloud_DB\extensions\clm\public\schema\Logs

...\BMCCloudLifeCycleManagement\Cloud_DB\extensions\clm\private\schema\Logs

...\BMCCloudLifeCycleManagement\Cloud_DB\extensions\clm\private\dso\Logs

...\BMCCloudLifeCycleManagement\Cloud_DB\extensions\clm\private\logic\Logs

...\BMCCloudLifeCycleManagement\Cloud_DB\extensions\clm\public\dso\Logs

...\BMCCloudLifeCycleManagement\Cloud_DB\extensions\clm\public\schema\Logs

...\BMCCloudLifeCycleManagement\Cloud_Portal\plugin\arplugin.log

 

Enterprise BMC Remedy AR System server
(AR System server)

arerror.log

Starting with BMC Remedy AR System 8.1 Service Pack 2, Full Text Search (FTS) errors are recorded in a single location, the arerror.log file. See AR-System-server-logging in the BMC Remedy Action Request System online technical documentation.

<installDirectory>\AR System\ARServer\Db

 

arplugin.log

The AR System plug-in server log file. This file is generated when the Java plug-in server starts.

<installDirectory>\AR System\ARServer\Db

 

armonitor.log

The AR monitor configuration file, which contains the commands that the armonitor binary executes.

<installDirectory>\AR System\ARServer\Db

 

arfilter.log

The AR filter log file shows all of the filters that were checked during an operation. If a filter was executed, the log also provides a list of the operations performed. By default, the log file is named arfilter.log.

<installDirectory>\AR System\ARServer\Db

Mid Tier

All Mid Tier logs, especially:

arsystem_install_log

<installDirectory>\ARSystem\

<installDirectory>\ARSystem\midtier\logs

Atrium Core Web Services

All Atrium Core Web Services logs

<installDirectory>\Atrium Web Registry\Logs

Cloud Portal Web Application

clmui_install_log.txt

..\CloudPortalWebApplication\tomcat\logs

..\CloudPortalWebApplication\tomcat\webapps\clmui\WEB-INF\classes\config.properties

BMC Self-Check Monitor

selfchecker_install_log.txt

%temp% directory

..\Selfchecker\tomcat\logs

TrueSight Server Automation server

appserver.log

Log file for the BMC Server Automation Application Server. See Controlling Application Server logging in the BMC Server Automation online technical documentation.

<installDirectory>/NSH/br/

 

rscd.log

Log file for the BMC Server Automation agent. See Controlling RSCD agent logging in the BMC Server Automation online technical documentation.

<installDirectory>

 

job_deployment_hostname.log

The log file for the Application Server instance of type Job, created by default by the BMC Cloud Lifecycle Maintenance installation program.

<installDirectory>/NSH/br/

 

config_deployment_hostname.log

The log file for the Application Server instance of type Job, created by default by the BMC Cloud Lifecycle Maintenance installation program.

<installDirectory>/NSH/br/

TrueSight Network Automation server

BCA-Networks.log

The BMC Network Automation application server log files. See Understanding application server log files in the BMC Network Automation online technical documentation.

...\BCA-Networks-Data\log

TrueSight Orchestration

grid.log

The grid.log is the most important log file that BMC Atrium Orchestrator generates, and is used for troubleshooting CDP issues, adapter issues, and BMC Atrium Orchestrator Development Studio issues. The grid.log file is created shortly after the peer is started for the first time.

For more information about logging in BMC Atrium Orchestrator, see the Understanding-the-log-files in the BMC Atrium Orchestrator online documentation.

AO_HOME/tomcat/logs

 

processes.log

Contains logging generated by BMC Atrium Orchestrator workflows.

AO_HOME/tomcat/logs

 

repository.log

Contains logging information for the BMC Atrium Orchestrator repository.

AO_HOME/repository/logs

Remedy Single Sign-On

rsso.0.log

localhost.<timestamp>.log

Contains logging generated during configuring or using Remedy Single Sign-On with BMC Cloud Lifecycle Management.

<endUserPortalInstallDirectory>/bmc/CloudPortalWebApplication/tomcat/logs

Related topic

Enabling-logs-if-you-run-into-upgrade-problems

 

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