OK. This is the right url of 1.1.4 http://communities.quest.com/docs/DOC-9191

As I suspected the 2nd problem was actually a matter of capital vs small letter. The correct response from the cmd script from windows regarding the logical disks is "Ok" not "OK". So within this section "REM Extract the status of each logical volume REM -----------------------------------------"

I changed these to "Ok" IF NOT "!_log_result!"=="Ok" SET _status=red IF NOT "!_log_result!"=="Ok" SET _message="At least one logical volume is in a failure state." SET _ministatus=green IF NOT "!_log_result!"=="Ok" SET _ministatus=red

So, now remains point 1 as it will not load the cmd script. It is supposed to execute on a 5 min interval (for testing purposes).

I'll dig.

Please, if anyone can help, I would be grateful. Thank you

On Fri, Jul 19, 2013 at 2:58 PM, Gonzalez Peto <jkokino at gmail.com> wrote:

I forgot to add:

On the server side, I have xymon 4.2.3 and I just added "# raid" after the hostname entry I want to monitor in bb-hosts

On Fri, Jul 19, 2013 at 2:57 PM, Gonzalez Peto <jkokino at gmail.com> wrote:

...

Hello

I read many posts about raid, hp raid and etc. http://lists.xymon.com/archive/2010-February/027413.html

This pages says CheckHpRaid 1.1.4: http://developer.sysco.ch/hobbit/ http://developer.sysco.ch/hobbit/CheckHpRaid.cmd When I open it, it is 1.1.3

I found 1.1.4 @ http://xymonton.org/ and works well however I dont know how to completely make it automatic

Few issues:

1. It seems that the cmd file will not be leaded automatically. If I execute it manually, then all is ok, and the xymon server receives this info. Then it will not receive more automatically. I placed the cmd file in C:\Program Files\BBWin\ext
   I also tried by placing the cmd file in the root folder I edited the the BBWIN.cfg file <load value="cmd /c C:\CheckHpRaid_1.1.4.cmd" timer="5m"/> or <load value="cmd /c CheckHpRaid_1.1.4.cmd" timer="5m"/>

I took cmd /c from the bbwin manual chm file which comes with 0.12 version

2. Second problem is that the logical disk is reported ok and all individual physical disk are ok, and yet I get color red for the logical disk. :) I am still trying to figure the source code where the if cases and statuses are wrong? And of course it says "At least one logical volume is in a failure state."

Is anyone able to help? Specially the first question - point 1. The other one I think I will figure it out sooner or later.

Thank you

FYI, in my experience you can generally specify a path relative to the BBWin bin folder as shown below. This is nice if you still have a mix of 32- and 64-bit systems, or have BBWin installed in different locations for some reason, etc.

<load value='cmd /c "..\ext\CheckHpRaid.cmd"' timer="3h"/>

Cheers.

From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of Gonzalez Peto Sent: Friday, July 19, 2013 9:13 AM To: xymon at xymon.com Subject: Re: [Xymon] raid bbwin monitoring

Brilliant. The path was incorrect when I went into debug mode for bbwin.exe This is the correct: <load value='cmd /c "C:\Program Files\BBWin\ext\CheckHpRaid.cmd"' timer="3h"/> <load value='cmd /c "C:\Program Files (x86)\BBWin\ext\CheckHpRaid.cmd"' timer="3h"/>

Credits to Ray. Thank you http://lists.xymon.com/archive/2009-August/025750.html

On Fri, Jul 19, 2013 at 3:20 PM, Gonzalez Peto <jkokino at gmail.com<mailto:jkokino at gmail.com>> wrote: OK. This is the right url of 1.1.4 http://communities.quest.com/docs/DOC-9191

As I suspected the 2nd problem was actually a matter of capital vs small letter. The correct response from the cmd script from windows regarding the logical disks is "Ok" not "OK". So within this section "REM Extract the status of each logical volume REM -----------------------------------------"

I changed these to "Ok" IF NOT "!_log_result!"=="Ok" SET _status=red IF NOT "!_log_result!"=="Ok" SET _message="At least one logical volume is in a failure state." SET _ministatus=green IF NOT "!_log_result!"=="Ok" SET _ministatus=red

So, now remains point 1 as it will not load the cmd script. It is supposed to execute on a 5 min interval (for testing purposes).

