Xymon Mailing List Archive search

BBWin Ext Scripts after 30min are unavaliable

12 messages in this thread

list Cayo de Moraes · Mon, 8 Jun 2009 15:17:08 +0200 ·
Hi guys,

im monitoring with some external scripts on my BBWin and when i try to set
up the "check time" higher (like one time a day) I noticed that the column
get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the
hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client side?

TIA
list Greg Hubbard · Mon, 8 Jun 2009 13:39:03 +0000 ·
By default, the Hobbit server expects your tests to update at least once every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME" expires with no updates the server marks the test "purple" and sends an alert.

The fix is simple -- in your script you need to send a LIFETIME value when you send your status message.  If you test once every day, you need to calculate LIFETIME as 24 * 60 + some extra in case your test is delayed from some reason.

You can read about this in the man pages for the "bb" command (Xymon communications program).

GLH
quoted from Cayo de Moraes

From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
Sent: Monday, June 08, 2009 8:17 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to set up the "check time" higher (like one time a day) I noticed that the column get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client side?

TIA
list Cayo de Moraes · Tue, 9 Jun 2009 11:06:55 +0200 ·
Hi Greg,

thank you for your support, it gave me the right direction! =D

I found out that this lifetime in the scripts should look like this:

$BB $BBDISP "status+70 $MACHINE.$TEST $COLOR `date` OK"


but the Windows .vbs scripts dont give such parameters back to
hobbit-server... I just dont know how to implement this "status+time" in the
vbs scripts...

another thing is that the column dont get purple but black!


Thanks


2009/6/8 HUBBARD, GREG ((EDS)) <user-54b18961ee8d@xymon.invalid>
quoted from Greg Hubbard
 By default, the Hobbit server expects your tests to update at least once
every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME" expires
with no updates the server marks the test "purple" and sends an alert.

The fix is simple -- in your script you need to send a LIFETIME value when
you send your status message.  If you test once every day, you need to
calculate LIFETIME as 24 * 60 + some extra in case your test is delayed from
some reason.

You can read about this in the man pages for the "bb" command (Xymon
communications program).

GLH

*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Monday, June 08, 2009 8:17 AM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to set
up the "check time" higher (like one time a day) I noticed that the column
get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the
hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client side?

TIA
list Greg Hubbard · Tue, 9 Jun 2009 12:35:58 +0000 ·
Well, that changes things!

First, if the column goes black instead of purple, it means that the agent is trying to do the right thing.  The "black" (or "white") state means "nothing to report" and does not mean up or down.  "Purple" means "no data received before lifetime expired".

So how do the Windows vbs scripts communicate with the remote Hobbit server?  Are you using BBWin, or the Big Brother NT client?
quoted from Cayo de Moraes

GLH

From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
Sent: Tuesday, June 09, 2009 4:07 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi Greg,

thank you for your support, it gave me the right direction! =D

I found out that this lifetime in the scripts should look like this:

$BB $BBDISP "status+70 $MACHINE.$TEST $COLOR `date` OK"


but the Windows .vbs scripts dont give such parameters back to hobbit-server... I just dont know how to implement this "status+time" in the vbs scripts...

another thing is that the column dont get purple but black!


Thanks


2009/6/8 HUBBARD, GREG ((EDS)) <user-54b18961ee8d@xymon.invalid<mailto:user-54b18961ee8d@xymon.invalid>>
signature
By default, the Hobbit server expects your tests to update at least once every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME" expires with no updates the server marks the test "purple" and sends an alert.

The fix is simple -- in your script you need to send a LIFETIME value when you send your status message.  If you test once every day, you need to calculate LIFETIME as 24 * 60 + some extra in case your test is delayed from some reason.

You can read about this in the man pages for the "bb" command (Xymon communications program).

GLH

