Bug 1108872

Summary: Logconv.pl with an empty access log gives lots of errors
Product: Red Hat Enterprise Linux 7 Reporter: Noriko Hosoi <nhosoi>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: medium Docs Contact:
Priority: low    
Version: 7.1CC: mreynolds, nhosoi, nkinder, rmeggins, sramling
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: 389-ds-base- 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.
Story Points: ---
Clone Of: 1060385 Environment:
Last Closed: 2015-03-05 09:35:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1060385    
Bug Blocks:    

Comment 2 Sankar Ramalingam 2015-01-07 13:45:07 UTC
Running logconv with empty access log files doesn't throw any error. Hence, marking the bug as Verified.

[root@mgmt9 ~]# logconv.pl -efcibaltnxrgjuyp -s 10 -V /tmp/access 
Access Log Analyzer 8.1
Command: logconv.pl /tmp/access
Processing 1 Access Log(s)...

[001] /tmp/access                   	size (bytes):            0
Skipping empty access log (/tmp/access)...
There was no logging to process, exiting...
Cleaning up temp files...

Comment 4 errata-xmlrpc 2015-03-05 09:35:03 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.