I'll dig.

Please, if anyone can help, I would be grateful. Thank you

On Fri, Jul 19, 2013 at 2:58 PM, Gonzalez Peto <jkokino at gmail.com<mailto:jkokino at gmail.com>> wrote: I forgot to add:

On the server side, I have xymon 4.2.3 and I just added "# raid" after the hostname entry I want to monitor in bb-hosts

On Fri, Jul 19, 2013 at 2:57 PM, Gonzalez Peto <jkokino at gmail.com<mailto:jkokino at gmail.com>> wrote: Hello

I read many posts about raid, hp raid and etc. http://lists.xymon.com/archive/2010-February/027413.html

This pages says CheckHpRaid 1.1.4: http://developer.sysco.ch/hobbit/ http://developer.sysco.ch/hobbit/CheckHpRaid.cmd When I open it, it is 1.1.3

I found 1.1.4 @ http://xymonton.org/ and works well however I dont know how to completely make it automatic

Few issues:

1. It seems that the cmd file will not be leaded automatically. If I execute it manually, then all is ok, and the xymon server receives this info. Then it will not receive more automatically. I placed the cmd file in C:\Program Files\BBWin\ext
   I also tried by placing the cmd file in the root folder I edited the the BBWIN.cfg file <load value="cmd /c C:\CheckHpRaid_1.1.4.cmd" timer="5m"/> or <load value="cmd /c CheckHpRaid_1.1.4.cmd" timer="5m"/>

I took cmd /c from the bbwin manual chm file which comes with 0.12 version

2. Second problem is that the logical disk is reported ok and all individual physical disk are ok, and yet I get color red for the logical disk. :) I am still trying to figure the source code where the if cases and statuses are wrong? And of course it says "At least one logical volume is in a failure state."

Is anyone able to help? Specially the first question - point 1. The other one I think I will figure it out sooner or later.

Thank you

On 22 July 2013 22:59, Gonzalez Peto <jkokino at gmail.com> wrote:

One question: Do you go in bb-services and define raid as a service like [raid] and nothing else?

No, bb-services is for something different. It's used for defining your own bbnet/xymonnet protocols for testing. For example, you might want to monitor some new service listening on port 19283, and to do a little conversation to make sure you get the correct result. To do this, you define the protocol and port in the bb-services file. (In Xymon, this file is called protocols.cfg.)

In this case, "raid" is not a network test, and so doesn't need anything in bb-services.

Because I am not able to make the mail alert working while all other alerts in similar fashion do work.

This is what I try: PAGE=testpage SERVICE=raid MAIL email[at]address.com COLOR=red REPEAT=1m

PAGE=testpage SERVICE=conn MAIL email2[at]address.com DURATION>2m REPEAT=1 RECOVERED

The "SERVICE" in the alerts file has a different meaning to "service" used in the "bb-services" filename. If the "raid" dot on your Xymon "testpage" screen goes red, then it should trigger an email as you have configured above.

The second on works, the first one doesnt. So, since raid is not in my

bb-services file, then it is not a service per se, so I wonder how do I define it? Whether this is the correct way?

It's defined dynamically when the message comes from the client. You don't need to do anything.

I tested with: .././bin/bbcmd hobbitd_alert --test foo raid

Tells me it will fire email which is ok. However, it doesnt fire email in reality 00027264 2013-07-22 14:57:07 Matching host:service:page 'foo:raid:testpage' against rule line 62 00027264 2013-07-22 14:57:07 *** Match with 'PAGE=testpage SERVICE=raid'

---

00027264 2013-07-22 14:57:07 Matching host:service:page 'foo:raid:testpage' against rule line 64 00027264 2013-07-22 14:57:07 *** Match with 'MAIL email[at]address.comCOLOR=red REPEAT=1m' *** 00027264 2013-07-22 14:57:07 Mail alert with command 'mail -s "Hobbit [12345] foo:raid CRITICAL (RED)" email[at]address.com'

Looks OK to me.

Do you folks have any idea where to read/look? examples?

No, sorry. I'm not very experienced with alerting. However, the fact that you tacked this question onto what was essentially another thread probably means that nobody is going to read it. People who have no experience with BBWin are more likely to skip the entire thread. As your alerting issue is unrelated to BBWin, you might get a better response if you start a new thread.

J