Reference logs for troubleshooting RHSM enhancements

Use the reference logs for troubleshooting RHSM enhancements.

Download plug-in log and configuration files

Enhanced logging with clearer error reporting and error handling to improve troubleshooting.

RHSMPlugin.log
Lists the results of the downloads related to the execution of the RHSM download plug-in. The amount of information depends on the logging level.
The log can be found in the following locations:
  • On Windows systems: %PROGRAM FILES%\BigFix Enterprise\BES Server\DownloadPlugins\RHSMProtocol
  • On Linux systems: /var/opt/BESServer/DownloadPlugins/RHSMProtocol
Note: Due to a no hash download limitation, some errors which are not relevant to your deployment might display in the log.
RHSMDownloadCacher.log
Displays the results of the entitlement certificate access check to Red Hat repositories that BigFix supports.
  • On Windows systems: %PROGRAM FILES%\BigFix Enterprise\BES Server\DownloadPlugins\RHSMProtocol
  • On Linux systems: /var/opt/BESServer/DownloadPlugins/RHSMProtocol
Note: Due to a no hash download limitation, some errors which are not relevant to your deployment might display in the log.
You can set logging levels for RHSMDownloadCacher.log. For more information, see Using the RHSM download cacher.
plugin.ini
The RHSM configuration log can be found in the following location: <BES Server install location>\DownloadPlugins\RHSMProtocol\plugin.ini.
  • On Windows systems, the file is in the BigFix server installation directory. For example, %PROGRAM FILES%\BigFix Enterprise\BES Server\DownloadPlugins\ RHSMProtocol.
  • On Linux systems, the file is in the root directory tree occupied by the download plug-in. For example, /var/opt/BESServer/DownloadPlugins/RHSMProtocol.
To retrieve information that can be used for troubleshooting issues, update the logger level value to DEBUG.

Client log file

The following log file can be found in the client folder in the directory /var/opt/BESClient/EDRDeployData.

EDR_DeploymentResults.txt
Lists the results of the EDR deployment and the Yum output.