Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 17. Logging and Reporting Problems

The following sections describe the most commonly used log files and debugging tools available in Satellite.

17.1. Increasing Logging Levels to Help with Debugging
Copier lien

You can increase the logging level of Satellite components to troubleshoot Satellite. Increasing the logging level to debug provides the most detailed information. The default logging level is info.

To increase logging for the Foreman Application:

  1. Set the logging level to debug: 

    # satellite-installer --foreman-logging-level debug
    Copy to Clipboard Toggle word wrap

  2. After you complete debugging, reset the logging level to the default value: 

    # satellite-installer --reset-foreman-logging-level
    Copy to Clipboard Toggle word wrap

For more information about Satellite logging settings, use satellite-installer with the --full-help option: 

# satellite-installer --full-help | grep logging
Copy to Clipboard Toggle word wrap

17.1.2. Increasing the Logging Level for Hammer
Copier lien

You can find the log in ~/.hammer/log/hammer.log.

To increase logging for Hammer:

  • In /etc/hammer/cli_config.yml, set the :log_level: option to debug: 
:log_level: 'debug'
Copy to Clipboard Toggle word wrap

17.1.3. Increasing the Logging Level for Capsule
Copier lien

You can find the log in /var/log/foreman-proxy/proxy.log.

To increase logging for Capsule:

  1. Set the logging level to debug: 

    # satellite-installer --foreman-proxy-log-level DEBUG
    Copy to Clipboard Toggle word wrap

  2. After you complete debugging, reset the logging level to the default value: 

    # satellite-installer --reset-foreman-proxy-log-level
    Copy to Clipboard Toggle word wrap
Note

Running satellite-installer will revert the setting back to default.

17.1.4. Increasing the Logging Level for Candlepin
Copier lien

You can find the logs in /var/log/candlepin/candlepin.log and /var/log/candlepin/error.log.

To increase logging for Candlepin:

  1. In /etc/candlepin/candlepin.conf, set the logging level to DEBUG: 

    log4j.logger.org.candlepin=DEBUG
    Copy to Clipboard Toggle word wrap

  2. Restart the tomcat service: 

    # systemctl restart tomcat
    Copy to Clipboard Toggle word wrap

If the candlepin log files are too verbose, you can decrease the default debug level: 

log4j.logger.org.candlepin.resource.ConsumerResource=WARN
log4j.logger.org.candlepin.resource.HypervisorResource=WARN
Copy to Clipboard Toggle word wrap

17.1.5. Increasing the Logging Level for Qpid Dispatch Router
Copier lien

Qpid logs to syslog. You can view the log in /var/log/messages or with journalctl.

To increase logging for Qpid Dispatch Router:

  1. In /etc/qpid-dispatch/qdrouterd.conf, set the logging level to debug: 

    enable: debug+
    Copy to Clipboard Toggle word wrap

  2. Restart the Qpid Dispatch Router: 

    # systemctl restart qdrouterd
    Copy to Clipboard Toggle word wrap
Note

Running satellite-installer will revert the setting to default.

17.1.6. Increasing the Logging Level For Qpid Broker
Copier lien

Qpid logs to syslog. You can view the log in /var/log/messages or with journalctl.

To increase logging for Qpid Broker:

  1. In /etc/qpid/qpidd.conf, set the logging level to debug: 

    log-enable=debug+
    Copy to Clipboard Toggle word wrap

  2. Restart Qpid Broker: 

    # systemctl restart qpidd
    Copy to Clipboard Toggle word wrap
Note

Running satellite-installer will revert the setting to default.

17.1.7. Increasing the Logging Level For Redis
Copier lien

You can find the log for Redis in /var/log/redis/redis.log.

To increase logging for Redis:

  1. In /etc/redis.conf, set the logging level to debug: 

    loglevel debug
    Copy to Clipboard Toggle word wrap

  2. Restart the Redis service: 

    # systemctl restart redis
    Copy to Clipboard Toggle word wrap
Note

Running satellite-installer will revert the setting to default.

17.1.8. Increasing the Logging Level For Satellite Installer
Copier lien

You can find the log files in /var/log/foreman-installer/.

To increase the logging level of the Satellite installer, add the --verbose-log-level debug option during the installation: 

# satellite-installer --verbose-log-level debug
Copy to Clipboard Toggle word wrap

17.1.9. Increasing the Logging Level For Pulp
Copier lien

By default, Pulp logs to syslog. You can view the log in /var/log/messages or with journalctl.

To increase logging for Pulp:

  1. In /etc/pulp/settings.py, set the logging level to DEBUG: 

    LOGGING = {"dynaconf_merge": True, "loggers": {'': {'handlers': ['console'], 'level': 'DEBUG'}}}
    Copy to Clipboard Toggle word wrap

  2. Restart the Pulp services: 

    # systemctl restart \
