Bug 1329246

Summary:	systemd-journal-remote fills filesystem quickly
Product:	Red Hat Enterprise Linux 7	Reporter:	Martin Stefany <martin>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED WONTFIX	QA Contact:	qe-baseos-daemons
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	dani-rh, john.petrucci, martin, systemd-maint-list
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 07:41:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.