Xymon Mailing List Archive search

Using bbproxy to replicate the display

9 messages in this thread

list Craig Whilding · Tue, 1 Nov 2005 13:15:48 -0000 · 
My company has a few sites that are currently using hobbit or big
brother for monitoring. What we wish to do is forward all of this
information to a central hobbit server so collate it for reports etc.
This server would also be testing the networks site gateways etc. After
reading the "delay creation of web pages" posts I realise bbproxy is the
replacement to bbrelay I require but I was wondering how I should set it
up. Looking at the manual and hobbitlaunch.cfg it says I should disable
hobbitd. Will each sites monitoring work as normal if I set --bbdisplay=
localhost and also the other, central machine?

 
Thanks

 
Craig Whilding
list Henrik Størner · Tue, 1 Nov 2005 16:40:17 +0100 ·
▸ quoted from Craig Whilding
On Tue, Nov 01, 2005 at 01:15:48PM -0000, Whilding, Craig wrote:
My company has a few sites that are currently using hobbit or big
brother for monitoring. What we wish to do is forward all of this
information to a central hobbit server so collate it for reports etc.
This server would also be testing the networks site gateways etc. After
reading the "delay creation of web pages" posts I realise bbproxy is the
replacement to bbrelay I require but I was wondering how I should set it
up. Looking at the manual and hobbitlaunch.cfg it says I should disable
hobbitd. Will each sites monitoring work as normal if I set --bbdisplay=
localhost and also the other, central machine?
By default, hobbitd and bbproxy will conflict because they will both
attempt to listen to port 1984 to handle incoming messages.

But if you configure them properly, they can coexist. The setup you're
after sounds like you want bbproxy to receive all of the incoming
status messages and then forward them to a) a local hobbitd running
on the same host, and b) the central hobbitd server.

The easiest way to do that is to setup the local hobbitd's to listen on
only the loopback interface (127.0.0.1), and bbproxy to listen on the 
public IP-address. Say your local server has IP 172.16.10.1 and the 
central Hobbit server is 10.0.100.200, then you should use the options 

  --listen=127.0.0.1 

for hobbitd, and 

  --listen=172.16.10.1 --bbdisplay=127.0.0.1,10.0.100.200
  
for bbproxy.


Regards,
Henrik
list Craig Whilding · Tue, 1 Nov 2005 15:43:28 -0000 · 
Thanks Henrik, ill give it a try.

Craig Whilding
▸ quoted from Henrik Størner

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: 01 November 2005 15:40
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

On Tue, Nov 01, 2005 at 01:15:48PM -0000, Whilding, Craig wrote:
My company has a few sites that are currently using hobbit or big
brother for monitoring. What we wish to do is forward all of this
information to a central hobbit server so collate it for reports etc.
This server would also be testing the networks site gateways etc.
After
reading the "delay creation of web pages" posts I realise bbproxy is
the
replacement to bbrelay I require but I was wondering how I should set
it
up. Looking at the manual and hobbitlaunch.cfg it says I should
disable
hobbitd. Will each sites monitoring work as normal if I set
--bbdisplay=
localhost and also the other, central machine?
By default, hobbitd and bbproxy will conflict because they will both
attempt to listen to port 1984 to handle incoming messages.

But if you configure them properly, they can coexist. The setup you're
after sounds like you want bbproxy to receive all of the incoming
status messages and then forward them to a) a local hobbitd running
on the same host, and b) the central hobbitd server.

The easiest way to do that is to setup the local hobbitd's to listen on
only the loopback interface (127.0.0.1), and bbproxy to listen on the 
public IP-address. Say your local server has IP 172.16.10.1 and the 
central Hobbit server is 10.0.100.200, then you should use the options 

  --listen=127.0.0.1 

for hobbitd, and 

  --listen=172.16.10.1 --bbdisplay=127.0.0.1,10.0.100.200
  
for bbproxy.


Regards,
Henrik
list Craig Whilding · Wed, 2 Nov 2005 13:45:19 -0000 · 
Should I be setting the loopback to listen on a specific port as
currently its still giving errors that they are conflicting and so the
status board does not show up.

Thanks

Craig
▸ quoted from Craig Whilding

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: 01 November 2005 15:40
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