pulpcore-api \
pulpcore-content \
pulpcore-resource-manager \
pulpcore-worker@1 \
pulpcore-worker@2 \
redis
    Copy to Clipboard Toggle word wrap

17.1.10. Increasing the Logging Level For Puppet Agent
Copier lien

You can find the logs in /var/log/puppetlabs/puppet/.

To increase logging for Puppet agent:

  1. Ensure Puppet is enabled in your Satellite. For more information, see Enabling Puppet Integration with Satellite in Managing Configurations Using Puppet Integration in Red Hat Satellite.

  2. Set the logging level to debug: 

    # satellite-installer --puppet-agent-additional-settings log_level:debug
    Copy to Clipboard Toggle word wrap

17.1.11. Increasing the Logging Level For Puppet Server
Copier lien

You can find the logs in /var/log/puppetlabs/puppetserver/.

To increase logging for Puppet server:

  1. Ensure Puppet is enabled in your Satellite. For more information, see Enabling Puppet Integration with Satellite in Managing Configurations Using Puppet Integration in Red Hat Satellite.

  2. Set the logging level to debug: 

    # satellite-installer --puppet-server-additional-settings log_level:debug
    Copy to Clipboard Toggle word wrap

  3. Restart the Puppet server: 

    # satellite-maintain service restart --only puppetserver
    Copy to Clipboard Toggle word wrap

17.2. Configuring Logging Levels with Hammer CLI
Copier lien

You can use Hammer to log debugging information for various Satellite components. The default logging level is INFO.

  • To list the components whose logging level you can change by using hammer: 

    # hammer admin logging --list
    Copy to Clipboard Toggle word wrap

  • To set DEBUG level logging for all components: 

    # hammer admin logging --all --level-debug
# satellite-maintain service restart
    Copy to Clipboard Toggle word wrap

  • To set PRODUCTION level logging for all components: 

    # hammer admin logging --all --level-production
# satellite-maintain service restart
    Copy to Clipboard Toggle word wrap

  • To set DEBUG level logging for a specific component: 

    # hammer admin logging --components My_Component --level-debug
# satellite-maintain service restart
    Copy to Clipboard Toggle word wrap

  • To list all available logging options: 

    # hammer admin logging --help
    Copy to Clipboard Toggle word wrap

17.3. Configuring Logging to Journal or File-based Logging
Copier lien

Satellite uses file-based logging by default. You can use the satellite-installer command to reconfigure logging.

Procedure for configuring logging with Journal

  1. Enter the following satellite-installer command to configure logging to the journald service: 

    # satellite-installer \
--foreman-logging-layout pattern \
--foreman-logging-type journald \
--foreman-proxy-log JOURNAL
    Copy to Clipboard Toggle word wrap

  2. Optional: To inspect the log messages, use the journalctl utility. For example:

    • journalctl --unit foreman and journalctl --unit foreman-proxy show messages for the foreman and foreman-proxy units
    • journalctl REQUEST=request_ID shows messages for a specified request

Procedure for configuring file-based logging

  1. Enter the following satellite-installer command to configure file-based logging: 

    # satellite-installer \
--reset-foreman-logging-layout \
--reset-foreman-logging-type \
--reset-foreman-proxy-log
    Copy to Clipboard Toggle word wrap

  2. Optional: To inspect the log messages, view these files:

    • /var/log/foreman/production.log
    • /var/log/foreman-proxy.log

Additional resources

For more information about Journal, see Viewing logs using the command line in the Red Hat Enterprise Linux 8 Configuring Basic System Settings Guide.

17.4. Selective Debugging with Individual Loggers
Copier lien

You can enable individual loggers for selective debugging.

Procedure

  1. Enable the required individual loggers. For example, to enable sql and ldap loggers, enter the following command: 

    # satellite-installer \
--foreman-loggers ldap:true \
--foreman-loggers sql:true
    Copy to Clipboard Toggle word wrap

  2. Optional: Reset all loggers to their default values: 

    # satellite-installer --reset-foreman-loggers
    Copy to Clipboard Toggle word wrap

17.5. Overview of Individual Loggers
Copier lien

The following list provides an overview of selected loggers. You can find the complete list of loggers with their default values in /usr/share/foreman/config/application.rb under Foreman::Logging.add_loggers.

app

Logs web requests and all general application messages.

Default value: true.

audit

Logs additional fact statistics, numbers of added, updated, and removed facts.

Default value: true.

background
Logs information from the background processing component.
blob

Logs contents of rendered templates for auditing purposes.

Important

