Red Hat Summit Red Hat SummitApoyoConsolaDesarrolladoresIniciar una pruebaContacto

Este contenido no está disponible en el idioma seleccionado.

Appendix B. Increasing logging levels of Satellite components

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

B.1. Increasing the logging level for Foreman
Copiar enlace

By default, you can find the log in /var/log/foreman/production.log. For more information, see Section A.2, “Configuring logging type and layout”.

Note

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

Procedure

  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

B.2. Increasing the logging level for Hammer
Copiar enlace

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

Procedure

  • In /etc/hammer/cli_config.yml, set the :log_level: option to debug: 

    :log_level: 'debug'
    Copy to Clipboard Toggle word wrap

B.3. Increasing the logging level for Capsule
Copiar enlace

By default, you can find the log in /var/log/foreman-proxy/proxy.log. For more information, see Section A.2, “Configuring logging type and layout”.

Procedure

  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

B.4. Increasing the logging level for Candlepin
Copiar enlace

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

Procedure

  1. Set the logging level to DEBUG: 

    # satellite-installer --katello-candlepin-loggers log4j.logger.org.candlepin:DEBUG
    Copy to Clipboard Toggle word wrap

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

    # satellite-installer \
--katello-candlepin-loggers log4j.logger.org.candlepin:DEBUG \
--katello-candlepin-loggers log4j.logger.org.candlepin.resource.ConsumerResource:WARN \
--katello-candlepin-loggers log4j.logger.org.candlepin.resource.HypervisorResource:WARN
    Copy to Clipboard Toggle word wrap

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

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

B.5. Increasing the logging level for Redis
Copiar enlace

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

Procedure

  1. In /etc/redis/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.

B.6. Increasing the logging level for satellite-installer
Copiar enlace

satellite-installer writes logs to /var/log/foreman-installer/.

Procedure

  • Increase the logging level of the satellite-installer utility: 

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

    Note that this only affects standard output but not any log files written to disk.

B.7. Increasing the logging level for Pulp
Copiar enlace

Pulp logs to the systemd journal. You can view the logs using journalctl --unit 'pulpcore*'.

Procedure

  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@\*
    Copy to Clipboard Toggle word wrap
    Note

    Running satellite-installer will revert the setting to default.

B.8. Increasing the logging level for Puppet agent
Copiar enlace

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

Prerequisites

Procedure

  • Set the logging level to debug: 

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

B.9. Increasing the logging level for Puppet server
Copiar enlace

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

Prerequisites

Procedure

  • Set the logging level to debug: 

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

Aprender

Pruebe, compre y venda

Comunidades

Acerca de la documentación de Red Hat

Ayudamos a los usuarios de Red Hat a innovar y alcanzar sus objetivos con nuestros productos y servicios con contenido en el que pueden confiar. Explore nuestras recientes actualizaciones.

Hacer que el código abierto sea más inclusivo

Red Hat se compromete a reemplazar el lenguaje problemático en nuestro código, documentación y propiedades web. Para más detalles, consulte el Blog de Red Hat.

Acerca de Red Hat

Ofrecemos soluciones reforzadas que facilitan a las empresas trabajar en plataformas y entornos, desde el centro de datos central hasta el perímetro de la red.

Theme

© 2026 Red HatVolver arriba