Re: [hobbit] BBWin Ext Scripts after 30min are unavaliable

[Cayo de Moraes <camorae (at) googlemail.com>]

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 <Shea.Graeme.A (at) edumail.vic.gov.au>

>  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:camorae (at) googlemail.com]
> *Sent:* Tuesday, 9 June 2009 7:07 PM
> *To:* hobbit (at) hswn.dk
> *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)) <ghubbard (at) hp.com>
>
> 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:camorae (at) googlemail.com]
> *Sent:* Monday, June 08, 2009 8:17 AM
> *To:* hobbit (at) hswn.dk
> *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.
>