quoted from Cayo de Moraes
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid<mailto:user-92aec3b3c467@xymon.invalid>]
Sent: Monday, June 08, 2009 8:17 AM
To: user-ae9b8668bcde@xymon.invalid<mailto:user-ae9b8668bcde@xymon.invalid>
Subject: [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to set up the "check time" higher (like one time a day) I noticed that the column get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client side?

TIA
list Graeme A Shea · Wed, 10 Jun 2009 14:51:38 +1000 ·
You have to modify the first line of the script to specify the timeout
(time to purple) eg.

 
"green status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test on
the server "Darth"  have the standard time out

 
"green+2h status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test
on the server "Darth" will timeout in 2 hours.

 
"green+1d status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test
on the server "Darth" will  timeout in 1 day

 
There is (or was) a bug in BBWin in that you have to have data on the
first line after the status or ZyMon generates an error. 

 
Hope this helps

Regards

Graeme
quoted from Cayo de Moraes

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Tuesday, 9 June 2009 7:07 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

 
Hi Greg,

thank you for your support, it gave me the right direction! =D

I found out that this lifetime in the scripts should look like this:

$BB $BBDISP "status+70 $MACHINE.$TEST $COLOR `date` OK"


but the Windows .vbs scripts dont give such parameters back to
hobbit-server... I just dont know how to implement this "status+time" in
the vbs scripts...

another thing is that the column dont get purple but black! 


Thanks


2009/6/8 HUBBARD, GREG ((EDS)) <user-54b18961ee8d@xymon.invalid>

By default, the Hobbit server expects your tests to update at least once
every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME"
expires with no updates the server marks the test "purple" and sends an
alert.

 
The fix is simple -- in your script you need to send a LIFETIME value
when you send your status message.  If you test once every day, you need
to calculate LIFETIME as 24 * 60 + some extra in case your test is
delayed from some reason.

 
You can read about this in the man pages for the "bb" command (Xymon
communications program).

 
GLH

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Monday, June 08, 2009 8:17 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to
set up the "check time" higher (like one time a day) I noticed that the
column get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the
hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client
side?

TIA

 

Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.
list Cayo de Moraes · Wed, 10 Jun 2009 09:08:02 +0200 ·
Thx for the help guys, but its not working...

Im using BBWin and here is my configuration:


ext script:
oOutFile.WriteLine "green+1d" & vbCrLf
    Else
        oOutFile.WriteLine "red+1d" & vbCrLf


logfile from ext script, which is send to Xymon:
green+1d

    testserver running test


my BBWin.cfg looks like this:
<externals>
    <setting name="timer" value="3m" />
    <setting name="logstimer" value="60s" />
    <load value="cscript C:\PROGRA~2\BBWin\ext\testscript.vbs" timer="300m"
/>
</externals>


With this configuration i could get a green status for 43 minutes (instead
of 30) til it got black again... Am I still doing something wrong?

thanks,
Cayo


2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>
quoted from Graeme A Shea
 You have to modify the first line of the script to specify the timeout
(time to purple) eg.


“green status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on the
server “Darth”  have the standard time out


“green+2h status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on
the server “Darth” will timeout in 2 hours.


“green+1d status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on
the server “Darth” will  timeout in 1 day


There is (or was) a bug in BBWin in that you have to have data on the first
line after the status or ZyMon generates an error.


Hope this helps

Regards

Graeme


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Tuesday, 9 June 2009 7:07 PM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable


Hi Greg,

thank you for your support, it gave me the right direction! =D

I found out that this lifetime in the scripts should look like this:

$BB $BBDISP "status+70 $MACHINE.$TEST $COLOR `date` OK"


but the Windows .vbs scripts dont give such parameters back to
hobbit-server... I just dont know how to implement this "status+time" in the
vbs scripts...

another thing is that the column dont get purple but black!


Thanks


 2009/6/8 HUBBARD, GREG ((EDS)) <user-54b18961ee8d@xymon.invalid>

By default, the Hobbit server expects your tests to update at least once
every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME" expires
with no updates the server marks the test "purple" and sends an alert.


The fix is simple -- in your script you need to send a LIFETIME value when
you send your status message.  If you test once every day, you need to
calculate LIFETIME as 24 * 60 + some extra in case your test is delayed from
some reason.


You can read about this in the man pages for the "bb" command (Xymon
communications program).


GLH


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Monday, June 08, 2009 8:17 AM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to set
up the "check time" higher (like one time a day) I noticed that the column
get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the
hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client side?

TIA


*Important - *This email and any attachments may be confidential. If
received in error, please contact us and delete all copies. Before opening
or using attachments check them for viruses and defects. Regardless of any
loss, damage or consequence, whether caused by the negligence of the sender
or not, resulting directly or indirectly from the use of any attached files
our liability is limited to resupplying any affected attachments. Any
representations or opinions expressed are those of the individual sender,
and not necessarily those of the Department of Education and Early Childhood
Development.
list Graeme A Shea · Wed, 10 Jun 2009 17:27:28 +1000 ·
I had to put information in the first line after the status message or
it wouldn't work. Something like

 
"green+24h testserver.test " should work, I add the date and time too.
"green+24h" didn't work for me.
quoted from Cayo de Moraes

 
Regards

 
Graeme

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Wednesday, 10 June 2009 5:08 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

 
Thx for the help guys, but its not working...

Im using BBWin and here is my configuration:


ext script:
oOutFile.WriteLine "green+1d" & vbCrLf
    Else
        oOutFile.WriteLine "red+1d" & vbCrLf


logfile from ext script, which is send to Xymon:
green+1d

    testserver running test


my BBWin.cfg looks like this:
<externals>
    <setting name="timer" value="3m" />
    <setting name="logstimer" value="60s" />
    <load value="cscript C:\PROGRA~2\BBWin\ext\testscript.vbs"
timer="300m" /> 
</externals> 


With this configuration i could get a green status for 43 minutes
(instead of 30) til it got black again... Am I still doing something
wrong? 

thanks,
Cayo


2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

You have to modify the first line of the script to specify the timeout
(time to purple) eg.

 
"green status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test on
the server "Darth"  have the standard time out

 
"green+2h status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test
on the server "Darth" will timeout in 2 hours.

 
"green+1d status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test
on the server "Darth" will  timeout in 1 day

 
There is (or was) a bug in BBWin in that you have to have data on the
first line after the status or ZyMon generates an error. 

 
Hope this helps

Regards

Graeme

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Tuesday, 9 June 2009 7:07 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

 
Hi Greg,

thank you for your support, it gave me the right direction! =D

I found out that this lifetime in the scripts should look like this:

$BB $BBDISP "status+70 $MACHINE.$TEST $COLOR `date` OK"


but the Windows .vbs scripts dont give such parameters back to
hobbit-server... I just dont know how to implement this "status+time" in
the vbs scripts...

another thing is that the column dont get purple but black! 


Thanks


2009/6/8 HUBBARD, GREG ((EDS)) <user-54b18961ee8d@xymon.invalid>

By default, the Hobbit server expects your tests to update at least once
every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME"
expires with no updates the server marks the test "purple" and sends an
alert.

 
The fix is simple -- in your script you need to send a LIFETIME value
when you send your status message.  If you test once every day, you need
to calculate LIFETIME as 24 * 60 + some extra in case your test is
delayed from some reason.

 
You can read about this in the man pages for the "bb" command (Xymon
communications program).

 
GLH

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Monday, June 08, 2009 8:17 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to
set up the "check time" higher (like one time a day) I noticed that the
column get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the
hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client
side?

TIA

 
Important - This email and any attachments may be confidential. If
received in error, please contact us and delete all copies. Before
opening or using attachments check them for viruses and defects.
Regardless of any loss, damage or consequence, whether caused by the
negligence of the sender or not, resulting directly or indirectly from
the use of any attached files our liability is limited to resupplying
any affected attachments. Any representations or opinions expressed are
those of the individual sender, and not necessarily those of the
Department of Education and Early Childhood Development.

 
Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.
list Cayo de Moraes · Wed, 10 Jun 2009 12:46:45 +0200 ·
still not working... now I get this in the page (column "test") -->
Testserver.test

=D

Hobbit seems not to work this parameters out. It simply ignores my green+24
(still black after 30 minuter) and prints the "testserver.test" in the
webpage...


2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>
quoted from Graeme A Shea
 I had to put information in the first line after the status message or it
wouldn’t work. Something like


“green+24h testserver.test “ should work, I add the date and time too.
“green+24h” didn’t work for me.


Regards


Graeme


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Wednesday, 10 June 2009 5:08 PM

*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable


Thx for the help guys, but its not working...

Im using BBWin and here is my configuration:


ext script:
oOutFile.WriteLine "green+1d" & vbCrLf
    Else
        oOutFile.WriteLine "red+1d" & vbCrLf


logfile from ext script, which is send to Xymon:
green+1d

    testserver running test


my BBWin.cfg looks like this:
<externals>
    <setting name="timer" value="3m" />
    <setting name="logstimer" value="60s" />
    <load value="cscript C:\PROGRA~2\BBWin\ext\testscript.vbs" timer="300m"
/>
</externals>


With this configuration i could get a green status for 43 minutes (instead
of 30) til it got black again... Am I still doing something wrong?

thanks,
Cayo


 2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

You have to modify the first line of the script to specify the timeout
(time to purple) eg.


“green status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on the
server “Darth”  have the standard time out


“green+2h status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on
the server “Darth” will timeout in 2 hours.


“green+1d status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on
the server “Darth” will  timeout in 1 day


There is (or was) a bug in BBWin in that you have to have data on the first
line after the status or ZyMon generates an error.


Hope this helps

Regards

Graeme


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Tuesday, 9 June 2009 7:07 PM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable


Hi Greg,

thank you for your support, it gave me the right direction! =D

I found out that this lifetime in the scripts should look like this:

$BB $BBDISP "status+70 $MACHINE.$TEST $COLOR `date` OK"


but the Windows .vbs scripts dont give such parameters back to
hobbit-server... I just dont know how to implement this "status+time" in the
vbs scripts...

another thing is that the column dont get purple but black!


Thanks

 2009/6/8 HUBBARD, GREG ((EDS)) <user-54b18961ee8d@xymon.invalid>

By default, the Hobbit server expects your tests to update at least once
every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME" expires
with no updates the server marks the test "purple" and sends an alert.


The fix is simple -- in your script you need to send a LIFETIME value when
you send your status message.  If you test once every day, you need to
calculate LIFETIME as 24 * 60 + some extra in case your test is delayed from
some reason.


You can read about this in the man pages for the "bb" command (Xymon
communications program).


GLH


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Monday, June 08, 2009 8:17 AM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to set
up the "check time" higher (like one time a day) I noticed that the column
get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the
hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client side?

TIA


*Important - *This email and any attachments may be confidential. If
received in error, please contact us and delete all copies. Before opening
or using attachments check them for viruses and defects. Regardless of any
loss, damage or consequence, whether caused by the negligence of the sender
or not, resulting directly or indirectly from the use of any attached files
our liability is limited to resupplying any affected attachments. Any
representations or opinions expressed are those of the individual sender,
and not necessarily those of the Department of Education and Early Childhood
Development.


*Important - *This email and any attachments may be confidential. If
received in error, please contact us and delete all copies. Before opening
or using attachments check them for viruses and defects. Regardless of any
loss, damage or consequence, whether caused by the negligence of the sender
or not, resulting directly or indirectly from the use of any attached files
our liability is limited to resupplying any affected attachments. Any
representations or opinions expressed are those of the individual sender,
and not necessarily those of the Department of Education and Early Childhood
Development.
list Graeme A Shea · Wed, 10 Jun 2009 22:14:05 +1000 ·
It needs "green+24h" not just "green+24". Everything after the "green"
or "green+24h" will appear on the status page and  something else is
needed on the first line or BBWin (at least in version 0.9) does not
work properly.  An example of one of my files that one of my test
scripts puts in the tmp folder of BBWin is between the dotted lines.

 
......................................................Start next line
........................................................................
...........................

green+27h Defragmentation completed at 9/06/2009 1:16:26 AM

 
&green Beginning defragmentation of C: at 9/06/2009 1:00:00 AM

&green Drive C: Successfully defragmented. at 1:09:40 AM

 
&green Beginning defragmentation of E: at 9/06/2009 1:09:40 AM

&green Drive E: Successfully defragmented. at 1:14:56 AM

 
&green Beginning defragmentation of F: at 9/06/2009 1:14:56 AM

&green Drive F: Successfully defragmented. at 1:16:14 AM

 
&green Beginning defragmentation of G: at 9/06/2009 1:16:14 AM

&green Drive G: Successfully defragmented. at 1:16:26 AM

 
BBDefrag, Shea Technology Pty. Ltd., BBDefrag.vbs Version: 2.0.2

 
................................................End line
above...................................................................
........................................

 
Everything apart from the "green+27h" is displayed on the status page.
The "&green" displays a green dot on the status page.
quoted from Cayo de Moraes

 
Hope this helps

 
Regards

Graeme.

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Wednesday, 10 June 2009 8:47 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

 
still not working... now I get this in the page (column "test") -->
Testserver.test

=D

Hobbit seems not to work this parameters out. It simply ignores my
green+24 (still black after 30 minuter) and prints the "testserver.test"
in the webpage...


2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

I had to put information in the first line after the status message or
it wouldn't work. Something like

 
"green+24h testserver.test " should work, I add the date and time too.
"green+24h" didn't work for me.

 
Regards

 
Graeme

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Wednesday, 10 June 2009 5:08 PM


To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

 
Thx for the help guys, but its not working...

Im using BBWin and here is my configuration:


ext script:
oOutFile.WriteLine "green+1d" & vbCrLf
    Else
        oOutFile.WriteLine "red+1d" & vbCrLf


logfile from ext script, which is send to Xymon:
green+1d

    testserver running test


my BBWin.cfg looks like this:
<externals>
    <setting name="timer" value="3m" />
    <setting name="logstimer" value="60s" />
    <load value="cscript C:\PROGRA~2\BBWin\ext\testscript.vbs"
timer="300m" /> 
</externals> 


With this configuration i could get a green status for 43 minutes
(instead of 30) til it got black again... Am I still doing something
wrong? 

thanks,
Cayo


2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

You have to modify the first line of the script to specify the timeout
(time to purple) eg.

 
"green status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test on
the server "Darth"  have the standard time out

 
"green+2h status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test
on the server "Darth" will timeout in 2 hours.

 
"green+1d status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test
on the server "Darth" will  timeout in 1 day

 
There is (or was) a bug in BBWin in that you have to have data on the
first line after the status or ZyMon generates an error. 

 
Hope this helps

Regards

Graeme

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Tuesday, 9 June 2009 7:07 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

 
Hi Greg,

thank you for your support, it gave me the right direction! =D

I found out that this lifetime in the scripts should look like this:

$BB $BBDISP "status+70 $MACHINE.$TEST $COLOR `date` OK"


but the Windows .vbs scripts dont give such parameters back to
hobbit-server... I just dont know how to implement this "status+time" in
the vbs scripts...

another thing is that the column dont get purple but black! 


Thanks

2009/6/8 HUBBARD, GREG ((EDS)) <user-54b18961ee8d@xymon.invalid>

By default, the Hobbit server expects your tests to update at least once
every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME"
expires with no updates the server marks the test "purple" and sends an
alert.

 
The fix is simple -- in your script you need to send a LIFETIME value
when you send your status message.  If you test once every day, you need
to calculate LIFETIME as 24 * 60 + some extra in case your test is
delayed from some reason.

 
You can read about this in the man pages for the "bb" command (Xymon
communications program).

 
GLH

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Monday, June 08, 2009 8:17 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to
set up the "check time" higher (like one time a day) I noticed that the
column get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the
hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client
side?

TIA

 
Important - This email and any attachments may be confidential. If
received in error, please contact us and delete all copies. Before
opening or using attachments check them for viruses and defects.
Regardless of any loss, damage or consequence, whether caused by the
negligence of the sender or not, resulting directly or indirectly from
the use of any attached files our liability is limited to resupplying
any affected attachments. Any representations or opinions expressed are
those of the individual sender, and not necessarily those of the
Department of Education and Early Childhood Development.

 
Important - This email and any attachments may be confidential. If
received in error, please contact us and delete all copies. Before
opening or using attachments check them for viruses and defects.
Regardless of any loss, damage or consequence, whether caused by the
negligence of the sender or not, resulting directly or indirectly from
the use of any attached files our liability is limited to resupplying
any affected attachments. Any representations or opinions expressed are
those of the individual sender, and not necessarily those of the
Department of Education and Early Childhood Development.

 
Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.
list Cayo de Moraes · Wed, 10 Jun 2009 15:28:54 +0200 ·
Hi Graeme,

sorry for my last post... I wrote only "green+24" but I meant "green+24h".

It doesnt work... I forgot to say that im using BBWin v0.12
quoted from Graeme A Shea

thanks,
Cayo


2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>
 It needs “green+24h” not just “green+24”. Everything after the “green” or
“green+24h” will appear on the status page and  something else is needed on
the first line or BBWin (at least in version 0.9) does not work properly.
 An example of one of my files that one of my test scripts puts in the tmp
folder of BBWin is between the dotted lines.


………………………………………………Start next line ………………………………………………………………………………………

green+27h Defragmentation completed at 9/06/2009 1:16:26 AM


&green Beginning defragmentation of C: at 9/06/2009 1:00:00 AM

&green Drive C: Successfully defragmented. at 1:09:40 AM


&green Beginning defragmentation of E: at 9/06/2009 1:09:40 AM

&green Drive E: Successfully defragmented. at 1:14:56 AM


&green Beginning defragmentation of F: at 9/06/2009 1:14:56 AM

&green Drive F: Successfully defragmented. at 1:16:14 AM


&green Beginning defragmentation of G: at 9/06/2009 1:16:14 AM

&green Drive G: Successfully defragmented. at 1:16:26 AM


BBDefrag, Shea Technology Pty. Ltd., BBDefrag.vbs Version: 2.0.2


…………………………………………End line above……………………………………………………………………………………………..


Everything apart from the “green+27h” is displayed on the status page. The
“&green” displays a green dot on the status page.


Hope this helps


Regards

Graeme.


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Wednesday, 10 June 2009 8:47 PM

*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable


still not working... now I get this in the page (column "test") -->
Testserver.test

=D

Hobbit seems not to work this parameters out. It simply ignores my green+24
(still black after 30 minuter) and prints the "testserver.test" in the
webpage...


 2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

I had to put information in the first line after the status message or it
wouldn’t work. Something like


“green+24h testserver.test “ should work, I add the date and time too.
“green+24h” didn’t work for me.


Regards


Graeme


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Wednesday, 10 June 2009 5:08 PM


*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable


Thx for the help guys, but its not working...

Im using BBWin and here is my configuration:


ext script:
oOutFile.WriteLine "green+1d" & vbCrLf
    Else
        oOutFile.WriteLine "red+1d" & vbCrLf


logfile from ext script, which is send to Xymon:
green+1d

    testserver running test


my BBWin.cfg looks like this:
<externals>
    <setting name="timer" value="3m" />
    <setting name="logstimer" value="60s" />
    <load value="cscript C:\PROGRA~2\BBWin\ext\testscript.vbs" timer="300m"
/>
</externals>


With this configuration i could get a green status for 43 minutes (instead
of 30) til it got black again... Am I still doing something wrong?

thanks,
Cayo


 2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

You have to modify the first line of the script to specify the timeout
(time to purple) eg.


“green status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on the
server “Darth”  have the standard time out


“green+2h status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on
the server “Darth” will timeout in 2 hours.


“green+1d status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on
the server “Darth” will  timeout in 1 day


There is (or was) a bug in BBWin in that you have to have data on the first
line after the status or ZyMon generates an error.


Hope this helps

Regards

Graeme


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Tuesday, 9 June 2009 7:07 PM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable


Hi Greg,

thank you for your support, it gave me the right direction! =D

I found out that this lifetime in the scripts should look like this:

$BB $BBDISP "status+70 $MACHINE.$TEST $COLOR `date` OK"


but the Windows .vbs scripts dont give such parameters back to
hobbit-server... I just dont know how to implement this "status+time" in the
vbs scripts...

another thing is that the column dont get purple but black!


Thanks

2009/6/8 HUBBARD, GREG ((EDS)) <user-54b18961ee8d@xymon.invalid>

By default, the Hobbit server expects your tests to update at least once
every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME" expires
with no updates the server marks the test "purple" and sends an alert.


The fix is simple -- in your script you need to send a LIFETIME value when
you send your status message.  If you test once every day, you need to
calculate LIFETIME as 24 * 60 + some extra in case your test is delayed from
some reason.


You can read about this in the man pages for the "bb" command (Xymon
communications program).


GLH


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Monday, June 08, 2009 8:17 AM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to set
up the "check time" higher (like one time a day) I noticed that the column
get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the
hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client side?

TIA


*Important - *This email and any attachments may be confidential. If
received in error, please contact us and delete all copies. Before opening
or using attachments check them for viruses and defects. Regardless of any
loss, damage or consequence, whether caused by the negligence of the sender
or not, resulting directly or indirectly from the use of any attached files
our liability is limited to resupplying any affected attachments. Any
representations or opinions expressed are those of the individual sender,
and not necessarily those of the Department of Education and Early Childhood
Development.


*Important - *This email and any attachments may be confidential. If
received in error, please contact us and delete all copies. Before opening
or using attachments check them for viruses and defects. Regardless of any
loss, damage or consequence, whether caused by the negligence of the sender
or not, resulting directly or indirectly from the use of any attached files
our liability is limited to resupplying any affected attachments. Any
representations or opinions expressed are those of the individual sender,
and not necessarily those of the Department of Education and Early Childhood
Development.


*Important - *This email and any attachments may be confidential. If
received in error, please contact us and delete all copies. Before opening
or using attachments check them for viruses and defects. Regardless of any
loss, damage or consequence, whether caused by the negligence of the sender
or not, resulting directly or indirectly from the use of any attached files
our liability is limited to resupplying any affected attachments. Any
representations or opinions expressed are those of the individual sender,
and not necessarily those of the Department of Education and Early Childhood
Development.
list Graeme A Shea · Thu, 11 Jun 2009 06:22:29 +1000 ·
I have reread the thread and may have been misleading you. These fixes
will fix a purple error. A "black" error does not exist (AFAIK), does it
go clear (or white),  have you custom icons that would explain why it is
black and not clear? I believe the scripts are working fine the problem
lies elsewhere.

 
I notice with my install that if the whole host stops reporting most
tests go clear (shown as a white dot)  and stay that way until the next
time the test is run. If the host comes back on line they still stay
clear. It sort of makes sense because if the host goes offline then
XyMon no longer remembers the timeout and reports no data (which is
correct).

 
So back to this issue. Are you reporting other tests as well (like disk,
cpu etc.) or only the custom tests.  If the whole host stops reporting
then no data reports would be consistent with my observations.
quoted from Cayo de Moraes

 
Hope this helps

 
Regards

Graeme

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Wednesday, 10 June 2009 11:29 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

 
Hi Graeme,

sorry for my last post... I wrote only "green+24" but I meant
"green+24h".

It doesnt work... I forgot to say that im using BBWin v0.12

thanks,
Cayo


2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

It needs "green+24h" not just "green+24". Everything after the "green"
or "green+24h" will appear on the status page and  something else is
needed on the first line or BBWin (at least in version 0.9) does not
work properly.  An example of one of my files that one of my test
scripts puts in the tmp folder of BBWin is between the dotted lines.

 
......................................................Start next line
........................................................................
...........................

green+27h Defragmentation completed at 9/06/2009 1:16:26 AM

 
&green Beginning defragmentation of C: at 9/06/2009 1:00:00 AM

&green Drive C: Successfully defragmented. at 1:09:40 AM

 
&green Beginning defragmentation of E: at 9/06/2009 1:09:40 AM

&green Drive E: Successfully defragmented. at 1:14:56 AM

 
&green Beginning defragmentation of F: at 9/06/2009 1:14:56 AM

&green Drive F: Successfully defragmented. at 1:16:14 AM

 
&green Beginning defragmentation of G: at 9/06/2009 1:16:14 AM

&green Drive G: Successfully defragmented. at 1:16:26 AM

 
BBDefrag, Shea Technology Pty. Ltd., BBDefrag.vbs Version: 2.0.2

 
................................................End line
above...................................................................
........................................

 
Everything apart from the "green+27h" is displayed on the status page.
The "&green" displays a green dot on the status page.

 
Hope this helps

 
Regards

Graeme.

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Wednesday, 10 June 2009 8:47 PM


To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

 
still not working... now I get this in the page (column "test") -->
Testserver.test

=D

Hobbit seems not to work this parameters out. It simply ignores my
green+24 (still black after 30 minuter) and prints the "testserver.test"
in the webpage...


2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

I had to put information in the first line after the status message or
it wouldn't work. Something like

 
"green+24h testserver.test " should work, I add the date and time too.
"green+24h" didn't work for me.

 
Regards

 
Graeme

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Wednesday, 10 June 2009 5:08 PM


To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

 
Thx for the help guys, but its not working...

Im using BBWin and here is my configuration:


ext script:
oOutFile.WriteLine "green+1d" & vbCrLf
    Else
        oOutFile.WriteLine "red+1d" & vbCrLf


logfile from ext script, which is send to Xymon:
green+1d

    testserver running test


my BBWin.cfg looks like this:
<externals>
    <setting name="timer" value="3m" />
    <setting name="logstimer" value="60s" />
    <load value="cscript C:\PROGRA~2\BBWin\ext\testscript.vbs"
timer="300m" /> 
</externals> 


With this configuration i could get a green status for 43 minutes
(instead of 30) til it got black again... Am I still doing something
wrong? 

thanks,
Cayo


2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

You have to modify the first line of the script to specify the timeout
(time to purple) eg.

 
"green status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test on
the server "Darth"  have the standard time out

 
"green+2h status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test
on the server "Darth" will timeout in 2 hours.

 
"green+1d status Darth.dhcp green 10/06/2009 2:44:50 PM" The dhcp test
on the server "Darth" will  timeout in 1 day

 
There is (or was) a bug in BBWin in that you have to have data on the
first line after the status or ZyMon generates an error. 

 
Hope this helps

Regards

Graeme

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Tuesday, 9 June 2009 7:07 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

 
Hi Greg,

thank you for your support, it gave me the right direction! =D

I found out that this lifetime in the scripts should look like this:

$BB $BBDISP "status+70 $MACHINE.$TEST $COLOR `date` OK"


but the Windows .vbs scripts dont give such parameters back to
hobbit-server... I just dont know how to implement this "status+time" in
the vbs scripts...

another thing is that the column dont get purple but black! 


Thanks

2009/6/8 HUBBARD, GREG ((EDS)) <user-54b18961ee8d@xymon.invalid>

By default, the Hobbit server expects your tests to update at least once
every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME"
expires with no updates the server marks the test "purple" and sends an
alert.

 
The fix is simple -- in your script you need to send a LIFETIME value
when you send your status message.  If you test once every day, you need
to calculate LIFETIME as 24 * 60 + some extra in case your test is
delayed from some reason.

 
You can read about this in the man pages for the "bb" command (Xymon
communications program).

 
GLH

 
From: Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid] 
Sent: Monday, June 08, 2009 8:17 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to
set up the "check time" higher (like one time a day) I noticed that the
column get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the
hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client
side?


Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.
list Cayo de Moraes · Mon, 15 Jun 2009 09:37:58 +0200 ·
well, I have kinda of custom graphs. Im using the BB old icons to replace
the Hobbit-Smilies.

