RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 rh-issues@redhat.com 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", 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 1056573 - Messages generated by rsyslog itself are not forwarded to journald
Summary: Messages generated by rsyslog itself are not forwarded to journald
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rsyslog
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Radovan Sroka
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-22 13:45 UTC by Tomas Heinrich
Modified: 2017-03-24 12:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-24 12:58:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Heinrich 2014-01-22 13:45:26 UTC
Description of problem:
rsyslog pulls most of the external messages from journald, but the messages generated by rsyslog itself are not forwarded back to journald. This means that users relying solely on journald are going to miss these messages.

Version-Release number of selected component (if applicable):
rsyslog-7.4.7-3.el7

Steps to Reproduce:
Actual results:
$ grep 'rsyslogd-3003.*foo' /var/log/messages
Jan 22 08:38:51 rhel-7 rsyslogd-3003: invalid or yet-unknown config file command 'foo' - have you forgotten to load a module? [try http://www.rsyslog.com/e/3003 ]
$ journalctl | grep foo

Expected results:
$ journalctl | grep foo
Jan 22 08:38:51 rhel-7 rsyslogd[1268]: invalid or yet-unknown config file command 'foo' - have you forgotten to load a module? [try http://www.rsyslog.com/e/3003 ]

Additional info:
This would probably employ the omjournal module and some additional filtering in imjournal (see imuxsock for inspiration).


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