Share This:

Welcome to March’s new AR Server Blog post and we are discussing D2P Log Analysis.

 

When working with the Deployment Manager Console, if you experience an issue, the following logs are automatically generated that can be used to troubleshoot the problem:

      • ard2pplugin.log: Collects Plug-in related logging. Always resides on AR Server
      • ard2pclient.log: Collects logs only when you are deploying a package using the command-line interface
      • arfiledeployer.log: Collects logs specific to the binary payload in a package
      • ard2pdeploymentactivity.log: Collects Filter, SQL, and API combined logging. Always resides on AR Server
      • armonitor.log: Collects logs for AR, Mid Tier, and Smart IT application activities

 

 

The default location of all these logs:

ComponentOperating System
Location
AR System ServerWindows<Install directory>\BMC Software\ARSystem\Arserver\Db
Linux<Install directory>/BMC Software/ARSystem/db
Mid tierWindows<Install directory>\BMC Software\ARSystem\midtier\filedeployer\Logs
Linux<Install directory>/bmc/ARSystem/midtier/filedeployer/Logs
Smart ITWindows<Install Directory\Smart_IT\filedeployer\Logs
Linux<Install Directory/Smart_IT/filedeployer/Logs>

 

 

Now let's see the different symptoms of package deployment and logging details

 

 

Stage
SymptomsLogging DetailsNext Steps
Package Import Fails
  • Unable to view the package after importing the ZIP file
  • Package import fails with 'Init Error'
  • The package fails to upload the ZIP file, and the status gets stuck in the importing state
  • Package import fails with the following error message: Error in plugin: ARSYS.ARF.ARMIGRATE

Import Failure Example 1:

  • Open ard2pplugin.log and locate the first line of the package import, search for "*/ARMigratePlugin starting import operation". Review the Date & Time on the above line to find the current attempt
    • You will find the import operation with package zip name, E.g. */ARMigratePlugin starting import operation.<Package Entry ID: E.g. ITSM2002.zip".
  • Review a couple of lines from this step to locate more details on what the import operation did and if the import was successful, E.g. ARException trying up update status to application!  form=RDA:DeploymentDataDetails status=1entryId=ITSM2002.zip.zip message=Error: Results from import log file:
  • As the message=Error, search for "ERROR -" from above line to locate the complete error message

import error.PNG

 

Import Failure Example 2:

import error 2.PNG

 

Import Success Example:

  • If package import is successful, you can search for "ARMigratePlugin: Import of Package completed" to get the complete details on what all files got imported. Review the Date & Time on the above line to find the current attempt
    • E.g. */Success: ARMigratePlugin: Import of Package completed.  Please check Log results that follow for Specific results:

import success.PNG

Review Troubleshooting package import issues
Package Deploy Fails

Package deploy fails with following error on AR System Deployment Management Console

  • Init Error
  • Init Pending Deploy

     

     

Deploy Failure Example 1:

  • Open ard2pplugin.log and locate the first line of the package deploy, search for "*/ARMigratePlugin : starting deploy". Review the Date & Time on the above line to find the current attempt
  • E.g. "/ARMigratePlugin: starting deploy init operation. <Package Entry ID: <id> Package Name: E.g. ITSM 2002, Package Version: <version>
      • Deploy operation will start only when the Import Operation is completed successfully. You will find "./ARMigratePlugin: import operation completed" message right before starting deploy
  • The first stage of deploy operation is "Deploy Init". If the package status on Deployment Management Console shows "Init Error", then in the log, search for "*/ARMigratePlugin: starting deploy init operation"
      • Review a couple of lines from this step to locate more details on the error message

deploy error 1.PNG

 

Deploy Failure Example 2:

  • The second stage of deploy operation is "Deploy Package". If the package status on Deployment Management Console shows "Init Pending Deploy", then in the ard2pplugin.log log, search for "*/ARMigratePlugin: starting deploy package item operation"
      • Review a couple of lines from this step to locate more details on the error message. Review the Date & Time on the above line to find the current attempt.
  • If the next couple of line shows "*/ARMigratePlugin: deploy package item operation completed" without any error, then open arfiledeployer.log to get further details on failure

deploy success 1.PNG

 

For package deploy, open arfiledeployer.log

  1. Search for "Connected to ARServer <hostname>". Review the Date & Time on the above line to find the current attempt.
    • Once AR Server is connected, review next few lines to confirm if the registration with AR System Monitor GUID is successful and CCS Settings are loaded
      • E.g. "Registering monitor in AR System Monitor with existing GUID <AGGAA5V0FWSPCAP03LG9PJ6T1ZOBIV>" (Monitor ID of this AR Server from AR System Monitor Form)
      • E.g. "Loading CCS settings for component ARServer_<hostname>_7319_AGGAA5V0FWSPCAP03LG9PJ6T1ZOBIV" (Hostname, Port and Monitor ID from AR System Monitor Form)
    • Search for "com.bmc.arsys.filedeployer.PayloadProcessor"
        • E.g. com.bmc.arsys.filedeployer.PayloadProcessor  - Found 3 payloads which are waiting for utility run."

     

    • If log show entry with "PayloadProcessor" and points to the correct number of payloads, it means package deploy operation is successful and you should continue with deployment payload operations.

    pending deplo success.PNG

     

    • If log stops writing post "Loading CCS settings for component", it means the package deploy operation has failed.

    pending deplo1.PNG

    Review Troubleshooting package deploy issues

    Package Deployment Payload Fails
    • The status of Deployment Payload entries is stuck in Waiting For Utility Run
    • The status of Deployment Payload entries in the package is any of the following:
      • Rollback Success
      • Download Failed
      • Deployment Failed
      • Rollback Failed
      • Skipped
      • Timed Out
      • Monitor Unreachable

    Deployment Payload Failure Example 1:

    • Locate the 'Deployment Payload' item entry from the D2P package and select 'View Payload Status' to confirm if payloads got deployed successfully or not
    • Copy the Deployment ID of the entry which shows 'Rollback' or any other status except success

    rollback.jpg

     

    • Open arfiledeployer.log and search using the GUID and find the first line, E.g. "Processing payload with DEPLOYMENT ID IDGAA5V0G75KCAPRSYOGPQVPGIG8TZ". Review the Date & Time on the above line to find the current attempt
      • Review a couple of lines from this step to locate more details and search for "payload as DEPLOYMENT FAILED"  (For any status other than success, the payload will always use deployment failed keyword)
      • Locate the line exactly above "payload as DEPLOYMENT FAILED" to see the actual cause of failure

      deployment payload error 1.PNG

       

      Deployment Payload Failure Example 2:deployment payload error 2.PNG

       

      Deployment Payload Failure Example 3:

      • Locate the 'Deployment Payload' item entry from the D2P package and select 'View Payload Status' to confirm if the host status is stuck in "Waiting For Utility Run" post running the arpayloaddeploymentutil.bat
      • If so, search for "Failed to read the PayLoad form", there is a possibility AR Server is not getting signal post utility run

      deployment payload Error 90.PNG

       

      • In such a case, open armonitor.log, search for 'Process Failed to Start'. Match the time from arfiledeployer.log and confirm if any AR Server process is stuck or failed to start

      armonitor.PNG

       

      Deployment Payload Success Example:

      deployment success.PNG

       

      Review Troubleshooting deployment payload issues

       

       

      Reference Information for additional details