Bug 1397606

Summary: Limit Journalctl journal to 200MB by default
Product: [Fedora] Fedora Reporter: Josh Berkus <jberkus>
Component: fedora-productimg-atomicAssignee: Colin Walters <walters>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 34CC: nekohayo, walters
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-08 01:07: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:

Description Josh Berkus 2016-11-23 00:05:42 UTC
Description of problem:

By default, the size of the journal on new Atomic Hosts is unlimited.  Since Kubernetes produces a LOT of log output, this can cause the journal to baloon up to several GB in size, and as a result run the root volume out of disk space.

Version-Release number of selected component (if applicable):

Fedora Atomic 25, but affects all versions.

How reproducible:

100%

Steps to Reproduce:
1.  Deploy a new Fedora Atomic system
2. Install Kubernetes on it
3. Run it for a few days
4. Journal will grow to over 2GB in size

Actual results:

Journal grows indefinitely, becoming several GB in size.


Desired results:

The Journal should cap at some resonable size, like 200MB.

Recommended solution:

Set SystemMaxUse to 200MB in the default journald.conf file.

Comment 1 Fedora End Of Life 2017-11-16 19:40:09 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-12-12 10:26:16 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Jean-François Fortin Tam 2021-01-29 02:40:55 UTC
Reopening as this has been an eternal thorn in my feet for all the Fedora Workstation machines I maintain, which typically have 10 to 15 GB for the / partition (used to be 7-10 GB, but that's hard to fit in these days with PackageKit and localization files eating tons of space).

Not sure the component is right though, shouldn't this be "journalctl", as it also affects Workstation and I suppose many other usecases?

Comment 4 Jean-François Fortin Tam 2021-01-29 14:49:42 UTC
Upstream bug at https://github.com/systemd/systemd/issues/17382#issuecomment-769836118 but I can't actually link it here because it makes RH Bugzilla crash/traceback.

Comment 5 Ben Cotton 2021-02-09 16:14:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 6 Ben Cotton 2022-05-12 16:42:48 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 7 Ben Cotton 2022-06-08 01:07:10 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.