On Tue, Nov 01, 2005 at 01:15:48PM -0000, Whilding, Craig wrote:
My company has a few sites that are currently using hobbit or big
brother for monitoring. What we wish to do is forward all of this
information to a central hobbit server so collate it for reports etc.
This server would also be testing the networks site gateways etc.
After
reading the "delay creation of web pages" posts I realise bbproxy is
the
replacement to bbrelay I require but I was wondering how I should set
it
up. Looking at the manual and hobbitlaunch.cfg it says I should
disable
hobbitd. Will each sites monitoring work as normal if I set
--bbdisplay=
localhost and also the other, central machine?
By default, hobbitd and bbproxy will conflict because they will both
attempt to listen to port 1984 to handle incoming messages.

But if you configure them properly, they can coexist. The setup you're
after sounds like you want bbproxy to receive all of the incoming
status messages and then forward them to a) a local hobbitd running
on the same host, and b) the central hobbitd server.

The easiest way to do that is to setup the local hobbitd's to listen on
only the loopback interface (127.0.0.1), and bbproxy to listen on the 
public IP-address. Say your local server has IP 172.16.10.1 and the 
central Hobbit server is 10.0.100.200, then you should use the options 

  --listen=127.0.0.1 

for hobbitd, and 

  --listen=172.16.10.1 --bbdisplay=127.0.0.1,10.0.100.200
  
for bbproxy.


Regards,
Henrik
list Craig Whilding · Wed, 2 Nov 2005 13:48:50 -0000 · 
Just looking through again, should BBSERVERID in hobbitserver.cfg still
be set as the real ip of the machine?
▸ quoted from Craig Whilding

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: 01 November 2005 15:40
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

On Tue, Nov 01, 2005 at 01:15:48PM -0000, Whilding, Craig wrote:
My company has a few sites that are currently using hobbit or big
brother for monitoring. What we wish to do is forward all of this
information to a central hobbit server so collate it for reports etc.
This server would also be testing the networks site gateways etc.
After
reading the "delay creation of web pages" posts I realise bbproxy is
the
replacement to bbrelay I require but I was wondering how I should set
it
up. Looking at the manual and hobbitlaunch.cfg it says I should
disable
hobbitd. Will each sites monitoring work as normal if I set
--bbdisplay=
localhost and also the other, central machine?
By default, hobbitd and bbproxy will conflict because they will both
attempt to listen to port 1984 to handle incoming messages.

But if you configure them properly, they can coexist. The setup you're
after sounds like you want bbproxy to receive all of the incoming
status messages and then forward them to a) a local hobbitd running
on the same host, and b) the central hobbitd server.

The easiest way to do that is to setup the local hobbitd's to listen on
only the loopback interface (127.0.0.1), and bbproxy to listen on the 
public IP-address. Say your local server has IP 172.16.10.1 and the 
central Hobbit server is 10.0.100.200, then you should use the options 

  --listen=127.0.0.1 

for hobbitd, and 

  --listen=172.16.10.1 --bbdisplay=127.0.0.1,10.0.100.200
  
for bbproxy.


Regards,
Henrik
list Thomas Pedersen · Wed, 02 Nov 2005 14:55:29 +0100 · 
No but you should remove the $BBSERVERID from the --listen option on 
hobbitd.
▸ quoted from Craig Whilding

Whilding, Craig wrote:

Just looking through again, should BBSERVERID in hobbitserver.cfg still
be set as the real ip of the machine? 

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: 01 November 2005 15:40
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

On Tue, Nov 01, 2005 at 01:15:48PM -0000, Whilding, Craig wrote:
 

My company has a few sites that are currently using hobbit or big
brother for monitoring. What we wish to do is forward all of this
information to a central hobbit server so collate it for reports etc.
This server would also be testing the networks site gateways etc.
   

After
 

reading the "delay creation of web pages" posts I realise bbproxy is
   

the
 

replacement to bbrelay I require but I was wondering how I should set
   

it
 

up. Looking at the manual and hobbitlaunch.cfg it says I should
   

disable
 

hobbitd. Will each sites monitoring work as normal if I set
   

--bbdisplay=
 

localhost and also the other, central machine?
   

