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 1060385 - Logconv.pl with an empty access log gives lots of errors
Summary: Logconv.pl with an empty access log gives lots of errors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: 6.6
Assignee: Rich Megginson
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On:
Blocks: 1108872
TreeView+ depends on / blocked
 
Reported: 2014-02-01 02:14 UTC by Sankar Ramalingam
Modified: 2020-09-13 20:57 UTC (History)
6 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-34.el6
Doc Type: Bug Fix
Doc Text:
Cause: Trying to process an empty log file Consequence: The script fails to run, and reports a series of Perl errors. Fix: Check and ignore empty log files Result: The script can correctly identify and handle an empty log file.
Clone Of:
: 1108872 (view as bug list)
Environment:
Last Closed: 2014-10-14 07:52:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1048 0 None None None 2020-09-13 20:57:52 UTC
Red Hat Product Errata RHBA-2014:1385 0 normal SHIPPED_LIVE 389-ds-base bug fix and enhancement update 2014-10-14 01:27:42 UTC

Description Sankar Ramalingam 2014-02-01 02:14:51 UTC 
Description of problem: Running logconv.pl tool on the empty access log file gives lots of errors.


Version-Release number of selected component (if applicable): 389-ds-base-1.3.1.6-15


How reproducible: Consistently with the empty access log files.


Steps to Reproduce:
1. Create an instance and empty the access log file.
2. Run logconv.pl tool to check if -M option is working.
3. logconv.pl -m -M /var/log/dirsrv/slapd-testinst/access


Actual results:
logconv.pl -m -M /var/log/dirsrv/slapd-testinst/access

Access Log Analyzer 8.0

Command: logconv.pl /var/log/dirsrv/slapd-testinst/access

Processing 1 Access Log(s)...

[00] /var/log/dirsrv/slapd-testinst/access	size (bytes):            0
Use of uninitialized value $_ in pattern match (m//) at /usr/bin/logconv.pl line 1595.
Use of uninitialized value $_ in pattern match (m//) at /usr/bin/logconv.pl line 1600.
Use of uninitialized value $_ in pattern match (m//) at /usr/bin/logconv.pl line 1606.
Use of uninitialized value $_ in split at /usr/bin/logconv.pl line 1623.
Use of uninitialized value $time in substitution (s///) at /usr/bin/logconv.pl line 1627.
Use of uninitialized value $tzone in substitution (s///) at /usr/bin/logconv.pl line 1628.
Use of uninitialized value $tzone in pattern match (m//) at /usr/bin/logconv.pl line 1634.
Use of uninitialized value $hr in multiplication (*) at /usr/bin/logconv.pl line 1635.
Use of uninitialized value $min in multiplication (*) at /usr/bin/logconv.pl line 1635.
Use of uninitialized value $sign in string eq at /usr/bin/logconv.pl line 1636.
Use of uninitialized value $time in split at /usr/bin/logconv.pl line 1640.
Use of uninitialized value $date in split at /usr/bin/logconv.pl line 1641.
Use of uninitialized value $mon in hash element at /usr/bin/logconv.pl line 1642.
Use of uninitialized value in scalar assignment at /usr/share/perl5/vendor_perl/Carp.pm line 182.
Day '' out of range 1..31 at /usr/bin/logconv.pl line 1642.



Expected results:


Additional info:
Comment 2 Noriko Hosoi 2014-02-20 18:21:40 UTC 
Upstream ticket:
https://fedorahosted.org/389/ticket/47713
Comment 4 mreynolds 2014-05-27 18:54:58 UTC 
Fixed upstream.



Verification steps:

[1]  Create empty log file:

     # touch /tmp/access

[2]  Run logconv

     # logconv.pl /tmp/access    

[3]  There should not be any Perl errors, and the script should report the empty log file:  "Skipping empty access log (/tmp/access)..."
Comment 7 srkrishn@redhat.com 2014-07-22 12:00:56 UTC 
This bug has been verified as shown below:

[root@hp-ms-01-c04 ~]# touch /tmp/access3
[root@hp-ms-01-c04 ~]# logconv.pl /tmp/access3
Access Log Analyzer 8.0
Command: logconv.pl /tmp/access3
Processing 1 Access Log(s)...
[001] /tmp/access3                  	size (bytes):            0
Skipping empty access log (/tmp/access3)...
There was no logging to process, exiting...
Cleaning up temp files...
Done.


This was tested on build number:1.2.11.15-38-389-ds-base
Comment 8 Sankar Ramalingam 2014-07-31 10:13:37 UTC 
Marking the bug as Verified, based on the previous comment from Sriram,
Comment 9 errata-xmlrpc 2014-10-14 07:52:58 UTC 
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.

http://rhn.redhat.com/errata/RHBA-2014-1385.html
Note You need to log in before you can comment on or make changes to this bug.