Im also monitoring the standard column like cpu, disk, etc.. these checks
are done every 5 minutes. only the custom checks should be done once a day.

I can follow your idea that xymon does not rebember the status and thats why
it becomes black (should be purple :D ).


Well... maybe should I make these checks every 30 min? it seems to be the
only way to make this work! This little issue is kinda bad, because i dont
see if the status was green or red before it became black.


thanks for the help guys.
quoted from Graeme A Shea


2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>
 I have reread the thread and may have been misleading you. These fixes
will fix a purple error. A “black” error does not exist (AFAIK), does it go
clear (or white),  have you custom icons that would explain why it is black
and not clear? I believe the scripts are working fine the problem lies
elsewhere.


I notice with my install that if the whole host stops reporting most tests
go clear (shown as a white dot)  and stay that way until the next time the
test is run. If the host comes back on line they still stay clear. It sort
of makes sense because if the host goes offline then XyMon no longer
remembers the timeout and reports no data (which is correct).


So back to this issue. Are you reporting other tests as well (like disk,
cpu etc.) or only the custom tests.  If the whole host stops reporting then
no data reports would be consistent with my observations.


Hope this helps


Regards

Graeme


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Wednesday, 10 June 2009 11:29 PM

*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable


Hi Graeme,

sorry for my last post... I wrote only "green+24" but I meant "green+24h".

