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.

Description of problem:
Given Red Hat forces systemd-journal by default, please also add support
for systemd-journal to logwatch (backport).

Version-Release number of selected component (if applicable):
logwatch-7.4.0-32.20130522svn140.el7.noarch

How reproducible:
Run logwatch on a system without rsyslog but with systemd-journal.

Actual results:
No support for systemd-journal at logwatch.

Expected results:
Support for systemd-journal at logwatch.

Additional info:
See also bug #864872 and http://pkgs.fedoraproject.org/cgit/rpms/logwatch.git/commit/?id=bf7f580f8f7ef791153be84b9e00fc5c6a9f3a0c for a possible patch

Cross-filed ticket 01957073 on the Red Hat customer portal.

(In reply to Robert Scheck from comment #0)
> Description of problem:
> Given Red Hat forces systemd-journal by default...

That's not true. RHEL7 installations don't use journal by default.

> How reproducible:
> Run logwatch on a system without rsyslog but with systemd-journal.

This contradicts the "Red Hat forces...". You changed the default.

> Expected results:
> Support for systemd-journal at logwatch.

Yes, backporting those patches is trivial.

(In reply to Jan Synacek from comment #3)
> That's not true. RHEL7 installations don't use journal by default.

A RHEL 7 standard installation has journald by default, at least journalctl
contains more information than rsyslog logs, but it's not persistent, yes. I
guess that is what you meant.

> Yes, backporting those patches is trivial.

Thanks! :)

Testing package can be found at https://jsynacek.fedorapeople.org/logwatch/logwatch-7.4.0-34.20130522svn140.el7.bz1504984.noarch.rpm.

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.

https://access.redhat.com/errata/RHBA-2018:0822