Red Hat Bugzilla – Bug 1031715
bacula bconsole pruning messages - wrong date calculation
Last modified: 2016-07-22 04:40:26 EDT
Description of problem: I am getting a few messages from bacula like:
18-Nov 05:06 bacula.ops.impresa.pt JobId 1080: Begin pruning Jobs older than 43 years 5 months 2 days 5 hours 6 mins 13 secs.
18-Nov 05:06 bacula.ops.impresa.pt JobId 1080: No Jobs found to prune.
18-Nov 05:06 bacula.ops.impresa.pt JobId 1080: Begin pruning Jobs.
18-Nov 05:06 bacula.ops.impresa.pt JobId 1080: No Files found to prune.
18-Nov 05:06 bacula.ops.impresa.pt JobId 1080: End auto prune.
While searching on the internet I got this link which suggests this might have been fixed in 5.0.1. If this verifies is it possible to consider na update to 5.0.1 or backport fix? I'm available to help testing.
Version-Release number of selected component (if applicable): 5.0.0-12
How reproducible: Always
Steps to Reproduce: Run bconsole/bat and check console output; Same on jobs.
Actual results: Values are not right and no recycle/pruning
Expected results: Values should be realistic and recycle/pruning working
Name = ENV_QA
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 8 days
LabelFormat = "ENV_QA_"
Maximum Volumes = 9
RecyclePool = ENV_QA
Not really sure if this is related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573178
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.
This issue is fixed in Red Hat Enterprise Linux version 7.