New client-side external script to monitor Bacula backup server with Xymon
list Bill Arlofski
The script is a simple (and a little ugly) Bash shell script that uses Bacula's bconsole "status dir" command output to see if any jobs are waiting on operator intervention, and it also checks the last "x" number of jobs to see if any of them failed and reports both instances back to a Xymon monitoring server. For those who do not know, Bacula is an open-source, enterprise network backup system that is widely used. It may be found here: http://www.bacula.org/ I wrote the script a while back but modified it today to include checking for "intervention required" type issues. An entry for the script has been added to Xymonton (http://xymonton.trantor.org/doku.php/monitors#available_monitors), and may be found here: http://www.revpol.com/xymon_bacula_check_script There are currently no instructions on installing it, but they will be up shortly. Basic instructions for installing such a script may be found in the Xymon man pages as well. Hope this helps someone somewhere. :) (I cross-posted a similar notice to the bacula-users mailing list today) -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/
list Josh Luthman
You are awesome. Thank you for sharing and documenting! Josh Luthman Office: XXX-XXX-XXXX Direct: XXX-XXX-XXXX XXXX Wayne St Suite XXXX Troy, OH XXXXX “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill
▸
On Fri, Jun 4, 2010 at 2:27 PM, Bill Arlofski <user-0b8af203a56e@xymon.invalid> wrote:The script is a simple (and a little ugly) Bash shell script that uses Bacula's bconsole "status dir" command output to see if any jobs are waiting on operator intervention, and it also checks the last "x" number of jobs to see if any of them failed and reports both instances back to a Xymon monitoring server. For those who do not know, Bacula is an open-source, enterprise network backup system that is widely used. It may be found here: http://www.bacula.org/ I wrote the script a while back but modified it today to include checking for "intervention required" type issues. An entry for the script has been added to Xymonton (http://xymonton.trantor.org/doku.php/monitors#available_monitors), and may be found here: http://www.revpol.com/xymon_bacula_check_script There are currently no instructions on installing it, but they will be up shortly. Basic instructions for installing such a script may be found in the Xymon man pages as well. Hope this helps someone somewhere. :) (I cross-posted a similar notice to the bacula-users mailing list today) -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/
list Patrick Nixon
Installed! On Fri, Jun 4, 2010 at 2:36 PM, Josh Luthman
▸
<user-4c45a83f15cb@xymon.invalid> wrote:You are awesome. Thank you for sharing and documenting! Josh Luthman Office: XXX-XXX-XXXX Direct: XXX-XXX-XXXX XXXX Wayne St Suite XXXX Troy, OH XXXXX “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill On Fri, Jun 4, 2010 at 2:27 PM, Bill Arlofski <user-0b8af203a56e@xymon.invalid> wrote:The script is a simple (and a little ugly) Bash shell script that uses Bacula's bconsole "status dir" command output to see if any jobs are waiting on operator intervention, and it also checks the last "x" number of jobs to see if any of them failed and reports both instances back to a Xymon monitoring server. For those who do not know, Bacula is an open-source, enterprise network backup system that is widely used. It may be found here: http://www.bacula.org/ I wrote the script a while back but modified it today to include checking for "intervention required" type issues. An entry for the script has been added to Xymonton (http://xymonton.trantor.org/doku.php/monitors#available_monitors), and may be found here: http://www.revpol.com/xymon_bacula_check_script There are currently no instructions on installing it, but they will be up shortly. Basic instructions for installing such a script may be found in the Xymon man pages as well. Hope this helps someone somewhere. :) (I cross-posted a similar notice to the bacula-users mailing list today) -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/
list Bill Arlofski
▸
On 06/07/10 16:07, Patrick Nixon wrote:
Installed! On Fri, Jun 4, 2010 at 2:36 PM, Josh Luthman <user-4c45a83f15cb@xymon.invalid> wrote:You are awesome. Thank you for sharing and documenting! Josh Luthman
Hi Josh, Patrick! Glad to see my efforts have helped someone! :) Just wanted to comment that the part of the script where it runs the bconsole "status dir" command will surely require a little "tuning" depending on your environment and requirements. On the initial, hurried posting of that script I was incorrectly grepping for "is waiting on" OR "mount" which would of course catch things like "is waiting on storage..." and "is waiting on max client jobs..." and probably a few others. Surely these are cases that may occur in an environment where there are many clients, and/or many jobs running simultaneously and might not represent an issue that needs attention. I plan on making the status messages being grepped a variable in the next update so they are easily modified and not obscured/blended into the script itself. -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/
list Patrick Nixon
It's unlikely I'm ever going to run into those errors as we do backup to disk :) I did add a $GREP -v "You have messages." to the end of the list jobs line, because I think I saw it come across in one of the updates. --Patrick
▸
On Tue, Jun 8, 2010 at 11:11 AM, Bill Arlofski <user-4210565d0a80@xymon.invalid> wrote:On 06/07/10 16:07, Patrick Nixon wrote:Installed! On Fri, Jun 4, 2010 at 2:36 PM, Josh Luthman <user-4c45a83f15cb@xymon.invalid> wrote:You are awesome. Thank you for sharing and documenting! Josh LuthmanHi Josh, Patrick! Glad to see my efforts have helped someone! :) Just wanted to comment that the part of the script where it runs the bconsole "status dir" command will surely require a little "tuning" depending on your environment and requirements. On the initial, hurried posting of that script I was incorrectly grepping for "is waiting on" OR "mount" which would of course catch things like "is waiting on storage..." and "is waiting on max client jobs..." and probably a few others. Surely these are cases that may occur in an environment where there are many clients, and/or many jobs running simultaneously and might not represent an issue that needs attention. I plan on making the status messages being grepped a variable in the next update so they are easily modified and not obscured/blended into the script itself. -- Bill Arlofski Reverse Polarity, LLC http://www.revpol.com/