By default, hobbitd and bbproxy will conflict because they will both
attempt to listen to port 1984 to handle incoming messages.

But if you configure them properly, they can coexist. The setup you're
after sounds like you want bbproxy to receive all of the incoming
status messages and then forward them to a) a local hobbitd running
on the same host, and b) the central hobbitd server.

The easiest way to do that is to setup the local hobbitd's to listen on
only the loopback interface (127.0.0.1), and bbproxy to listen on the 
public IP-address. Say your local server has IP 172.16.10.1 and the 
central Hobbit server is 10.0.100.200, then you should use the options 

 --listen=127.0.0.1 

for hobbitd, and 

 --listen=172.16.10.1 --bbdisplay=127.0.0.1,10.0.100.200
 
for bbproxy.


Regards,
Henrik
list Craig Whilding · Wed, 2 Nov 2005 14:14:38 -0000 · 
The --listen option is set to 127.0.0.1 only for hobbitd in the
hobbitlaunch.cfg file. 

Even when hobbitd is DISABLED I still get the socket is in use.
▸ quoted from Thomas Pedersen

-----Original Message-----
From: Thomas [mailto:user-97316fb2dd2a@xymon.invalid] 
Sent: 02 November 2005 13:55
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

No but you should remove the $BBSERVERID from the --listen option on 
hobbitd.

Whilding, Craig wrote:

Just looking through again, should BBSERVERID in hobbitserver.cfg still
be set as the real ip of the machine? 

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: 01 November 2005 15:40
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

On Tue, Nov 01, 2005 at 01:15:48PM -0000, Whilding, Craig wrote:
 

My company has a few sites that are currently using hobbit or big
brother for monitoring. What we wish to do is forward all of this
information to a central hobbit server so collate it for reports etc.
This server would also be testing the networks site gateways etc.
   

After
 

reading the "delay creation of web pages" posts I realise bbproxy is
   

the
 

replacement to bbrelay I require but I was wondering how I should set
   

it
 

up. Looking at the manual and hobbitlaunch.cfg it says I should
   

disable
 

hobbitd. Will each sites monitoring work as normal if I set
   

--bbdisplay=
 

localhost and also the other, central machine?
   

By default, hobbitd and bbproxy will conflict because they will both
attempt to listen to port 1984 to handle incoming messages.

But if you configure them properly, they can coexist. The setup you're
after sounds like you want bbproxy to receive all of the incoming
status messages and then forward them to a) a local hobbitd running
on the same host, and b) the central hobbitd server.

The easiest way to do that is to setup the local hobbitd's to listen on
only the loopback interface (127.0.0.1), and bbproxy to listen on the 
public IP-address. Say your local server has IP 172.16.10.1 and the 
central Hobbit server is 10.0.100.200, then you should use the options 

 --listen=127.0.0.1 

for hobbitd, and 

 --listen=172.16.10.1 --bbdisplay=127.0.0.1,10.0.100.200
 
for bbproxy.


Regards,
Henrik
list Thomas Pedersen · Wed, 02 Nov 2005 15:21:54 +0100 · 
In my setup I have --listen=127.0.0.1 on the hobbitd section and 
--listen=172.17.100.10 --bbdisplay=127.0.0.1,172.17.100.20 on the 
bbproxy section.

My central server is on 172.17.100.20

Try to look at netstat -ln and see where you have the port 1984 listening.
▸ quoted from Craig Whilding

Whilding, Craig wrote:

The --listen option is set to 127.0.0.1 only for hobbitd in the
hobbitlaunch.cfg file. 

Even when hobbitd is DISABLED I still get the socket is in use. 

-----Original Message-----
From: Thomas [mailto:user-97316fb2dd2a@xymon.invalid] 
Sent: 02 November 2005 13:55
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

No but you should remove the $BBSERVERID from the --listen option on 
hobbitd.

Whilding, Craig wrote:

 
Just looking through again, should BBSERVERID in hobbitserver.cfg still
be set as the real ip of the machine? 

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: 01 November 2005 15:40
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

On Tue, Nov 01, 2005 at 01:15:48PM -0000, Whilding, Craig wrote:


