Xymon Mailing List Archive search

display howto

13 messages in this thread

list Lee J. Imber · Wed, 5 Apr 2006 16:09:54 -0400 · 
Greet,

Looking for some help on how to setup two hobbit servers.

First I will explain what I have and then what I am trying to  accomplish.

Currently.

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.
I would like to see both racks displayed on the east coast hobbit  server display. I do not want the west
coast clients to send data to the east coast hobbit server.

Thanks,

Lee
list Larry Barber · Wed, 5 Apr 2006 15:15:58 -0500 · 
I think the easiest way to do this would be run a bbproxy on the west coast
server. Change hobbitd on the west coast server so it listens on a port
other than 1984, then start a bbproxy that forwards all incoming data to
both the new port on the west coast server and to port 1984 on the east
coast server.  You will also have to update bb-hosts and the like on the
east coast server.

Thanks,
Larry Barber
▸ quoted from Lee J. Imber

On 4/5/06, Lee J. Imber <user-263d836b52f6@xymon.invalid> wrote:
Greet,

Looking for some help on how to setup two hobbit servers.

First I will explain what I have and then what I am trying to
accomplish.

Currently.

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.
I would like to see both racks displayed on the east coast hobbit
server display. I do not want the west
coast clients to send data to the east coast hobbit server.

Thanks,

Lee
list Henrik Størner · Wed, 5 Apr 2006 22:23:13 +0200 ·
▸ quoted from Lee J. Imber
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
list Lee J. Imber · Wed, 5 Apr 2006 16:53:25 -0400 · 
Thanks Henrik and Larry for the replies.

I will definitely give that a try.

Thanks!

Lee
▸ quoted from Henrik Størner

On Apr 5, 2006, at 4:23 PM, Henrik Stoerner wrote:

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
list Craig Whilding · Thu, 6 Apr 2006 10:53:16 +0100 · 
Thanks for the info Henrik, I'd already set this up but the network test
bit was causing me problems (think id had BBDISPLAYS set for int and ext
ip's), putting it in the script sorted that finally! I added the BBDISP
value into the bbretest-net.sh script also. I use the NET: tag in
bbhosts to locally test servers on the machine that's receiving info
from other hobbit servers also.

Thanks,
Craig Whilding
▸ quoted from Lee J. Imber

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: 05 April 2006 21:23
To: user-ae9b8668bcde@xymon.invalid
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
list Craig Whilding · Thu, 6 Apr 2006 11:08:46 +0100 · 
Oops, spoke too soon!

Every 5 minutes im getting 6 lines of "Cannot bind to listen socket
(Address already in use)". Network tests are now fine and are showing up
on both servers displays fine. Is this something to do with the local
bbgen? It only gives its report to the local server so is it
interfering?

Thanks
▸ quoted from Craig Whilding

-----Original Message-----
From: Whilding, Craig 
Sent: 06 April 2006 10:53
To: user-ae9b8668bcde@xymon.invalid
Subject: RE: [hobbit] display howto

Thanks for the info Henrik, I'd already set this up but the network test
bit was causing me problems (think id had BBDISPLAYS set for int and ext
ip's), putting it in the script sorted that finally! I added the BBDISP
value into the bbretest-net.sh script also. I use the NET: tag in
bbhosts to locally test servers on the machine that's receiving info
from other hobbit servers also.

Thanks,
Craig Whilding

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: 05 April 2006 21:23
To: user-ae9b8668bcde@xymon.invalid
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
list Great Dilla · Mon, 17 Apr 2006 02:24:20 +0800 · 
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
▸ quoted from Craig Whilding


-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: 05 April 2006 21:23
To: user-ae9b8668bcde@xymon.invalid
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
Attachments (1)
list Thomas Pedersen · Mon, 17 Apr 2006 11:23:46 +0200 · 
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
▸ quoted from Great Dilla

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:user-ce4a2c883f75@xymon.invalid]
Sent: 05 April 2006 21:23
To: user-ae9b8668bcde@xymon.invalid
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


--
list Larry Barber · Mon, 17 Apr 2006 08:59:34 -0500 · 
Sounds like you're using the same port for both hobbitd and bbproxy. That
won't work. If you don't want to change all your clients you need to change
the port that hobbitd listens to, then setup bbproxy to forward the incoming
messages to both the new hobbitd port on the localhost and to whatever other
machine(s) you want to send them to.

Thanks,
Larry Barber
▸ quoted from Thomas Pedersen

On 4/17/06, Thomas <user-97316fb2dd2a@xymon.invalid> 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

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:user-ce4a2c883f75@xymon.invalid]
Sent: 05 April 2006 21:23
To: user-ae9b8668bcde@xymon.invalid
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


