[hobbit] display howto

[Larry Barber]

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


Thanks,
Larry Barber


On 4/17/06, Great Dilla <great.dilla at gmail.com> wrote:
>
> hobbitd part of hobbitlaunch.cfg
> -----
> # This is the main Hobbit daemon. You cannot live without this one.
> [hobbitd]
>         HEARTBEAT
>         ENVFILE /export/hobbit/server/etc/hobbitserver.cfg
>         CMD hobbitd --pidfile=$BBSERVERLOGS/hobbitd.pid
> --restart=$BBTMP/hobbitd.chk --che
> ckpoint-file=$BBTMP/hobbitd.chk --checkpoint-interval=600
> --log=$BBSERVERLOGS/hobbitd.log
> --admin-senders=127.0.0.1,$BBSERVERIP --ghosts=log --listen=127.0.0.1
> -----
>
> bbproxy part of hobbitlaunch.cfg
> -----
> [bbproxy]
>         ENVFILE /export/hobbit/server/etc/hobbitserver.cfg
>         CMD $BBHOME/bin/bbproxy --hobbitd --report=$MACHINE.bbproxy
> --no-daemon --pidfile=$BBSERVERLOGS/bbproxy.pid
> --bbdisplay=127.0.0.1,10.116.162.29 --listen=10.116.162.30
>         LOGFILE $BBSERVERLOGS/bbproxy.log
> -----
>
> I am doing this as a guinea pig server on the lab before I deploy it
> on our Singapore office. It is a remote site that I will be monitoring
> from the Philippines.
>
> Thanks for your inputs.
>
> On 4/17/06, Thomas <tlp-hobbit at holme-pedersen.dk> wrote:
> > It would help greatly if you would include your hobbitd and bbproxy
> > sections of hobbitlaunch.cfg
> >
> > The setup you want is to have hobbitd only have a --listen=127.0.0.1
> > option and the bbproxy have --listen=1.2.3.4 --bbdisplay=127.0.0.1
> > --bbdisplay=2.3.4.5
> >
> > The BBDISP in hobbitserver.cfg should still be your 1.2.3.4 address
> >
>
> To unsubscribe from the hobbit list, send an e-mail to
> hobbit-unsubscribe at hswn.dk
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20060417/610dc82f/attachment.html>