It doesnt work... I forgot to say that im using BBWin v0.12

thanks,
Cayo

 2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

It needs “green+24h” not just “green+24”. Everything after the “green” or
“green+24h” will appear on the status page and  something else is needed on
the first line or BBWin (at least in version 0.9) does not work properly.
 An example of one of my files that one of my test scripts puts in the tmp
folder of BBWin is between the dotted lines.


………………………………………………Start next line ………………………………………………………………………………………

green+27h Defragmentation completed at 9/06/2009 1:16:26 AM


&green Beginning defragmentation of C: at 9/06/2009 1:00:00 AM

&green Drive C: Successfully defragmented. at 1:09:40 AM


&green Beginning defragmentation of E: at 9/06/2009 1:09:40 AM

&green Drive E: Successfully defragmented. at 1:14:56 AM


&green Beginning defragmentation of F: at 9/06/2009 1:14:56 AM

&green Drive F: Successfully defragmented. at 1:16:14 AM


&green Beginning defragmentation of G: at 9/06/2009 1:16:14 AM

&green Drive G: Successfully defragmented. at 1:16:26 AM


BBDefrag, Shea Technology Pty. Ltd., BBDefrag.vbs Version: 2.0.2


…………………………………………End line above……………………………………………………………………………………………..


Everything apart from the “green+27h” is displayed on the status page. The
“&green” displays a green dot on the status page.