My company has a few sites that are currently using hobbit or big
brother for monitoring. What we wish to do is forward all of this
information to a central hobbit server so collate it for reports etc.
This server would also be testing the networks site gateways etc.
  

After


reading the "delay creation of web pages" posts I realise bbproxy is
  

the


replacement to bbrelay I require but I was wondering how I should set
  

it


up. Looking at the manual and hobbitlaunch.cfg it says I should
  

disable


hobbitd. Will each sites monitoring work as normal if I set
  

--bbdisplay=


localhost and also the other, central machine?
  

By default, hobbitd and bbproxy will conflict because they will both
attempt to listen to port 1984 to handle incoming messages.

But if you configure them properly, they can coexist. The setup you're
after sounds like you want bbproxy to receive all of the incoming
status messages and then forward them to a) a local hobbitd running
on the same host, and b) the central hobbitd server.

The easiest way to do that is to setup the local hobbitd's to listen on
only the loopback interface (127.0.0.1), and bbproxy to listen on the 
public IP-address. Say your local server has IP 172.16.10.1 and the 
central Hobbit server is 10.0.100.200, then you should use the options 

--listen=127.0.0.1 

for hobbitd, and 

--listen=172.16.10.1 --bbdisplay=127.0.0.1,10.0.100.200

for bbproxy.


Regards,
Henrik
list Craig Whilding · Thu, 3 Nov 2005 15:08:52 -0000 · 
Finally solved it - BBSERVERID was being used by another variable that
was performing network tests and listening on the external port.
Changing it to 127.0.01 lets me see the status board locally and have
the bbproxy working properly.

Thanks for the help.

Craig
▸ quoted from Thomas Pedersen

-----Original Message-----
From: Thomas [mailto:user-97316fb2dd2a@xymon.invalid] 
Sent: 02 November 2005 14:22
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

In my setup I have --listen=127.0.0.1 on the hobbitd section and 
--listen=172.17.100.10 --bbdisplay=127.0.0.1,172.17.100.20 on the 
bbproxy section.

My central server is on 172.17.100.20

Try to look at netstat -ln and see where you have the port 1984
listening.

Whilding, Craig wrote:

The --listen option is set to 127.0.0.1 only for hobbitd in the
hobbitlaunch.cfg file. 

Even when hobbitd is DISABLED I still get the socket is in use. 

-----Original Message-----
From: Thomas [mailto:user-97316fb2dd2a@xymon.invalid] 
Sent: 02 November 2005 13:55
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

No but you should remove the $BBSERVERID from the --listen option on 
hobbitd.

Whilding, Craig wrote:

 
Just looking through again, should BBSERVERID in hobbitserver.cfg
still
be set as the real ip of the machine? 

-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid] 
Sent: 01 November 2005 15:40
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] Using bbproxy to replicate the display

On Tue, Nov 01, 2005 at 01:15:48PM -0000, Whilding, Craig wrote:


My company has a few sites that are currently using hobbit or big
brother for monitoring. What we wish to do is forward all of this
information to a central hobbit server so collate it for reports etc.
This server would also be testing the networks site gateways etc.
  

After


reading the "delay creation of web pages" posts I realise bbproxy is
  

the


replacement to bbrelay I require but I was wondering how I should set
  

it


up. Looking at the manual and hobbitlaunch.cfg it says I should
  

disable


hobbitd. Will each sites monitoring work as normal if I set
  

--bbdisplay=


localhost and also the other, central machine?
  

By default, hobbitd and bbproxy will conflict because they will both
attempt to listen to port 1984 to handle incoming messages.

But if you configure them properly, they can coexist. The setup you're
after sounds like you want bbproxy to receive all of the incoming
status messages and then forward them to a) a local hobbitd running
on the same host, and b) the central hobbitd server.

The easiest way to do that is to setup the local hobbitd's to listen
on
only the loopback interface (127.0.0.1), and bbproxy to listen on the 
public IP-address. Say your local server has IP 172.16.10.1 and the 
central Hobbit server is 10.0.100.200, then you should use the options
--listen=127.0.0.1 

for hobbitd, and 

--listen=172.16.10.1 --bbdisplay=127.0.0.1,10.0.100.200

for bbproxy.


Regards,
Henrik