Chapter 11. Monitoring

Red Hat Update Infrastructure Manager can display information about the state of the Red Hat Update Infrastructure installation in several different ways. The most human-readable information is available in the Synchronization Status and Scheduling screen, which is described in Chapter 9, Status and Scheduling. Status and monitoring information can also be obtained in a machine-readable state, for use with automated monitoring solutions such as Nagios.

Procedure 11.1. Monitoring the state of Red Hat Update Infrastructure

  1. To retrieve a status code that provides a summary of the current state of the Red Hat Update Infrastructure, run the rhui-manager command from the shell prompt with the status command, and echo the result to standard output: 
    # rhui-manager --username admin --password admin status

# echo $?
0
    This command should be automated to suit your individual requirements.

    Note

    It is recommended that this command always be used with the --username and --password switches specified, in order to bypass the authentication certificate and avoid the command failing due to expired credentials.
  2. A status code of 0 indicates that the Red Hat Update Infrastructure is running correctly. Other values, such as listed in Table 11.1, “Status Codes”, indicates an error exists. If multiple errors exists, the status codes are logically OR'd together.

    Table 11.1. Status Codes

    Status Code Description
    0 Success
    1 Repository synchronization error
    2 CDS synchronization error
    4 CDS heartbeat error
    8 Identity certificate expiration warning
    16 Identity certificate expiration error
    32 Entitlement CA certificate expiration warning
    64 Entitlement CA certificate expiration error

Log Files

  • ~/.rhui/rhui.log
    Red Hat Update Infrastructure Manager logs
  • /var/log/pulp/pulp.log
    Red Hat Update Appliance logs

    Note

    The pulp.log file is automatically written to a new enumerated log file when the base file reaches 1MB in size. The most recent four versions are kept in addition to the currently written file.
  • /var/log/pulp/grinder.log
    Package synchronization output

    Note

    The grinder.log file is automatically written to a new enumerated log file when the base file reaches 1MB in size. The most recent four versions are kept in addition to the currently written file.
  • /var/log/pulp-cds/gofer.log
    The gofer.log file is located on CDS instances, and logs information about errors related to the CDS function.
  • /var/log/gofer/agent.log
    The agent.log file is located on CDS instances, and logs information about communication errors. This file contains information about whether the CDS instance was able to successfully connect to the Qpid broker running on the Red Hat Update Appliance.
Report a bug