[Bacula-users] Monitoring bacula with Nagios
Folks, Does anyone have any tips for montioring Bacula with Nagios? Ideally I was thinking of connecting to the sockets and doing a hello to make sure it was happy. I haven't been able to find any plugings and tinking with the protocol there seems to be some non printing characters which makes it a little tricky to write my own. Any other suggestions for achiving it? Mike. signature.asc Description: Digital signature -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Monitoring bacula with Nagios
In the message dated: Thu, 26 Mar 2009 23:21:53 -, The pithy ruminations from Mike on <[Bacula-users] Monitoring bacula with Nagios> were: => => => Folks, => => Does anyone have any tips for montioring Bacula with Nagios? Yes. => => Ideally I was thinking of connecting to the sockets and doing a hello to => make sure it was happy. I haven't been able to find any plugings and => tinking with the protocol there seems to be some non printing characters => which makes it a little tricky to write my own. => => Any other suggestions for achiving it? Sure. I'm using the Nagios "nrpe" facility to have the nagios server issue calls to each client to run the nagios "check_procs" command, looking for the presence of the process "bacula-fd". You can do similar things to check for the bacula-sd and bacula-dir daemons. Here are some config file snippets: ===nagios server=== checkcommands.cfg command_line/usr/lib/nagios/check_nrpe -H $HOSTADDRESS$ -c check_bacula-fd -t 20 ===backup client=== nrpe.cfg command[check_bacula-fd]=/usr/local/nagios/libexec/check_procs -C bacula-fd -c 1: -w :2 => => Mike. => Mark Bergman voice: 215-662-7310 mark.berg...@uphs.upenn.edu fax: 215-614-0266 System Administrator Section of Biomedical Image Analysis Department of RadiologyUniversity of Pennsylvania PGP Key: https://www.rad.upenn.edu/sbia/bergman The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Monitoring bacula with Nagios
I found a check_bacula plugin somewhere - I think on nagiosexchange. It looks at the bacula log files for the last day, and issues a warning if any backups have failed. It also reports on the total number of backups. It's far from perfect (the warning state always remains exactly until midnight, for instance) but for the time being is useful enough for me. And it is a perl script, so it should be easy enough to customize. The copyright notice for that plugin says "Guy Van Sanden" and gives the URL http://nocturn.vbsnet.be Mike wrote: > Folks, > > Does anyone have any tips for montioring Bacula with Nagios? > > Ideally I was thinking of connecting to the sockets and doing a hello to > make sure it was happy. I haven't been able to find any plugings and > tinking with the protocol there seems to be some non printing characters > which makes it a little tricky to write my own. > > Any other suggestions for achiving it? > > Mike. > -- Kevin Keane Owner The NetTech Find the Uncommon: Expert Solutions for a Network You Never Have to Think About Office: 866-642-7116 http://www.4nettech.com This e-mail and attachments, if any, may contain confidential and/or proprietary information. Please be advised that the unauthorized use or disclosure of the information is strictly prohibited. The information herein is intended only for use by the intended recipient(s) named above. If you have received this transmission in error, please notify the sender immediately and permanently delete the e-mail and any copies, printouts or attachments thereof. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Monitoring bacula with Nagios
Hello Mike, have you already downloaded the source (.tar.gz) of Bacula? In it's bacula-2.x.x/examples/nagios you'll find everything you wish :-) christian -- "I sense much NT in you, NT leads to Blue Screen. Blue Screen leads to downtime, downtime leads to suffering. NT is the path to the darkside." - Unknown Unix Jedi > -Original Message- > From: Mike [mailto:m...@csits.net] > Sent: Friday, March 27, 2009 12:22 AM > To: bacula-users@lists.sourceforge.net > Subject: [Bacula-users] Monitoring bacula with Nagios > > Folks, > > Does anyone have any tips for montioring Bacula with Nagios? > > Ideally I was thinking of connecting to the sockets and doing > a hello to > make sure it was happy. I haven't been able to find any plugings and > tinking with the protocol there seems to be some non printing > characters > which makes it a little tricky to write my own. > > Any other suggestions for achiving it? > > Mike. > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Monitoring bacula with Nagios
> Folks, > > Does anyone have any tips for montioring Bacula with Nagios? > > I focus mainly on using "Run After Job"'s to run a script for send_nsca. In my case, the primary concern is that the jobs run, run without errors, and are complete by the time I think they should be (I monitor the general health of the Bacula servers with NRPE). Passive checks with a freshness threshold accomplish that for us. Marc. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Monitoring bacula with Nagios
We've done the most basic setup here, we use check_procs and look for bacula. If the process dies, it'll bitch. This way we usually catch problems before they happen. If bacula is just not happy in general, we'll know by the next morning with a failed / error backup job. Charlie On Mar 26, 2009, at 6:21 PM, Mike wrote: > Folks, > > Does anyone have any tips for montioring Bacula with Nagios? > > Ideally I was thinking of connecting to the sockets and doing a > hello to > make sure it was happy. I haven't been able to find any plugings and > tinking with the protocol there seems to be some non printing > characters > which makes it a little tricky to write my own. > > Any other suggestions for achiving it? > > Mike. > -- > ___ > 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
Re: [Bacula-users] Monitoring bacula with Nagios
On Fri, Mar 27, 2009 at 11:09 AM, Charlie Reddington wrote: > We've done the most basic setup here, we use check_procs and look for > bacula. If the process dies, it'll bitch. This way we usually catch > problems before they happen. > Have you ever seen bacula die? I mean in 5 years of using bacula on 35 to 50 machines I do not recall ever seeing bacula die. John -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Monitoring bacula with Nagios
On Fri, Mar 27, 2009 at 11:47 AM, John Drescher wrote: > On Fri, Mar 27, 2009 at 11:09 AM, Charlie Reddington > wrote: >> We've done the most basic setup here, we use check_procs and look for >> bacula. If the process dies, it'll bitch. This way we usually catch >> problems before they happen. >> > Have you ever seen bacula die? I mean in 5 years of using bacula on 35 > to 50 machines I do not recall ever seeing bacula die. > Ahh. Maybe once there was a bug in the storage daemon but that was very long ago. John -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Monitoring bacula with Nagios
>>> We've done the most basic setup here, we use check_procs and look for >>> bacula. If the process dies, it'll bitch. This way we usually catch >>> problems before they happen. >>> >> Have you ever seen bacula die? I mean in 5 years of using bacula on 35 >> to 50 machines I do not recall ever seeing bacula die. >> > Ahh. Maybe once there was a bug in the storage daemon but that was > very long ago. > Now I remember bat used to crash bacula-dir all the time on long queries as a result I do not use bat on the work network.. John -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Monitoring bacula with Nagios
Yep! The client side did. On Mar 27, 2009, at 10:48 AM, John Drescher wrote: > On Fri, Mar 27, 2009 at 11:47 AM, John Drescher > wrote: >> On Fri, Mar 27, 2009 at 11:09 AM, Charlie Reddington >> wrote: >>> We've done the most basic setup here, we use check_procs and look >>> for >>> bacula. If the process dies, it'll bitch. This way we usually catch >>> problems before they happen. >>> >> Have you ever seen bacula die? I mean in 5 years of using bacula on >> 35 >> to 50 machines I do not recall ever seeing bacula die. >> > Ahh. Maybe once there was a bug in the storage daemon but that was > very long ago. > > John -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Monitoring bacula with Nagios
On Fri, 27 Mar 2009, John Drescher wrote: > Have you ever seen bacula die? I mean in 5 years of using bacula on 35 > to 50 machines I do not recall ever seeing bacula die. Yep; storage daemon (2.4.2) dies on me about once a month. I get a file daemon failure about once a month too, but of course there's a lot more of those. Incidentally, when the file daemon dies, the job sits in the "waiting for FD to connect" state forever. The director has to be restarted, otherwise no further jobs start. Steve -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
