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 may be required to collect more information on 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 on how to do this see "Using log files" in the BMC Remedy Action Request System Optimizing and Troubleshooting Guide.
- For more information on logging in BMC Atrium Orchestrator, see “Troubleshooting” in the BMC Atrium Orchestrator System 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.
- 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 Application Adapter for BMC Remedy Action Request System User Guide.
- Enable additional logging in BMC BladeLogic Server Automation. For information, see “BMC BladeLogic log file reference” in the BMC BladeLogic ServerAutomation Administration Guide.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*