--
list Thomas Pedersen · Mon, 17 Apr 2006 16:24:06 +0200 · 
Yes, this is the setup I am running. Works just fine. I thought that was 
the setup what Dilla wanted to run too.
▸ quoted from Larry Barber

Larry Barber wrote:
Sounds like you're using the same port for both hobbitd and bbproxy. 
That won't work. If you don't want to change all your clients you need 
to change the port that hobbitd listens to, then setup bbproxy to 
forward the incoming messages to both the new hobbitd port on the 
localhost and to whatever other machine(s) you want to send them to.

Thanks,
Larry Barber

On 4/17/06, *Thomas* <user-97316fb2dd2a@xymon.invalid 
<mailto:user-97316fb2dd2a@xymon.invalid>> 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

    <http://127.0.0.1>;
    option and the bbproxy have --listen= 1.2.3.4 <http://1.2.3.4>;
    --bbdisplay=127.0.0.1 <http://127.0.0.1>;
    --bbdisplay=2.3.4.5 <http://2.3.4.5>;

    The BBDISP in hobbitserver.cfg should still be your 1.2.3.4
    <http://1.2.3.4>; address
▸ quoted from Great Dilla

    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: user-ce4a2c883f75@xymon.invalid
    <mailto:user-ce4a2c883f75@xymon.invalid>]
Sent: 05 April 2006 21:23
To: user-ae9b8668bcde@xymon.invalid <mailto:user-ae9b8668bcde@xymon.invalid>
▸ quoted from Larry Barber
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 <http://1.2.3.4>; port 1984
* West coast client sends message to IP 1.2.3.4 <http://1.2.3.4>;
    port 1984 (hobbitd)

With bbproxy:
* West coast hobbitd listens on 127.0.0.1 <http://127.0.0.1>;
    port 1984
* West cost bbproxy listend on 1.2.3.4 <http://1.2.3.4>; port 1984
* West coast client sends message to IP 1.2.3.4 <http://1.2.3.4>;
    port 1984 (bbproxy)
* bbproxy forwards incoming messages to 127.0.0.1
    <http://127.0.0.1>; port 1984, and
  to east coast hobbitd on 5.6.7.8 <http://5.6.7.8>; port 1984.
▸ quoted from Larry Barber

Note that you do not need any changes to the clients.

Changes needed:

* Add a --listen= 127.0.0.1 <http://127.0.0.1>; to hobbitd in
▸ quoted from Larry Barber
    your west coast
  hobbitlaunch.cfg
* Enable bbproxy in your west coast hobbitlaunch.cfg. Use the option

  "--bbdisplay= 127.0.0.1 <http://127.0.0.1>,5.6.7.8
    <http://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 <http://127.0.0.1>; address. This setting is
▸ quoted from Larry Barber
    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 <http://5.6.7.8>;
▸ quoted from Larry Barber
    address before running
  bbtest-net. Otherwise, it will pick up the BBSERVERIP setting and

  send the network test results to 127.0.0.1 <http://127.0.0.1>;
▸ quoted from Larry Barber
    - so they won't go
  through the proxy, and hence you won't see them on the east coast
  server.
* Restart Hobbit


Henrik


    --

    15-04-2006


--
list Great Dilla · Tue, 18 Apr 2006 00:50:41 +0800 · 
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.
▸ quoted from Thomas Pedersen

On 4/17/06, Thomas <user-97316fb2dd2a@xymon.invalid> 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
list Larry Barber · Mon, 17 Apr 2006 12:34:38 -0500 · 
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
▸ quoted from Great Dilla


On 4/17/06, Great Dilla <user-3e85c7b9d5a4@xymon.invalid> 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 <user-97316fb2dd2a@xymon.invalid> 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
list Great Dilla · Tue, 18 Apr 2006 05:34:41 +0800 · 
Thanks for the inputs Larry. Will be trying this out.
▸ quoted from Larry Barber

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
▸ quoted from Larry Barber
--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
▸ quoted from Larry Barber
--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