Hope this helps


Regards

Graeme.


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Wednesday, 10 June 2009 8:47 PM


*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable


still not working... now I get this in the page (column "test") -->
Testserver.test

=D

Hobbit seems not to work this parameters out. It simply ignores my green+24
(still black after 30 minuter) and prints the "testserver.test" in the
webpage...


 2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

I had to put information in the first line after the status message or it
wouldn’t work. Something like


“green+24h testserver.test “ should work, I add the date and time too.
“green+24h” didn’t work for me.


Regards


Graeme


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Wednesday, 10 June 2009 5:08 PM


*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable


Thx for the help guys, but its not working...

Im using BBWin and here is my configuration:


ext script:
oOutFile.WriteLine "green+1d" & vbCrLf
    Else
        oOutFile.WriteLine "red+1d" & vbCrLf


logfile from ext script, which is send to Xymon:
green+1d

    testserver running test


my BBWin.cfg looks like this:
<externals>
    <setting name="timer" value="3m" />
    <setting name="logstimer" value="60s" />
    <load value="cscript C:\PROGRA~2\BBWin\ext\testscript.vbs" timer="300m"
/>
</externals>


With this configuration i could get a green status for 43 minutes (instead
of 30) til it got black again... Am I still doing something wrong?

thanks,
Cayo


 2009/6/10 Shea, Graeme A <user-06769a90444e@xymon.invalid>

