Identifying issues between BMC Atrium Orchestrator and BMC Server Automation

When you receive an error message from the BMC Server Automation adapter, is it not always clear whether the error is from BMC Server Automation or BMC Atrium Orchestrator, but the error message itself gives a few indicators:

• If the error is in the grid.log and not the processes.log, the error is from BMC Atrium Orchestrator. This is because the processes.log contains the adapter request and response, so any messages sent by BMC Server Automation will be included there.
• If the error in the processes.log is "An internal error occurred", the error is from BMC Atrium Orchestrator. The grid.log will have more information.
• If the error in the processes.log contains an error number, the error is from BMC Server Automation. BMC Atrium Orchestrator does not have error numbers. For more information about logging in BMC Atrium Orchestrator, see the Troubleshooting topic in the BMC Atrium Orchestrator online documentation.
• If the adapter response indicates that the command was run as a "success" but still contains an error, the issue is with the command or with BMC Server Automation. This means that the adapter ran the command as expected, and BMC Server Automation returned an error message because the command caused an error.

After you have determined the source of the error, there are a few steps you can take to get more information:

• Test your command using BLCLI without using the adapter. If the same command completes successfully, then the adapter is not running the command properly. If the command fails with the same error message, there is an issue with the command or with BMC Server Automation. See the BMC Server Automation BLCLI Help for specific information about commands.
• Verify that BMC Server Automation is running properly.
  • Log on to the BMC Server Automation Console to view the status of each application server instance, using the Infrastructure Management view (Configuration > Infrastructure Management).
  • If you cannot log on to the console, you can verify the status of the Application Server Launcher using the following steps:
    • (Windows) Confirm the status of the BMC Server Automation Application Server service.
    • (UNIX) Confirm the presence of the Application Server Launcher process by executing ps -ef | grep blapp.
• Enable additional logging in BMC Server Automation. For information, see the Working with logs topic in the BMC Server Automation online documentation.
• Enable additional logging on the BMC Server Automation adapter in BMC Atrium Orchestrator. For information about how to do this see the Debug level adapter logging steps in topic in the BMC Atrium Orchestrator online documentation.