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.
Description of problem:
During a Workstation install failure (due to an rpm failing to download)
I noticed that /tmp was 100% full due to /tmp/dnf.librepo.log
being 975MB!
Version-Release number of selected component (if applicable):
anaconda-29.19.0.34-1.el8
Steps to Reproduce:
1. Net install of RHEL 8 (Workstation)
2. Look at Diskspace in /tmp partition.
Actual results:
In my case having downloaded about 77% of the packages
I noticed that /tmp was 100% with dnf.librepo.log taking up 975MB!
The file has about 8 million lines with select_next_target!! ;)
Expected results:
/tmp not to overfill during installation.
Additional info:
I am not sure if this is fatal or how reproducible but I thought
I better report it anyway, since it doesn't seem good.
(In reply to Jiri Konecny from comment #2)
> Thanks for the report. It is good to know that the log file could grow so
> large.
>
> I see this as a proposal on DNF to avoid such a grow of the log.
Definitely - seems to me like a debugging message that was left in place by mistake.
originally reported on Fedora/dnf bug 1580022
on RHEL 8 Beta I ended up with > 7 GB DEBUG level lines in dnf.librepo.log:
-rw-r--r--. 1 root root 7376408576 Mar 19 16:20 dnf.librepo.log
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/RHSA-2019:3583