Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1163020 - [RFE|TRACKER] Add systemd journal/systemd support
Summary: [RFE|TRACKER] Add systemd journal/systemd support
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Logging
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: 6.6.0
Assignee: Lukas Zapletal
QA Contact: Stephen Wadeley
: 1196754 1305013 (view as bug list)
Depends On:
Blocks: 1296845
TreeView+ depends on / blocked
Reported: 2014-11-12 09:01 UTC by Lukas Zapletal
Modified: 2019-12-16 05:21 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2019-10-22 12:46:40 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 8360 0 Normal Duplicate Full journald support 2020-09-23 21:21:37 UTC
Red Hat Knowledge Base (Solution) 2077723 0 None None None 2019-12-16 05:21:48 UTC
Red Hat Product Errata RHSA-2019:3172 0 None None None 2019-10-22 12:47:01 UTC

Description Lukas Zapletal 2014-11-12 09:01:10 UTC
On RHEL7 we should leverage journald sending all the logs there for:

- foreman core app
- plugins (katello, candlepin, pulp)
- foreman proxies
- cron jobs (using systemd-cat)

When possible, we should send logging levels properly as well, so users are able to leverage fine-grained filtering system in journald (WARN, ERROR, DEBUG, TRACE).

Let's also make sure that timestamps are correctly sent and we leverage all the journald goodies.

Comment 1 RHEL Program Management 2014-11-12 09:23:34 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Bryan Kearney 2015-04-17 18:08:21 UTC
*** Bug 1196754 has been marked as a duplicate of this bug. ***

Comment 4 Bryan Kearney 2015-08-25 18:32:36 UTC
Upstream bug component is Packaging

Comment 5 Bryan Kearney 2016-08-02 20:04:52 UTC
Upstream bug component is Packaging

Comment 7 Bryan Kearney 2016-08-04 20:19:03 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 8 Eric Helms 2016-12-16 16:31:08 UTC

Would you consider this BZ and to be duplicates? If no, can you clarify the differences? If yes, can we keep the most appropriate one and close the other as a dupe.

Comment 9 Lukas Zapletal 2016-12-19 09:11:37 UTC
Yeah, I renamed this one a bit, the goal is really to send this to (a logging) daemon avoiding own logrotating/rolling/restarting.

Comment 10 Lukas Zapletal 2016-12-19 09:12:04 UTC
*** Bug 1305013 has been marked as a duplicate of this bug. ***

Comment 11 Satellite Program 2018-03-29 14:22:19 UTC
Upstream bug assigned to lzap

Comment 12 Satellite Program 2018-04-30 18:21:10 UTC
Upstream bug assigned to lzap

Comment 14 Lukas Zapletal 2018-06-25 07:47:31 UTC
Closing, we implemented this in upstream but in Satellite we are going to document and go towards integrating with rsyslog rather than with journald for 3rd party logging. Good to have the feature for the future.

Comment 17 Lukas Zapletal 2019-06-28 06:40:37 UTC
Patrick, this is just a tracker for 6.6 feature "improve common logging". I am going to slip it to ON_QA and assign Stephen here, I believe this is already VERIFIED.

Details how to set things up are:

Comment 18 Stephen Wadeley 2019-08-07 14:03:40 UTC

lzap explained to me:

by default
foreman core (rails) writes to  /var/log/foreman/production.log and smart proxy writes to /var/log/foreman-proxy/proxy.log

to use journald, which will forward logs to rsyslog and then write to /var/log/messages, you need to run:

satellite-installer --foreman-logging-level info --foreman-logging-type journald \
  --foreman-logging-layout pattern --foreman-proxy-log JOURNAL

systemctl restart httpd


the `--foreman-logging-type journald` option installs foreman-journald

but package foreman-proxy-journald was not installed, I expected --foreman-proxy-log JOURNAL to pull it in. We can document that, raise another bug.

Before installing as above, I could 

hammer host list (to check foreman core)
tail -f /var/log/foreman/production.log
019-08-07T15:09:05 [I|app|a0ce4328] Started GET "/api/hosts?page=1&per_page=1000" for at 2019-08-07 15:09:05 +0200
2019-08-07T15:09:05 [I|app|a0ce4328] Processing by Api::V2::HostsController#index as JSON
2019-08-07T15:09:05 [I|app|a0ce4328]   Parameters: {"page"=>"1", "per_page"=>"1000", "apiv"=>"v2", "host"=>{}}

After installing as above I could:

hammer host list (to check foreman core)
journalctl --follow
Aug 07 15:39:56 foreman[21356]: Started GET "/api/hosts?page=1&per_page=1000" for at 2019-08-07 15:39:56 +0200
Aug 07 15:39:56 foreman[21356]: Processing by Api::V2::HostsController#index as JSON
Aug 07 15:39:56 foreman[21356]:   Parameters: {"page"=>"1", "per_page"=>"1000", "apiv"=>"v2", "host"=>{}}

I also set SyncIntervalSec=10 and then did systemctl daemon-reload to reduce the wait time.

Thank you

Comment 19 Stephen Wadeley 2019-08-08 09:51:20 UTC

Bug 1738784 - foreman-proxy-log JOURNAL option should install foreman-proxy-journald

DocsBug Bug 1738850 - Logging to journald and rsyslog

Comment 21 errata-xmlrpc 2019-10-22 12:46:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

Note You need to log in before you can comment on or make changes to this bug.