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 1329246 - systemd-journal-remote fills filesystem quickly
Summary: systemd-journal-remote fills filesystem quickly
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-21 13:25 UTC by Martin Stefany
Modified: 2020-12-15 07:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:41:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Martin Stefany 2016-04-21 13:25:36 UTC 
Description of problem:
systemd-journal-remote is basically unusable:
 - when receiving logs it fills the filesystem (512 MiB) too quickly, weird rotation of journal happens, filesystem limits (default or configured) are not honored and service+socket shortly fail
   - issue is reported upstream https://github.com/systemd/systemd/issues/1387
 - using --compress doesn't help much
 - example:
$ sudo systemctl start systemd-journal-remote.socket
$ sudo journalctl -D /var/log/journal/remote/ | wc -l
68523
$ du -h /var/log/journal/remote/
102M    /var/log/journal/remote/
...
$ sudo journalctl -D /var/log/journal/remote/ | wc -l
68547
$ du -h /var/log/journal/remote/
115M    /var/log/journal/remote/
... etc.


Version-Release number of selected component (if applicable):
systemd-journal-gateway-219-19.el7_2.7.x86_64

How reproducible:
Always

Steps to Reproduce:
Configure systemd-journal-upload to send logs to systemd-journal-remote, including necessary fixes as mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1327303 and notice filesystem fill up too quickly compared to minimal amount of messages.

Actual results:
Filesystem is filled up quickly, bad rotation of journal happens and service+socket shortly fail.

Expected results:
systemd-journal-remote should receive messages from systemd-journal-upload, honor default or configured limits, and rotate remote journal files.

Additional info:
https://github.com/systemd/systemd/issues/1387
Comment 4 RHEL Program Management 2020-12-15 07:41:10 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.