View Issue Details

IDProjectCategoryView StatusLast Update
0014837CentOS-7systemdpublic2018-06-19 18:46
ReporterHubbitus 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformLinuxOSCentosOS Version7-4.1708
Product Version7.4.1708 
Target VersionFixed in Version 
Summary0014837: Journald does not honor journal size limits
DescriptionWe use docker, which by default write logs into journald.

To limit space used for logs it configured like:

# cat /etc/systemd/journald.conf
...
[Journal]
Storage=persistent
Compress=True
Seal=True
SplitMode=none
SyncIntervalSec=5m
RateLimitInterval=30s
RateLimitBurst=1000
SystemMaxUse=256M
SystemKeepFree=4G
SystemMaxFileSize=128M
RuntimeMaxUse=256M
RuntimeKeepFree=4G
RuntimeMaxFileSize=128M
MaxRetentionSec=0
MaxFileSec=7day
ForwardToSyslog=True
ForwardToKMsg=False
ForwardToConsole=False
ForwardToWall=True
TTYPath=/dev/console
MaxLevelStore=info
MaxLevelSyslog=info
MaxLevelKMsg=notice
MaxLevelConsole=info
MaxLevelWall=emerg


I expect what it can't get more than 256Mb according to setting `SystemMaxUse=256M`.

Journald itself report exactly same size:
# journalctl --disk-usage
Archived and active journals take up 256.1M on disk.

And do not clean anything off course:
# journalctl --vacuum-size=256M
Vacuuming done, freed 0B of archived journals on disk.

But in reality got much more space:
# du -sh /var/log/journal/
1.5G /var/log/journal/

Verification by `journalctl --verify` does not show any error.
Tagssystemd
abrt_hash
URL

Activities

Hubbitus

Hubbitus

2018-06-19 18:46

reporter   ~0032115

Could someone please look on it?

Issue History

Date Modified Username Field Change
2018-05-18 13:53 Hubbitus New Issue
2018-05-18 13:53 Hubbitus Tag Attached: systemd
2018-06-19 18:46 Hubbitus Note Added: 0032115