Error: Invalid spaceKey on retrieving a related space config.

Collecting logs to troubleshoot package deployment issues

When you face any issues while importing a package that is provided as a binary payload, refer to the scenarios mentioned in Troubleshooting package deployment issues topic. If the issues still persist, collect log files. You can submit these files to BMC Customer Support, who use them to help you debug your system.

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:

    ComponentOperating systemLocationFile names
    AR System serverWindows

    <Install directory>\BMC Software\ARSystem\Arserver\Db

    • 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
    • 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.
  • Login to the computer where Mid Tier is installed. Collect the following mid tier logs:

    Component

    Operating system

    Location

    File name

    Component

    Operating system

    Location

    File name

    Mid tierWindows 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
  • Perform the following steps if the expected logs are not created for the arpayloaddeploymentutil.bat or arpayloaddeploymentutil.sh file:

    1. Open AR System Administration > AR System Administration Console > System > General > Centralized Configuration

    2. From the Component Name field, select com.bmc.arsys.filedeployer and select the associated AR System Server or mid tier entry. 

    3. From the Setting Name, select log-level
    4. Change the Setting Value to DEBUG.
    5. Run the arpayloaddeploymentutil.bat or arpayloaddeploymentutil.sh file again.

Related topic

Applying a deployment package

Was this page helpful? Yes No Submitting... Thank you

Comments