Troubleshooting continuous compliance for servers issues
This following topics offer basic troubleshooting tips for common issues that might occur when implementing continuous compliance for servers.
Troubleshooting Closed Loop Server Compliance and Audit
To troubleshoot issues with the Closed Loop Server Compliance and Closed Loop Server Audit use cases, perform the steps in the following table to isolate the issue.
Product | Troubleshooting steps |
---|---|
BMC Server Automation | Perform the following checks to isolate the issue.
|
BMC Atrium Orchestrator | Perform the following checks to verify that the modules and adapters are loaded and working.
|
BMC Remedy ITSM | Perform the following checks to see if the ticket was created.
|
Troubleshooting operator-initiated change
To troubleshoot issues with the operator-initiated change use case, perform the steps in the following table to isolate the issue.
Product | Troubleshooting steps |
---|---|
BMC Server Automation | Perform the following checks to isolate the issue:
|
BMC Atrium Orchestrator | Perform the following checks to verify modules and adapters are loaded and working:
|
BMC Remedy ITSM | Perform the following checks to see if the change request was created or updated.
|
Troubleshooting server incident enrichment
To troubleshoot issues with the Server Incident Enrichment use case, perform the following steps to isolate the issue:
Product | Troubleshooting steps |
---|---|
BMC Server Automation | Check for any of the following details:
|
BMC Atrium Orchestrator | Perform the following checks to verify that the modules and adapters are loaded and working.
|
BMC Remedy ITSM | Perform the following checks:
|
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.
- 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 steps topic 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, Debug level adapter logging steps topic in the BMC Atrium Orchestrator online documentation.
- Enable additional logging in BMC Server Automation. For information, see Working with logs in the BMC Server Automation documentation.
Comments
Log in or register to comment.