The blob logger might contain sensitive data.

dynflow
Logs information from the Dynflow process.
ldap

Logs high level LDAP queries and LDAP operations.

Default value: false.

notifications
Logs information from the notifications component.
permissions

Logs queries to user roles, filters, and permissions when loading pages.

Default value: false.

sql

Logs SQL queries made through Rails ActiveRecord.

Default value: false.

telemetry
Logs debugging information from telemetry.
templates
Logs information from the template renderer component.

17.6. Retrieving the Status of Services
Copier lien

Satellite uses a set of back-end services. When troubleshooting, you can check the status of Satellite services.

Procedure

  • In the Satellite web UI, navigate to Administer > About.

    • On the Smart Proxies tab, view the status of all Capsules.
    • On the Compute Resources tab, view the status of attached compute resource providers.
    • In the Backend System Status table, view the status of all back-end services.

CLI procedure

  • Get information from the database and Satellite services: 

    # hammer ping
    Copy to Clipboard Toggle word wrap

  • Check the status of the services running in systemd: 

    # satellite-maintain service status
    Copy to Clipboard Toggle word wrap

    Run satellite-maintain service --help for more information.

  • Perform a health check: 

    $ satellite-maintain health check
    Copy to Clipboard Toggle word wrap

    Run satellite-maintain health --help for more information.

17.7. Restarting Services
Copier lien

Satellite uses a set of back-end services. When troubleshooting, you can restart the services if needed.

Procedure

  • Restart Satellite services: 

    # satellite-maintain service restart
    Copy to Clipboard Toggle word wrap

17.8. Utilities for Processing Log Information
Copier lien

You can collect information from log files to troubleshoot Satellite.

sosreport

The sosreport command collects configuration and diagnostic information from a Linux system, such as the running Kernel version, loaded modules, running services, and system and service configuration files. This output is stored in a tar file located at /var/tmp/sosreport-XXX-20171002230919.tar.xz.

For more information, run sosreport --help or see What is a sosreport and how can I create one?.

Important

The sosreport command removes security information such as passwords, tokens, and keys while collecting information. However, the tar files can still contain sensitive information about the Satellite Server. Send the tar files directly to the intended recipient and not to a public target.

foreman-tail

The foreman-tail command displays Satellite logs in real time.

For more information, see the foreman-tail(8) man page.

17.9. Log File Directories
Copier lien

The following table provides an overview of selected log directories on Satellite Server:

Expand
Log file directoryDescription of log file content

/var/log/candlepin/

Subscription management

/var/log/foreman-installer/

Installer

/var/log/foreman-maintain/

Foreman maintain

/var/log/foreman-proxy/

Foreman proxy

/var/log/foreman/

Foreman

/var/log/httpd/

Apache HTTP server

/var/log/messages/

Various other log messages

/var/log/puppetlabs/puppet/

Puppet

/var/log/tomcat/

Candlepin web service logs

17.10. System Journal Metadata
Copier lien

The following table lists metadata that the journald service uses in Satellite. You can use this metadata to filter your queries.

AUDIT_ACTION

Audit action performed

Example: Create, update, or delete

AUDIT_TYPE

Audit resource type

Example: Host, Subnet, or ContentView

AUDIT_ID
Audit resource database ID as a number
AUDIT_ATTRIBUTE
Audit resource field or an updated database column
AUDIT_FIELD_OLD
Old audit value of an update action
AUDIT_FIELD_NEW
New audit value of an update action
AUDIT_ID
Record database ID of the audit subject
AUDIT_ATTRIBUTE

Attribute name or column on which an action was performed

Example: Name or description

EXCEPTION_MESSAGE
Exception message when error is logged
EXCEPTION_CLASS
Exception Ruby class when error is logged
EXCEPTION_BACKTRACE
Exception backtrace as a multiline string when error is logged
LOC_ID
Location database ID
LOC_NAME
Location name
LOC_LABEL
Location label
LOGGER

Logger name

To see the current list of loggers enabled by default, enter this command: 

# awk '/add_loggers/,/^$/' /usr/share/foreman/config/application.rb
Copy to Clipboard Toggle word wrap
ORG_ID
Organization database ID
ORG_NAME
Organization name
ORG_LABEL
Organization label
REMOTE_IP
Remote IP address of a client
REQUEST
Request ID generated by the Action Dispatch module
SESSION
Random ID generated per session or a request for a sessionless request
TEMPLATE_NAME
Template name
TEMPLATE_DIGEST
Digest (SHA256) of rendered template contents
TEMPLATE_HOST_NAME
Host name for a rendered template if present
TEMPLATE_HOST_ID
Host database ID for a rendered template if present
USER_LOGIN
User login name
Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat