AW: [hobbit] bbproxy timeout
Detlef Stracke
Detlef.Stracke at mobilcom.de
Mon Sep 28 10:09:05 CEST 2009
I have configured an exist radom IP ( I can not shutdown our
monitoring-cluster for tests ) and started in DEBUG. Now everything
works fine. I don`t know what Problem I had.
Whatever, I wait for the next network crash in our datacenter. ;-)
thanks for help
Detlef
________________________________
Von: jef.jagers at thomsonreuters.com
[mailto:jef.jagers at thomsonreuters.com]
Gesendet: Samstag, 26. September 2009 11:57
An: hobbit at hswn.dk
Betreff: RE: [hobbit] bbproxy timeout
Hi Detlef,
have you configured the bbproxy.log to log in debug mode?
This will provide you with more detailed info.
Regards,
Jef Jagers
Systems Engineer
Thomson CompuMark
Thomson Reuters
T +32 3 220 76 02
From: Detlef Stracke [mailto:Detlef.Stracke at mobilcom.de]
Sent: vrijdag, september 25, 2009 09:00
To: hobbit at hswn.dk
Subject: AW: [hobbit] bbproxy timeout
Hi Jef,
no crash and no messages in bbproxy.log. Everything of bbproxy goes
purple on the main-hobbitserver.
________________________________
Von: jef.jagers at thomsonreuters.com
[mailto:jef.jagers at thomsonreuters.com]
Gesendet: Donnerstag, 24. September 2009 14:49
An: hobbit at hswn.dk
Betreff: RE: [hobbit] bbproxy timeout
Hi Detlef,
Does bbproxy crash with error "Fatal Signal caught!" in the situation
you describe?
We experience a same problem, no mather the order we put the two
servers in.
Let me explain:
$BBHOME/bin/bbproxy --hobbitd --listen="ip" --bbdisplay=A:port,B:port
--report=$MACHINE.bbproxy --no-daemon
--pidfile=$BBSERVERLOGS/bbproxy.pid
Is the line found in hobbitlaunch.cfg
If A goes down, bbproxy crashes
if B goes down, same thing
If I switch A,B. Same situation.
Regards,
Jef Jagers
Systems Engineer
Thomson CompuMark
Thomson Reuters
T +32 3 220 76 02
From: Detlef Stracke [mailto:Detlef.Stracke at mobilcom.de]
Sent: woensdag, september 23, 2009 14:43
To: hobbit at hswn.dk
Subject: [hobbit] bbproxy timeout
Hi list,
the command
$BBHOME/bin/bbproxy --hobbitd --bbdisplay=12.13.14.15,20.21.22.23
--report=$MACHINE.bbproxy --no-daemon
--pidfile=$BBSERVERLOGS/bbproxy.pid
works verry well. Unfortunately if the fist ip is unreachable (hardware
is down), the 2nd get no data from the bbproxy. If I change the order of
the ip`s, everythings works fine.
Regards
Detlef
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20090928/640d361f/attachment.html>
More information about the Xymon
mailing list