You have to modify the first line of the script to specify the timeout
(time to purple) eg.


“green status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on the
server “Darth”  have the standard time out


“green+2h status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on
the server “Darth” will timeout in 2 hours.


“green+1d status Darth.dhcp green 10/06/2009 2:44:50 PM” The dhcp test on
the server “Darth” will  timeout in 1 day


There is (or was) a bug in BBWin in that you have to have data on the first
line after the status or ZyMon generates an error.


Hope this helps

Regards

Graeme


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Tuesday, 9 June 2009 7:07 PM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable


Hi Greg,

thank you for your support, it gave me the right direction! =D

I found out that this lifetime in the scripts should look like this:

$BB $BBDISP "status+70 $MACHINE.$TEST $COLOR `date` OK"


but the Windows .vbs scripts dont give such parameters back to
hobbit-server... I just dont know how to implement this "status+time" in the
vbs scripts...

another thing is that the column dont get purple but black!


Thanks

2009/6/8 HUBBARD, GREG ((EDS)) <user-54b18961ee8d@xymon.invalid>

By default, the Hobbit server expects your tests to update at least once
every 30 minutes.  This is the LIFETIME parameter.  After "LIFETIME" expires
with no updates the server marks the test "purple" and sends an alert.


The fix is simple -- in your script you need to send a LIFETIME value when
you send your status message.  If you test once every day, you need to
calculate LIFETIME as 24 * 60 + some extra in case your test is delayed from
some reason.


