Identifying issues between BMC Atrium Orchestrator and BMC BladeLogic Server Automation

When you receive an error message from the BMC BladeLogic Server Automation adapter, is it not always clear whether the error is from BMC BladeLogic 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 BladeLogic 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 BladeLogic Server Automation. BMC Atrium Orchestrator does not have error numbers. For more information on logging in BMC Atrium Orchestrator, see “Troubleshooting” in the BMC Atrium Orchestrator System Administration Guide.
• If the adapter response indicates that the command was run as a “success” but still contains an error, the problem is with the command or with BMC BladeLogic Server Automation. This means that the adapter ran the command as expected, and BMC BladeLogic Server Automation returned an error message because the command caused an error.

Once 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 BladeLogic Server Automation. See the BMC BladeLogic Server Automation BLCLI Help for specific information on commands.
• Verify that BMC BladeLogic Server Automation is running properly.
  • Log on to the BMC BladeLogic 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:
    • On a Microsoft Windows system, confirm the status of the BMC BladeLogic Server Automation Application Server service.
    • On Unix-style systems, confirm the presence of the Application Server Launcher process by executing ps -ef | grep blapp.
• Enable additional logging in BMC BladeLogic Server Automation. For information, see “BMC BladeLogic log file reference” in the BMC BladeLogic ServerAutomation Administration Guide.
• Enable additional logging on the BladeLogic adapter in BMC Atrium Orchestrator. For information on how to do this see "Debug level adapter logging steps" in the BMC Atrium Orchestrator Application Adapter for BMC BladeLogic Server Automation User Guide.