Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
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:


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.