Chapter 6. Maintaining a Red Hat Satellite Server

This chapter provides information on how to maintain a Red Hat Satellite Server, including information on relevant log files, how to enable debug logging, how to open a support case and attach the relevant log tar files, and how to use Red Hat Insights to proactively diagnose systems.

6.1. Logging and Reporting

Red Hat Satellite provides system information in the form of notifications and log files.

Table 6.1. Log Files for Reporting and Troubleshooting

Log File
Description of Log File Content
/var/log/candlepin
Subscription management
/var/log/foreman
Foreman
/var/log/foreman-proxy
Foreman proxy
/var/log/httpd
Apache HTTP server
/var/log/foreman-installer/satellite
Satellite installer
/var/log/foreman-installer/capsule
Capsule Server installer
/var/log/libvirt
Virtualization API
/var/log/mongodb
Satellite database
/var/log/pulp
Celerybeat and Celery startup request messages. After startup is complete, messages are logged to /var/log/messages.
/var/log/puppet
Configuration management
/var/log/rhsm
Subscription management
/var/log/tomcat6 and /var/log/tomcat
Apache web server messages for Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7, respectively.
/var/log/messages
Various other log messages related to pulp, rhsm, and goferd.
You can also use the foreman-tail command to follow many of the log files related to Satellite. You can run foreman-tail -l to list the processes and services that it follows.
On Red Hat Enterprise Linux 7, you can use the journal for more extensive logging information. See Using the Journal[3] for more information.