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.
Bug 1013897 - logconv.pl uses /var/tmp for BDB temp files
Summary: logconv.pl uses /var/tmp for BDB temp files
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On: 1013163
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-01 02:20 UTC by Nathan Kinder
Modified: 2020-09-13 20:44 UTC (History)
4 users (show)

Fixed In Version: 389-ds-base-1.3.1.6-5.el7
Doc Type: Bug Fix
Doc Text:
Cause: Using the -D argument to logconv.pl is supposed to use the given directory to create the temporary files. logconv.pl was writing a large amount of data in files in /var/tmp instead of the argument given to -D. Consequence: Could fill /var/tmp. Fix: The Berkeley DB tied perl arrays were causing this behavior. The fix is to get rid of arrays as much as possible, and get rid of all tied arrays. Result: /var/tmp is not in danger of filling up, the directory specified with -D is used, performance is much faster, disk usage is much less.
Clone Of: 1013163
Environment:
Last Closed: 2014-06-13 11:07:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 838 0 None None None 2020-09-13 20:44:34 UTC

Description Nathan Kinder 2013-10-01 02:20:43 UTC 
+++ This bug was initially created as a clone of Bug #1013163 +++

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47501

Not sure why, but using logconv.pl -V with DB_File creates temporary DB files in /var/tmp called BDBxxxxx.  These can grow to be very, very large.  They need to go in the -D $dataLocation directory.
Comment 2 srkrishn@redhat.com 2014-02-05 12:00:28 UTC 
hi,
i verified the logconv.pl -D option and the script creates the temp files in the directory following -D option and not in the /var/tmp directory.
the access log file is a customer log file.

the command was as follows
logconv.pl -D /RHEL7/data/DS/6.0/logfile/en/stat /RHEL7/data/DS/6.0/logfile/en/access.20120131-000045

this was tested on the latest build.
Comment 3 Sankar Ramalingam 2014-02-13 11:51:28 UTC 
Test cases automated in ./logfile/logconv.sh
Comment 4 Sankar Ramalingam 2014-02-14 15:54:22 UTC 
Marking the bug as Verified as per comment #2
Comment 5 Ludek Smid 2014-06-13 11:07:09 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.