Chapter 9. Configuration files, exit codes, and log files
The following configuration files, RHUI manager exit codes, and log files are used in Red Hat Update Infrastructure 4.
Configuration Files
| Component | File or Directory | Usage |
|---|---|---|
| Red Hat Update Appliance |
| Pulp config files |
|
| rhui-manager config files | |
|
| Certificates for Red Hat Update Infrastructure | |
|
| Used to set up the RHUA | |
|
| Configuration for the subscription synchronization script | |
| Content Delivery Server |
| Certificates for CDS |
| HAProxy |
| HAProxy configuration file |
RHUI Manager Exit Codes
RHUI Manager uses the following codes to indicate the result of running the rhui-manager status command and running the rhui-manager CLI commands.
| Status Code | Description |
|---|---|
| 0 | Success |
| 1 | General error or a repository synchronization error |
| 2 | SSL certificate error on a CDS |
| 32 | Entitlement CA or SSL certificate expiration warning |
| 64 | Entitlement CA or SSL certificate expiration error |
| 128 | One or more RHUI services is not running on the RHUA, CDS, or HAProxy nodes |
| 239 | A repository could not be deleted because it does not exist. |
| 240 | There was an issue with a required resource. For example, it was impossible to build a client configuration RPM because no valid repository was found. |
| 241 | A synchronization task could not be scheduled because an unknown repository was specified. To troubleshoot * Check the spelling * Add the repository first * Check logs for Pulp issues |
| 242 | A custom repository could not be created due to a Pulp issue. Check the message and logs for details. |
| 243 | Red Hat repositories could not be added because some of them already exist in RHUI and some of them were not available in the entitlement. |
| 244 | A custom repository could not be created because it already exists in RHUI. |
| 245 | A Red Hat repository could not be added because it already exists in RHUI. |
| 246 |
A Red Hat repository could not be added because it is not available in the entitlement. Check the spelling or remove the repository mapping cache using the command |
| 247 | A Red Hat repository could not be added due to a Pulp issue. Check the message and logs for details. |
| 248 |
Migration from RHUI 3 to RHUI 4 was stopped because one or more Red Hat repositories are already present in RHUI 4. You must remove the repositories or use the |
| 249 |
The RHUI configuration, |
| 250 | The entitlement certificate is not writable. |
| 251 | The entitlement certificate has expired. |
| 252 | The entitlement certificate is invalid because it does not contain RHUI repositories. |
| 253 | The entitlement certificate file is not a valid certificate. |
| 254 | Command-line Error: The RHUI CLI could not run due to a network issue. |
| 255 | Argument Error: A required argument was not supplied. |
Log Files
| Component | File or Directory | Usage |
|---|---|---|
| Red Hat Update Appliance |
| Red Hat Update Infrastructure Management Tool logs |
|
| Pulp logs; for example, repository synchronization | |
|
| nginx logs | |
|
| CDS and HAproxy management log, service status log | |
|
| Subscription synchronization log | |
|
| Repository export log | |
|
| Temporary directory cleanup log | |
|
| Repository version mapping log | |
| Content Delivery Server |
| nginx logs |
|
| clients' requests for content | |
|
| CDS authorizer plug-in logs; by default, requests without an entitlment certificate | |
|
| CDS content manager plug-in logs; for example, on-demand package downloads | |
|
| CDS mirror plug-in logs; by default, only logs from starting and stopping the plug-in | |
| Client |
| yum command logs |
| Client |
| dnf command logs |
|
| Client syslog |
See also older logs saved with a number or a time stamp as an extension, possibly compressed by gzip.