Bug 643932

Summary: logwatch script hard-codes possible date ranges
Product: [Fedora] Fedora EPEL Reporter: Ken Dreyer <ktdreyer>
Component: baculaAssignee: Andreas Thienemann <andreas>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: el5CC: andreas, fschwarz, mmcgrath, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-10 18:37:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ken Dreyer 2010-10-18 14:46:40 UTC 
Description of problem:
The logwatch script in bacula 2.0 only allows for a Range setting of "yesterday", "today", and "all". The main logwatch program in EL5 allows for any string that Date::Manip can parse.


Version-Release number of selected component (if applicable):
logwatch-7.3-8.el5
bacula-director-common-2.0.3-10.el5

Steps to Reproduce:
1. Install bacula and logwatch
2. Set a range in /etc/logwatch/conf/logwatch.conf that is not "yesterday", "today", or "all".
3. run logwatch

  
Actual results:
The logwatch email will contain errors in the Bacula section, like "Use of uninitialized value in string eq at /etc/logwatch/scripts/services/bacula line 74, <STDIN> line 433."

Expected results:
Proper logwatch output for bacula

Additional info:
This was discussed in http://bugs.bacula.org/view.php?id=1315 and fixed in upstream's git 9321c4aea3020df015addaa899cb972796592222. If the EPEL5 maintainers want to stay on 2.0, I think this would be appropriate to backport.
Comment 1 Fedora Update System 2012-07-19 15:04:55 UTC 
bacula-2.4.4-5.el5,bacula-docs-2.4.4-4.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/bacula-2.4.4-5.el5,bacula-docs-2.4.4-4.el5
Comment 2 Fedora Update System 2012-07-19 22:35:17 UTC 
Package bacula-2.4.4-5.el5, bacula-docs-2.4.4-4.el5:
* should fix your issue,
* was pushed to the Fedora EPEL 5 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing bacula-2.4.4-5.el5 bacula-docs-2.4.4-4.el5'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6421/bacula-2.4.4-5.el5,bacula-docs-2.4.4-4.el5
then log in and leave karma (feedback).
Comment 3 Fedora Update System 2012-07-20 08:10:09 UTC 
bacula-2.4.4-6.el5,bacula-docs-2.4.4-4.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/bacula-2.4.4-6.el5,bacula-docs-2.4.4-4.el5
Comment 4 Fedora Update System 2012-07-20 08:14:44 UTC 
bacula-2.4.4-6.el5,bacula-docs-2.4.4-4.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/bacula-2.4.4-6.el5,bacula-docs-2.4.4-4.el5
Comment 5 Fedora Update System 2012-07-26 10:41:29 UTC 
bacula-2.4.4-7.el5 has been submitted as an update for Fedora EPEL 5.
https://admin.fedoraproject.org/updates/bacula-2.4.4-7.el5
Comment 6 Fedora Update System 2012-08-10 18:37:48 UTC 
bacula-2.4.4-7.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.