Specify what should be considered a Warning/Critical

61 views

Skip to first unread message

Cookiefamily

unread,

Jul 16, 2019, 1:53:34 PM7/16/19

to bareos-users

Hello,
I have a few VMs that have a directory excluded in the Fileset that sometimes exists, sometimes doesn't.
But when it doesn't exist, I get a "ERR=No such file or directory" which causes the backup job to exit with "Warning".

For my monitoring scripts it would be handy if those errors don't cause a Warning and are just on the Info-level.

Is there any way to exclude certain errors or give them a different "priority" (Info, Warning, Critical)?

Andreas Rogge

unread,

Jul 17, 2019, 2:44:19 AM7/17/19

to bareos...@googlegroups.com

Am 16.07.19 um 19:53 schrieb Cookiefamily:

While there is no option to set the warning level here, we should
probably discuss whether excluding a non-exisitant directory should
generate a warning.

Best Regards,
Andreas

--
Andreas Rogge andrea...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221-630693-86
http://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz