Collecting logs to troubleshoot package deployment issues
When working with the Deployment Manager Console, if you experience a problem, logs are automatically generated that can be used to troubleshoot the problem. These logs can be collected and sent to BMC Customer Support for analysis and debugging. If you experience a problem while importing a binary payload, refer to the scenarios mentioned in Troubleshooting-package-deployment-issues topic.
When an issue occurs during package deployment, it can be difficult to identify the exact API, Filter, and SQL statements from their respective logs. The ard2pdeploymentactivity.log log file captures automatically (without pre-enabling logs) the specific API, filter, and SQL log lines related to all deployment operations such as Deploy, Build, Rollback.
To collect logs from an individual server
When you run the arpayloaddeploymentutil.bat or arpayloaddeploymentutil.sh utility and if an issue occurs while deploying the package, you need to send the process logs and mid tier logs to BMC Customer Support. The following tables provide details about collecting process logs and mid tier logs:
Login to the computer where AR System server is installed. Collect the following process logs:
Component
Operating system
Location
File names
AR System server
Windows
<Install directory>\BMC Software\ARSystem\Arserver\Db
- ard2pdeploymentactivity.log
Collects Filter logs, SQL logs, and API logs - ard2pplugin.log
Collects Plug-in related logs - ardebug.log
Collects entire server activity logs related to package deployment or rollback. - arfiledeployer
Collects logs specific to binary payload in a package. - ard2pclient
Collects logs only when you are deploying a package using command line interface. - armonitor.log
Collects logs for the entire AR Server activities.
UNIX
<Install directory>/BMC Software/ARSystem/db
- ard2pdeploymentactivity.log
Collects Filter logs, SQL logs, and API logs - ard2pplugin.log
Collects Plug-in related logs - ardebug.log
Collects entire server activity logs related to package deployment or rollback. - arfiledeployer
Collects logs specific to binary payload in a package. - ard2pclient
Collects logs only when you are deploying a package using command line interface. - armonitor.log
Collects logs for the entire AR Server activities.
- ard2pdeploymentactivity.log
Login to the computer where Mid Tier is installed. Collect the following mid tier logs:
Component
Operating system
Location
File name
Mid tier
Windows and UNIX
<Install directory>\BMC Software\ARSystem\midtier\filedeployer\Logs
- armonitor.log
Collects logs for Mid Tier activities. - arfiledeployer
Collects logs specific to binary payload in a package.
UNIX
<Install directory>/bmc/ARSystem/midtier/filedeployer/Logs
- armonitor.log
Collects logs for Mid Tier activities. - arfiledeployer
Collects logs specific to binary payload in a package.
If there is an issue regarding mid tier Tomcat Process Start/Stop, also collect the associated Tomcat application logs from the following loacation:
Operating system
Location
File name
Windows
<MidtierTomcatInstall Directory>\apace\tomcat7.0\logs\
catalina.date.log For example, catalina.2019-02-04.log
UNIX
<Midtier TomcatInstall Directory>/apache/tomcat7.0/logs
catalina.date.log
For example, catalina.2019-02-04.log- armonitor.log
- Perform the following steps if the expected logs are not created for the arpayloaddeploymentutil.bat or arpayloaddeploymentutil.sh file:
- Open AR System Administration > AR System Administration Console > System > General > Centralized Configuration
- From the Component Name field, select com.bmc.arsys.filedeployer and select the associated AR System Server or mid tier entry.
- From the Setting Name, select log-level.
- Change the Setting Value to DEBUG.
- Run the arpayloaddeploymentutil.bat or arpayloaddeploymentutil.sh file again.
Related topic