<div>The conn and ssh tests are handled by bbnet on the xymon server. The cpu, disks, memory, etc are run on each client system. Personally I wouldn't want to fool around with those. </div><div><br></div><div>The point of the little test script was that, with a much shorter lifetime, those messages will show purple dots a lot quicker when the bbproxy dies. You'll also only get a maximum of three to start with. All the other purple dots will come along 25 minutes later, if nobody fixes the bbproxy.</div>
<div><br></div><div>Ralph Mitchell</div><div><br></div><br><div class="gmail_quote">On Tue, Jul 7, 2009 at 3:31 PM, James <span dir="ltr"><<a href="mailto:j.sansford@ntlworld.com">j.sansford@ntlworld.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff">
<div><font face="Arial" size="2">Hi Ralph,</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">I'm using 4.2.3 - this is for a production area so
I'm weary to try out betas currently, we need stability. I've configured bbproxy
as a service on Solaris so it can bring itself back, but it will just crash
again so I think we might miss quite a few messages..which links into my second
point -> I was trying to find a way of configuring things such as conn, cpu
etc to have a faster purple time and to alert for it. I've found the lifetime
option but this as far as I can see is for custom stuff - not sure how to set it
up for tests such as conn, ssh, cpu etc?</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">I'll try out your script tomorrow and have a play -
as it currently stands if a bbserver dies for whatever reason (and therefore a
bbproxy) it can look for up to half an hour like many things are "green" when
they arn't infact being updated.</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">Cheers</font></div>
<div><font face="Arial" size="2">James</font></div><div><div></div><div class="h5">
<blockquote dir="ltr" style="padding-right:0px;padding-left:5px;margin-left:5px;border-left:#000000 2px solid;margin-right:0px">
<div style="font:10pt arial">----- Original Message ----- </div>
<div style="background:#e4e4e4;font:10pt arial"><b>From:</b>
<a title="ralphmitchell@gmail.com" href="mailto:ralphmitchell@gmail.com" target="_blank">Ralph
Mitchell</a> </div>
<div style="font:10pt arial"><b>To:</b> <a title="hobbit@hswn.dk" href="mailto:hobbit@hswn.dk" target="_blank">hobbit@hswn.dk</a> </div>
<div style="font:10pt arial"><b>Sent:</b> Tuesday, July 07, 2009 6:31
PM</div>
<div style="font:10pt arial"><b>Subject:</b> Re: [hobbit] Multiple hobbit
(bbproxy and bb server) queries</div>
<div><br></div>What version of hobbit/xymon are you running?? I used to
have a problem like that with 4.2. No bbproxy involved there, just
several hobbit servers. If one of them was down, the server/bin/bb
command would hang trying to talk to it. It should have either failed to
make the connect or timed out, but it didn't. Anyway...
<div><br></div>
<div>You could set up a simple heartbeat script, a bit like this:</div>
<div><br></div>
<div> #!/bin/bash</div>
<div><br></div>
<div> $BB $BBDISP "status+2 bbproxyname.panicnow
`date`</div>
<div> If this is purple, a bbproxy
died."</div>
<div><br></div>
<div>Set that up to launch every minute. The message has a lifetime of 2
minutes, so it'll go purple about 3 minutes after the bbproxy hangs up or
dies. You might want to pick a different column name. :)</div>
<div><br></div>
<div>Ralph Mitchell</div>
<div><br>
<div><br>
<div class="gmail_quote">On Tue, Jul 7, 2009 at 8:40 AM, <span dir="ltr"><<a href="mailto:j.sansford@ntlworld.com" target="_blank">j.sansford@ntlworld.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="padding-left:1ex;margin:0px 0px 0px 0.8ex;border-left:#ccc 1px solid">Hi
guys,<br><br>You may remember my questions from last week. Thanks again for
these. I have now implemented it however I have a few questions (and
possibly bugs?). I will first start by describing the setup. To keep things
simple I'll call each hobbit server IP as either "A" "B" or "C" depending on
the data centre.<br><br>Data centre 1:<br>bbproxy and bbserver (running on
same box, A). bbproxy configured to send to B,C,A. bbserver configured to
talk to A,B,C in hobbitserver.cfg.<br><br>Data centre 2:<br>bbproxy and
bbserver (running on same box, B). bbproxy configured to send to C,A,B.
bbserver configured to talk to B,C,A in hobbitserver.cfg.<br><br>Data centre
3:<br>bbproxy and bbserver (running on same box, C). bbproxy configured to
send to A,B,C. bbserver configured to talk to C,A,B in
hobbitserver.cfg.<br><br>---------------------------------------------------<br>Firstly,
everything looks good. However, if I am to stop bbserver at A (but keep
bbproxy running at A) then shortly afterwards bbproxy at A will start
crashing. I've tried changing the order of --bbdisplays and it seems like
the bbproxy will crash if the last bbdisplay IP has been shutdown/not
available. Is this known, or is there a workaround?<br><br>To explain this
better - Lets say bbproxy at site B is configured as --bbdisplays=B,C,A. If
I kill the xymon server at site A then this proxy will crash shortly
afterwards. Note I'm on x86 Solaris.<br><br><br>My other question is this -
currently if a proxy crashes and the other 2 xymon servers do not receive
updates, most tests continue to stay green. I'm sure I've seen a
configuration option but I can't seem to find it - can I configure these
tests to go purple if they don't receive an update within the next 5-10
minutes? They've only just gone purple after 30 minutes, but we really need
to know within 5 minutes if we haven't received a valid update.<br><br>Many
thanks,<br>James.<br><br>To unsubscribe from the hobbit list, send an e-mail
to<br><a href="mailto:hobbit-unsubscribe@hswn.dk" target="_blank">hobbit-unsubscribe@hswn.dk</a><br><br><br></blockquote></div><br></div></div></blockquote></div></div></div>
</blockquote></div><br>