Additional investigation and debug logging

You can also investigate various log files for additional information.

Search for errors in the BMC Atrium Orchestrator logs – grid.log and processes.log. Identify which product is giving the error message, the meaning of the error message, and potential resolutions.

Debug logs might be required to collect more information about the transaction encountering the error.  Below is a list of additional logs that can be enabled.

• Enable additional logging on the BMC Remedy ITSM server. Log the output to files. For information about how to do this see "Using log files" in the BMC Remedy Action Request System Optimizing and Troubleshooting Guide at PDFs.
• For more information about logging in BMC Atrium Orchestrator, see the Troubleshooting topic in the BMC Atrium Orchestrator online documentation.
• Enable additional logging on the BladeLogic adapter in BMC Atrium Orchestrator. For information about how to do this, see Debug-level adapter logging in the BMC Atrium Orchestrator online documentation.
• Enable additional logging on the Remedy adapters in BMC Atrium Orchestrator. For details on how to enable logging, see Debug-level adapter logging in the BMC Atrium Orchestrator online documentation.
• Enable additional logging in BMC Server Automation. For information, see the Working with logs topic in the BMC Server Automation online documentation.