You can read about this in the man pages for the "bb" command (Xymon
communications program).


GLH


*From:* Cayo de Moraes [mailto:user-92aec3b3c467@xymon.invalid]
*Sent:* Monday, June 08, 2009 8:17 AM
*To:* user-ae9b8668bcde@xymon.invalid
*Subject:* [hobbit] BBWin Ext Scripts after 30min are unavaliable

Hi guys,

im monitoring with some external scripts on my BBWin and when i try to set
up the "check time" higher (like one time a day) I noticed that the column
get unavaliable after 30 minutes for this client.

Is it a know issue?

I also tryed to put this paragraphs (i readed it here somewhere) in the
hobbit-client.cfg:

MAXMSG_DATA="5242880"
MAXMSG_CLIENT="5242880"
MAXMSG_STATUS="5242880"


Nothing works... do i have to setup something else on server/client side?


*Important - *This email and any attachments may be confidential. If
received in error, please contact us and delete all copies. Before opening
or using attachments check them for viruses and defects. Regardless of any
loss, damage or consequence, whether caused by the negligence of the sender
or not, resulting directly or indirectly from the use of any attached files
our liability is limited to resupplying any affected attachments. Any
representations or opinions expressed are those of the individual sender,
and not necessarily those of the Department of Education and Early Childhood
Development.