Hello William, On Wed, 29 Jan 2020 at 17:55, William Muriithi <will...@perasotech.com> wrote:
> Hello, > > Was trying to reduce the number of mails coming from Bacula, and was > combing through the logs to see what I can filter out. Currently, almost > all noise comes from bacula attempting to schedule a job and then realizing > the previous isn't yet done. I have configured bacula not to allow > duplicates to avoid jobs piling up in case I miss replacing tapes when all > are full. You can easily change the Message resource to not notify about all events, the documentation does provide good examples for this. > > > Anyway as I was doing so, I noticed that, sometime, bacula do consider > duplicate fatal? How would this make sense considering it was > intentionally configured? Kind of confused by these instances. You need to use the “Allow duplicate job” option in your job(s) configuration. > > > 22-Jan 17:50 bacula-dir JobId 25338: Fatal error: JobId 25266 already > running. Duplicate job not allowed. > > Regards, > William > If you still need help, you can share excerpt of your configuration in this thread so we can see what could be missing. Hope it helps Best, Davide > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users >
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
