Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1691011 - RFE - limit the number of retries for systemd-tmpfiles-clean
Summary: RFE - limit the number of retries for systemd-tmpfiles-clean
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd
Version: 7.6
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: systemd-maint
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-20 16:11 UTC by mlinden
Modified: 2019-03-21 07:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-21 07:51:23 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description mlinden 2019-03-20 16:11:53 UTC
Description of problem:

Systemd didn't have enough memory to start its tmpfiles-cleanup job it keep trying over and over until the logs where filled with the same error message

Feb 1 10:08:21 server systemd[1]: Failed to fork: Cannot allocate memory
Feb 1 10:08:21 server systemd[1]: systemd-tmpfiles-clean.service failed to run 'start' task: Cannot allocate memory
Feb 1 10:08:21 server systemd[1]: Failed to start Cleanup of Temporary Directories.
Feb 1 10:08:21 server systemd[1]: Unit systemd-tmpfiles-clean.service entered failed state.
Feb 1 10:08:21 server systemd[1]: systemd-tmpfiles-clean.service failed.
Feb 1 10:08:21 server systemd[1]: Starting Cleanup of Temporary Directories...

Could we limit the amount of times this runs with StartLimitIntervalSec=interval and StartLimitBurst=burst ?
As its rescheduled to run daily anyway, it should try X number of times and if that does not work, wait until next scheduled time.

Comment 2 Jan Synacek 2019-03-21 07:51:23 UTC
This is definitely not RHEL-7 material any more. Please, file an upstream issue first and if it gets accepted and implemented, we could perhaps try to backport the patch(es) to RHEL-8.


Note You need to log in before you can comment on or make changes to this bug.