Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionTakayoshi Kimura
2018-01-16 02:53:44 UTC
Description of problem:
Disk is getting full because docker journald log driver keeps file descriptors to deleted /var/log/journal/*/*.journal files.
The following command shows a lot of deleted file descriptors.
# find /proc/*/fd -ls | grep '(deleted)'
854653876 0 lr-x------ 1 root root 64 Jan 15 19:52 /proc/8004/fd/6793 -> /var/log/journal/aab77f0af404433695f49265761415c7/system\ (deleted)
854653877 0 lr-x------ 1 root root 64 Jan 15 19:52 /proc/8004/fd/6794 -> /var/log/journal/aab77f0af404433695f49265761415c7/system\ (deleted)
854653879 0 lr-x------ 1 root root 64 Jan 15 19:52 /proc/8004/fd/6796 -> /var/log/journal/aab77f0af404433695f49265761415c7/system\ (deleted)
Version-Release number of selected component (if applicable):
docker-1.12.6-55
docker-1.12.6-68
How reproducible:
Always when running a lot of containers
Steps to Reproduce:
1.
2.
3.
Actual results:
Disk full due to deleted journal files
Expected results:
Journal files deleted and free disk space
Additional info:
Upstream issue: https://github.com/moby/moby/issues/27343
To workaround, truncate the deleted files manually in a cron job:
# cd /proc/`pidof dockerd-current`/fd
# ls -l |grep var.log.journal |grep deleted.$ |awk '{print $9}' |while read x; do :> $x; done;
Is it docker code that is doing this? Or is this really the systemd journal API interfaces doing this? The reason to ask is because we seem the same behavior with rsyslog configured to use imjournal.
It looks like the journal reading logic in dockerd isn't handling SD_JOURNAL_INVALIDATE status results from sd_journal_process(), which would be a good time for it to close and reopen the handle that it's using to follow the journal as entries get added to it. A patch to handle that shouldn't be very large.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0436
This issue still exists in docker-1.13.1-103.git7f2769b
I'm using the truncate deleted files workaround, at the moment, but upstream now has recently fixed this in https://github.com/moby/moby/pull/38859
Can this be backported?