[hobbit] display howto
Thomas
tlp-hobbit at holme-pedersen.dk
Mon Apr 17 11:23:46 CEST 2006
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
Great Dilla wrote:
> Hi Henrik,
>
> I would like to have the same set-up. And am experiencing some problems.
>
> I will try my best to provide the needed information as much as I can:
> [1] using hobbit version: 4.1.2p1
>
> [2] my bbproxy.log contains the following (repeated lines, truncated):
> -----
> 2006-04-17 02:06:48 Cannot bind to listen socket (Address already in use)
> 2006-04-17 02:06:54 Cannot bind to listen socket (Address already in use)
> 2006-04-17 02:07:00 Cannot bind to listen socket (Address already in use)
> -----
>
> [3] hobbitlaunch.log contains (repeated lines, truncated):
> -----
> 2006-04-17 01:46:00 Task bbproxy terminated, status 1
> 2006-04-17 01:56:00 Task bbproxy terminated, status 1
> 2006-04-17 01:56:06 Task bbproxy terminated, status 1
> 2006-04-17 01:56:12 Task bbproxy terminated, status 1
> 2006-04-17 01:56:18 Task bbproxy terminated, status 1
> 2006-04-17 01:56:24 Task bbproxy terminated, status 1
> 2006-04-17 01:56:30 Task bbproxy terminated, status 1
> -----
>
> [4] hobbitclient.log contains (repeated lines, truncated):
> -----
> 2006-04-17 02:05:48 Could not connect to bbd at 10.116.162.30:1984 -
> Connection refused
> 2006-04-17 02:05:48 Whoops ! bb failed to send message - Connection failed
> -----
>
> [5] I followed the instructions you have outlined to the letter.
>
> [6] There is only one client for now, the "proxy" hobbit server. The
> tests started out green but turned purple after a while. Status
> messages for them are there. rrd graphs are all "nan". hobbitd status
> page displays this:
> -----
> Statistics for Hobbit daemon
> Up since 17-Apr-2006 01:45:31 (0 days, 00:30:02)
>
> Incoming messages : 114
> - status : 30
> - combo : 30
> - page : 0
> - summary : 0
> - data : 0
> - client : 0
> - notes : 0
> - enable : 0
> - disable : 0
> - ack : 0
> - config : 0
> - query : 0
> - hobbitdboard : 31
> - hobbitdlog : 23
> - drop : 0
> - rename : 0
> - dummy : 0
> - notify : 0
> - schedule : 0
> - Bogus/Timeouts : 0
> Incoming messages/sec : 0 (average last 300 seconds)
>
> status channel messages: 41 (1 readers)
> stachg channel messages: 7 (1 readers)
> page channel messages: 8 (1 readers)
> data channel messages: 0 (1 readers)
> notes channel messages: 0 (0 readers)
> enadis channel messages: 0 (0 readers)
> client channel messages: 0 (1 readers)
> -----
>
> [7] I am not able to see status messages on the "master" server. Do I
> need to add the configuration for the client in bb-hosts?
>
> Attached is the CMD shell script I made for bbtest-net. In case the
> problem is there. (the attachment is a zip file. gmail is funky about
> .zip containing execs so i renamed it)
>
> Your inputs on this are very much appreciated.
>
> Best regards,
> Great
>
>
>> -----Original Message-----
>> From: Henrik Stoerner [mailto:henrik at hswn.dk]
>> Sent: 05 April 2006 21:23
>> To: hobbit at hswn.dk
>> Subject: Re: [hobbit] display howto
>>
>> On Wed, Apr 05, 2006 at 04:09:54PM -0400, Lee J. Imber wrote:
>>> I have a rack of servers on the east coast with a hobbit server and a
>>> second rack of servers on the west coast with it's own hobbit server.
>>> Each hobbit server only reports on the servers in its rack. The two
>>> hobbit server do not know the other exists.
>>>
>>> What I would like to do is make the east coast hobbit server be the
>>> "master" server.
>>> Is there a way that I can have the west coast hobbit server send it's
>>> display to the east coast hobbit server.
>> Insert a bbproxy between the clients and the hobbit server on your
>> west coast installation, then configure bbproxy to forward incoming
>> messages to both servers.
>>
>> Right now:
>> * West coast hobbitd listens on 1.2.3.4 port 1984
>> * West coast client sends message to IP 1.2.3.4 port 1984 (hobbitd)
>>
>> With bbproxy:
>> * West coast hobbitd listens on 127.0.0.1 port 1984
>> * West cost bbproxy listend on 1.2.3.4 port 1984
>> * West coast client sends message to IP 1.2.3.4 port 1984 (bbproxy)
>> * bbproxy forwards incoming messages to 127.0.0.1 port 1984, and
>> to east coast hobbitd on 5.6.7.8 port 1984.
>>
>> Note that you do not need any changes to the clients.
>>
>> Changes needed:
>> * Add a --listen=127.0.0.1 to hobbitd in your west coast
>> hobbitlaunch.cfg
>> * Enable bbproxy in your west coast hobbitlaunch.cfg. Use the option
>> "--bbdisplay=127.0.0.1,5.6.7.8" to tell it to forward requests to
>> both servers.
>> * Change the BBSERVERIP setting in your hobbitserver.cfg to point
>> at the 127.0.0.1 address. This setting is used e.g. by the web CGI's
>> that talk to the "real" hobbit server, so it is best to point this
>> at the real server IP, not the proxy.
>> * If you run network tests from the same server, then you probably
>> need to change the CMD setting in hobbitlaunch.cfg also. Instead
>> of calling bbtest-net directly, put it into a shell script wrapper
>> and set BBDISP explicitly to the 5.6.7.8 address before running
>> bbtest-net. Otherwise, it will pick up the BBSERVERIP setting and
>> send the network test results to 127.0.0.1 - so they won't go
>> through the proxy, and hence you won't see them on the east coast
>> server.
>> * Restart Hobbit
>>
>>
>> Henrik
>> To unsubscribe from the hobbit list, send an e-mail to
>> hobbit-unsubscribe at hswn.dk
>>
>> ------------------------------------------------------------------------
>>
>> To unsubscribe from the hobbit list, send an e-mail to
>> hobbit-unsubscribe at hswn.dk
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.0.385 / Virus Database: 268.4.1/313 - Release Date: 15-04-2006
More information about the Xymon
mailing list