Thanks for the inputs Larry. Will be trying this out.
On 4/18/06, Larry Barber <user-6ef9c2864140@xymon.invalid> wrote:
I am running a setup similar to what you are aiming for, here is my hobbitd
portion of hobbitlaunch:
[hobbitd]
HEARTBEAT
ENVFILE /usr/local/hobbit/server/etc/hobbitserver.cfg
CMD hobbitd --pidfile=$BBSERVERLOGS/hobbitd.pid
--restart=$BBTMP/hobbitd.chk
--checkpoint-file=$BBTMP/hobbitd.chk
--checkpoint-interval=600 --log=$BBSERVERLOGS/hobbitd.log
--admin-senders=127.0.0.1,$BBSERVERIP --listen=x.x.x.x:1985 --ghosts=allow
--status-senders=127.0.0.1,$BBSERVERIP --dbghost=trackerdb
Notice the hobbit daemon is listening on port 1985 (you will also need to
make a change in hobbitserver.cfg).
Here is the bbproxy:
[bbproxy]
ENVFILE /usr/local/hobbit/server/etc/hobbitserver.cfg
CMD $BBHOME/bin/bbproxy --hobbitd --bbdisplay=x.x.x.x:1985
--bbdisplay=y.y.y.y:1984 --bbdisplay=z.z.z.z:1984 --report=bb.bbproxy
--no-daemon --pidfile=$BBSERVERLOGS/bbproxy.pid
LOGFILE $BBSERVERLOGS/bbproxy.log
Here notice the first bbdisplay option is what sends the messages to the new
hobbitd port on the host machine, the next two send the messages to two
other machines.
In order to get the network tests to be forwarded to the two other machines
above I had to modify the network test portion of hobbitlaunch thusly:
[bbnet]
ENVFILE /usr/local/hobbit/server/etc/hobbitserver.cfg
NEEDS hobbitd
CMD BBPORT=1984 bbtest-net --report --ping --timeout=15
LOGFILE $BBSERVERLOGS/bb-network.log
INTERVAL 2m
Before I added the BBPORT=1984 the program was sending the network reports
direct to hobbitd on port 1985, the reports weren't being forwarded to the
other machines.
Thanks,
Larry Barber