From: Mantis B. T. <no...@bu...> - 2009-11-29 21:58:38
|
The following issue has been SUBMITTED. ====================================================================== http://bugs.bacula.org/view.php?id=1428 ====================================================================== Reported By: neuvti Assigned To: ====================================================================== Project: bacula Issue ID: 1428 Category: rpms Reproducibility: always Severity: minor Priority: normal Status: new ====================================================================== Date Submitted: 2009-11-29 21:58 UTC Last Modified: 2009-11-29 21:58 UTC ====================================================================== Summary: applybaculadate- logwatch script missing / not found Description: There aren't official Bacula 3.0.3 rpms for RHEL/CentOS yet, so the one I'm using is self-built binaries from the official srpm. Since updating from 3.0.2, I started getting these messages to root's mail: ---- /etc/cron.daily/0logwatch: Cannot find shared script applybaculadate ---- After some investigation, I noticed that 3.0.2 (and obviously its predecessors) had had this file stucture under /etc/log.d: [root@garfield etc]# tree -D log.d/ log.d/ |-- [Jan 28 2009] conf | |-- [Jul 31 10:15] logfiles | | `-- [Jul 31 0:21] bacula.conf | `-- [Jul 31 10:15] services | `-- [Jul 14 22:10] bacula.conf `-- [Jan 28 2009] scripts `-- [Jul 31 10:15] services `-- [Jul 14 22:10] bacula In 3.0.3 these files above got moved to /etc/logwatch: [root@garfield etc]# tree -D logwatch/ logwatch/ |-- [Nov 22 19:33] conf | |-- [May 24 2008] ignore.conf | |-- [Nov 22 19:39] logfiles | | `-- [Nov 22 19:39] bacula.conf | |-- [May 24 2008] logwatch.conf | |-- [May 24 2008] override.conf | `-- [Nov 22 19:34] services | `-- [Oct 18 12:10] bacula.conf `-- [Nov 22 2:06] scripts `-- [Nov 22 19:32] services `-- [Oct 18 12:10] bacula This obviously was a correct (but not adequate) change, since the files seem to be logwatch-related. Previously, I had never seen any bacula-relates stuff in the daily logwatch output. The error message quoted above is obviously due to the last row of /etc/logwatch/conf/services/bacula.conf: ---- Title = "bacula" # Which logfile group... LogFile = bacula *ApplyBaculaDate = ---- I don't know the internals of logwatch, but after a couple of trial-and-errors I noticed that commenting out that last line of /etc/logwatch/conf/services/bacula.conf made the daily error message mail disappear, and the next logwatch run included a long history of completed bacula jobs. Sounds very much perfect but... Now, that quick and dirty fix of mine obviously wasn't enough, because every day the logwatch output contains the full history of all the jobs that cand be found in the current (non-rotated) log file. So, the original logwatch message for missing "applybaculadate" script seems still to be valid, it obviously contains some mechanism to control that the same jobs won't get reported repeatedly. ====================================================================== Issue History Date Modified Username Field Change ====================================================================== 2009-11-29 21:58 neuvti New Issue ====================================================================== |