Hi.
Thanks for the reply.
This however seems not to be the solution to my problem.
I configured the isolated hobbit servers to act as proxies and tested
this solution of yours both with and without being a proxy and it did
not work in either way.
Does anyone have a clue as to what is going on and/or know how to fix
this?
With regards,
Sigurður Guðbrandsson
On Fri, 2007-06-15 at 11:42 +0100, Jones, Jason (Altrincham) wrote:
You need to alter the bbnet section to:
[bbnet]
ENVFILE /usr/local/hobbit/server/etc/hobbitserver.cfg
CMD $BBHOME/bin/net-test.sh
LOGFILE $BBSERVERLOGS/bb-network.log
INTERVAL 5m
Make net-test.sh under $BBHOME/bin/ code follows:
#!/bin/sh
export BBDISP=<EXTERNAL IP>
$bbhome/bin/bbtest-net --report --ping --checkresponse --dns=ip
Hope this helps,
Jason.
-----Original Message-----
From: Sigurður Guðbrandsson [mailto:user-f6f2e0690a1f@xymon.invalid]
Sent: 15 June 2007 11:39
To: user-ae9b8668bcde@xymon.invalid
Subject: [hobbit] Problem with multiple display servers and hobbit.
Hiya.
I am having a bit of a problem with multiple display servers and hobbit.
I have a central server that is accessable from the internet and I have
a couple of servers here and there to monitor devices for me.
The devices can't send information to the central server, only the local
server at each location.
I configured each local server to have two bb displays in
hobbitserver.cfg. (See below)
# General settings
BBPORT="1984" # Portnumber where hobbitd/bbd listens
BBDISP="0.0.0.0" # IP of a single hobbit/bbd server
BBDISPLAYS="$BBSERVERIP 11.11.11.11" # IP of multiple
hobbit/bbd servers. If used, BBDISP must be 0.0.0.0
The second IP address is a fake one on purpose, however in my config it
is real.
And in the hobbitlaunch.cfg file the line that runs the daemon is the
following.
[hobbitd]
ENVFILE /usr/lib/hobbit/server/etc/hobbitserver.cfg
CMD hobbitd --pidfile=$BBSERVERLOGS/hobbitd.pid --restart=
$BBTMP/hobbitd.chk --checkpoint-file=$BBTMP/hobbitd.chk
--checkpoint-interval=50 --log=$BBSERVERLOGS/hobbitd.log
--admin-senders=127.0.0.1 --store-clientlogs=!msgs
This also is all good afaik.
When I look at the local server, the conn status and everything is good
all the time.
However when I look at the central server the conn tab is good for 4
minutes or so and then every server that has a local server is down for
1.
Has anyone experienced this problem and/or knows a solution to this?
With regards,
Sigurður Guðbrandsson.