Red Hat SummitAppendix 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
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”.
For more information about Satellite logging settings, use satellite-installer with the --full-help option:
# satellite-installer --full-help | grep loggingProcedure
Set the logging level to
debug:# satellite-installer --foreman-logging-level debugAfter you complete debugging, reset the logging level to the default value:
# satellite-installer --reset-foreman-logging-level
B.2. Increasing the logging level for Red Hat Lightspeed in Satellite
You can increase the logging levels for Red Hat Lightspeed in Satellite to DEBUG to get more detailed logs. You can find the logs in /var/log/messages.
Example B.1. Log entries of Red Hat Lightspeed in Satellite
Feb 3 10:39:54 satellite.example.com iop-core-engine[213708]: INFO:insights.core.dr:Trying telemetry.rules.plugins.sap.sap_hana_loose_sudo.check_group_members
Feb 3 10:39:54 satellite.example.com iop-core-engine[213708]: INFO:insights.core.dr:Trying telemetry.rules.plugins.sap.sap_hana_loose_sudo.report
Feb 3 10:39:54 satellite.example.com iop-core-engine[213708]: INFO:insights.core.dr:Trying telemetry.rules.plugins.ros.ros_instance_evaluation.find_solution
Feb 3 10:39:54 satellite.example.com iop-core-engine[213708]: INFO:insights.core.dr:Trying telemetry.rules.plugins.ros.ros_instance_evaluation.report
Feb 3 10:39:54 satellite.example.com iop-core-engine[213708]: INFO:insights_kafka_service.consumer:Completed processing request id 4be0099772a23aad477e493990247876
Feb 3 10:39:54 satellite.example.com iop-core-engine[213708]: INFO:insights_messaging.consumers.kafka:Completed one payloadThe default logging levels for Red Hat Lightspeed in Satellite are as follows:
loggers:
insights.core.dr:
level: "ERROR"
insights_messaging:
level: "INFO"
insights_kafka_service:
level: "INFO"
"":
level: "INFO"Prerequisites
You have installed Red Hat Lightspeed in Satellite on your Satellite Server. For more information, see the following resources:
- Installing and configuring Red Hat Lightspeed in Satellite in Installing Satellite Server in a connected network environment
- Installing and configuring Red Hat Lightspeed in Satellite in Installing Satellite Server in a disconnected network environment
Procedure
Increase the logging levels to
DEBUG:# satellite-installer \ --iop-core-engine-log-level-insights-core-dr DEBUG \ --iop-core-engine-log-level-insights-kafka-service DEBUG \ --iop-core-engine-log-level-insights-messaging DEBUG \ --iop-core-engine-log-level-root DEBUG
Verification
Check the logging levels of Red Hat Lightspeed in Satellite:
# podman exec iop-core-engine cat /var/config.yml | grep -A15 "logging:"
B.3. Increasing the logging level for Hammer
You can find the log in ~/.hammer/log/hammer.log.
Procedure
In
/etc/hammer/cli_config.yml, set the:log_level:option todebug::log_level: 'debug'
B.4. Increasing the logging level for Capsule
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
Set the logging level to
debug:# satellite-installer --foreman-proxy-log-level DEBUGAfter you complete debugging, reset the logging level to the default value:
# satellite-installer --reset-foreman-proxy-log-level
B.5. Increasing the logging level for Candlepin
You can find the logs in /var/log/candlepin/candlepin.log and /var/log/candlepin/error.log.
Procedure
Set the logging level to
DEBUG:# satellite-installer --katello-candlepin-loggers log4j.logger.org.candlepin:DEBUGIf 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:WARNAfter you complete debugging, reset the logging level to the default value:
# satellite-installer --reset-katello-candlepin-loggers
B.6. Increasing the logging level for Redis
You can find the log for Redis in /var/log/redis/redis.log.
Procedure
In
/etc/redis/redis.conf, set the logging level todebug:loglevel debugRestart the Redis service:
# systemctl restart redisNoteRunning
satellite-installerwill revert the setting to default.
B.7. Increasing the logging level for satellite-installer
satellite-installer writes logs to /var/log/foreman-installer/.
Procedure
Increase the logging level of the
satellite-installerutility:# satellite-installer --verbose-log-level debugNote that this only affects standard output but not any log files written to disk.
B.8. Increasing the logging level for Pulp
Pulp logs to the systemd journal. You can view the logs using journalctl --unit 'pulpcore*'.
Procedure
In
/etc/pulp/settings.py, set the logging level toDEBUG:LOGGING = {"dynaconf_merge": True, "loggers": {'': {'handlers': ['console'], 'level': 'DEBUG'}}}Restart the Pulp services:
# systemctl restart \ pulpcore-api \ pulpcore-content \ pulpcore-resource-manager \ pulpcore-worker@\*NoteRunning
satellite-installerwill revert the setting to default.
B.9. Increasing the logging level for OpenVox agent
You can find the logs in /var/log/puppetlabs/puppet/.
Prerequisites
- You have enabled Puppet on your Satellite. For more information, see Enabling Puppet integration with Satellite in Managing configurations by using Puppet integration.
Procedure
Set the logging level to
debug:# satellite-installer --puppet-agent-additional-settings log_level:debug
B.10. Increasing the logging level for OpenVox server
You can find the logs in /var/log/puppetlabs/puppetserver/.
Prerequisites
- You have enabled Puppet on your Satellite. For more information, see Enabling Puppet integration with Satellite in Managing configurations by using Puppet integration.
Procedure
Set the logging level to
debug:# satellite-installer --puppet-server-additional-settings log_level:debug
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}