Configuration and log files on RHUA, CDS and client systems

Solution Verified - Updated -

Environment

  • Red Hat Update Infrastructure 2.1

Issue

  • Which configuration and log files to check on RHUA, CDS or client system in case of RHUA related service?

Resolution

  • Configuration files

  1. RHUA

    /etc/pulp/*
/etc/rhui/rhui-tools.conf
/etc/qpidd.conf ( For qpid problems )
/etc/pki/rhua/*
/etc/pki/rhui/*
RHUI 2.0.2+: /etc/pki/pulp/*
pre RHUI 2.0.2: /etc/pki/content/*
The answers file used with rhui-installer (wherever it was saved)

  2. CDS

    /etc/pulp/*
/etc/pki/cds/*
For Qpid Issues, check to make sure the RHUI specific config has been added in /etc/qpidd.conf

# SSL - Added by RHUI Installer  
auth=no # RHUI  
require-encryption=yes # RHUI  
ssl-require-client-authentication=yes # RHUI  
ssl-cert-db=/etc/pki/rhua/qpid-nss # RHUI  
ssl-cert-password-file=/etc/pki/rhua/qpid-nss/password # RHUI  
ssl-cert-name=broker # RHUI  
ssl-port=5674 # RHUI

    Make sure port 5674 is opened in iptables and in any external firewall.

  • Log files and Debugging

  1. RHUA

    /root/.rhui/rhui.log* (assuming rhui-manager is run as root, which is  standard; however, if sudo is used, the .rhui dir is in the home directory of the user)
/root/.rhui/rhui-installer.log (likewise as above)
/var/log/pulp/*
/var/log/httpd/*
/var/log/messages (this is where Qpid logs)

  2. CDS

    /var/log/pulp-cds/*
/var/log/gofer/agent.log
/var/log/httpd/*

  3. Client

    /var/log/yum.log
/var/log/messages
Console output from yum commands

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments