20 Jan
2009
20 Jan
'09
2:32 p.m.
OK, it may be a documentation issue, I tried it with the --servers (like I said you should try!) and it failed. I tried it with the --bbdisplay= and it worked, so going back on what I said earlier, try this:
./bbcmd ./bbproxy --hobbitd --no-daemon --bbdisplay=192.168.252.80,$BBSERVERIP -report=192.168.252.78
Sorry,
|\/|
-----Original Message-----
From: Evelyne Simon [mailto:ESimon at aquitaine-valley.fr]
Sent: 20 January 2009 13:50
To: hobbit at hswn.dk
Subject: RE: [hobbit] hoobit relay
/bbcmd bbproxy --hobbitd --no-daemon --servers=192.168.252.80,$BBSERVERIP -report=192.168.252.78
2009-01-20 07:50:04 Using default environment file /usr/local/hobbit//server/etc/hobbitserver.cfg
2009-01-20 07:50:04 No BBDISPLAY address given - aborting
De : Ward, Martin [mailto:Martin.Ward at colt.net]
Envoyé : mardi 20 janvier 2009 13:56
À : hobbit at hswn.dk
Objet : RE: [hobbit] hoobit relay
Sorry, that was a case of my fingers working faster than my brain. You need to set up the environment which can be easy done like this, assuming you are logged in as the hobbit user and in the server/bin directory :
./bbcmd ./bbproxy --hobbitd --no-daemon --servers=192.168.252.80,$BBSERVERIP -report=192.168.252.78
-----Original Message-----
From: Evelyne Simon [mailto:ESimon at aquitaine-valley.fr]
Sent: 20 January 2009 12:32
To: hobbit at hswn.dk
Subject: RE: [hobbit] hoobit relay
./bbproxy --hobbitd --no-daemon --servers=192.168.252.80,$BBSERVERIP -report=192.168.252.78
log
2009-01-20 06:31:34 No BBDISPLAY address given - aborting
De : Ward, Martin [mailto:Martin.Ward at colt.net]
Envoyé : mardi 20 janvier 2009 10:45
À : hobbit at hswn.dk
Objet : RE: [hobbit] hoobit relay
I would recommend disabling bbproxy in your hobbitlaunch.cfg like this:
====
[bbproxy]
DISABLED
ENVFILE /usr/local/hobbit//server/etc/hobbitserver.cfg
CMD $BBHOME/bin/bbproxy --hobbitd --servers=192.168.252.80,$BBSERVERIP -report=192.168.252.78 --pidfile=$BBSERVERLOGS/bbproxy.pid
LOGFILE $BBSERVERLOGS/bbproxy.log
====
Then login as the hobbit user id, restart Hobbit so that the proxy isn't running:
$ server/hobbit.sh restart
and then run the bbproxy like this:
$ server/bin/bbcmdserver/bin/bbproxy --hobbitd --no-daemon --servers=192.168.252.80,$BBSERVERIP -report=192.168.252.78
If this works then you should start getting reports at your Hobbit master server from the proxy server, every five minutes.
|\/|artin
-----Original Message-----
From: Evelyne Simon [mailto:ESimon at aquitaine-valley.fr]
Sent: 20 January 2009 08:31
To: hobbit at hswn.dk
Subject: RE: [hobbit] hoobit relay
Hello
Excuse me but it's don't work again
[[bbproxy]
ENVFILE /usr/local/hobbit//server/etc/hobbitserver.cfg
CMD $BBHOME/bin/bbproxy --hobbitd --servers=192.168.252.80,$BBSERVERIP -report=192.168.252.78 --pidfile=$BBSERVERLOGS/bbproxy.pid
LOGFILE $BBSERVERLOGS/bbproxy.log
My bbproxy.log
Cannot bind to listen socket (Address already in use)
thanks
De : Ward, Martin [mailto:Martin.Ward at colt.net]
Envoyé : lundi 19 janvier 2009 17:42
À : hobbit at hswn.dk
Objet : RE: [hobbit] hoobit relay
The docs I have say that --BBDISPLAY is obsolete and to use --servers instead and specify all the servers in one go:
--servers ipmaster,$BBSERVERIP
I don't think you can put the--no-daemon option into your hobbitlaunch.cfg file. For testing purposes disable this entry and run bbproxy on the command line.
When you have bbproxy running tail the logs on your Hobbit master server to verify if the proxy is actually connecting or not. You should see if the proxy is connecting or not, which is the first step since the proxy doesn't seem to be talking to the master as yet...
|\/|artin
-----Original Message-----
From: Evelyne Simon [mailto:ESimon at aquitaine-valley.fr]
Sent: 19 January 2009 15:58
To: hobbit at hswn.dk
Subject: RE: [hobbit] hoobit relay
My client is a windows server and report to my bbproxy
My bbproxy :
[hobbitd]
DISABLED
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 --listening=127.0.0.1 --store-clientlogs=!msgs
[bbproxy]
ENVFILE /usr/local/hobbit//server/etc/hobbitserver.cfg
CMD $BBHOME/bin/bbproxy --hobbitd --bbdisplay=ip-master --bbdisplay=$BBSERVERIP --report=$MACHINE.bbproxy --no-daemon --pidfile=$BBSERVERLOGS/bbproxy.pid
LOGFILE $BBSERVERLOGS/bbproxy.log
Two problems :
On my bbproxy ihaven't display and on my master server no report
thanks
De : Ward, Martin [mailto:Martin.Ward at colt.net]
Envoyé : lundi 19 janvier 2009 16:21
À : hobbit at hswn.dk
Objet : RE: [hobbit] hoobit relay
OK, how have you configured your clients?
To help diagnosis you can run bbproxy in the foreground like so:
$ ~/server/bin/bbproxy --hobbitd --bbdisplay=$BBDISP --no-daemon --debug
Also, to ensure that your proxy server is talking to your master server you can use the report option (in non-debug mode or in debug mode):
$ ~/server/bin/bbproxy --report --hobbitd --bbdisplay=$BBDISP
|\/|artin
-----Original Message-----
From: Evelyne Simon [mailto:ESimon at aquitaine-valley.fr]
Sent: 19 January 2009 14:39
To: hobbit at hswn.dk
Subject: RE: [hobbit] hoobit relay
So, i configure my bbproxy server with parameters. It's ok
My logs
2009-01-19 14:27:22 Listening on 0.0.0.0:1984
2009-01-19 14:27:22 Sending to BBDISPLAY(s) xx.xx.xx.xx:1984
2009-01-19 14:27:22 Sending to BBPAGER(s) xx.Xx.xx.xx:1984
But I don't reports on master display server
Could you explain your configuration
Thanks
De : Ward, Martin [mailto:Martin.Ward at colt.net]
Envoyé : lundi 19 janvier 2009 15:05
À : hobbit at hswn.dk
Objet : RE: [hobbit] hoobit relay
Hi Simon,
You can run the bbproxy program with whatever flavour if parameters you need (check bbproxy man page), but this will work:
$ ~/server/bin/bbproxy --hobbitd --bbdisplay=$BBDISP
Then configure BBDISP in the .../etc/hobbitclient.cfg file on the remote clients to point to the IP address of the server running bbproxy.
HTH
|\/|artin
-----Original Message-----
From: Evelyne Simon [mailto:ESimon at aquitaine-valley.fr]
Sent: 19 January 2009 13:36
To: hobbit at hswn.dk
Subject: RE: [hobbit] hoobit relay
Yes, a function bbrelay exist
How can i configure it ?
thanks
De : Ward, Martin [mailto:Martin.Ward at colt.net]
Envoyé : lundi 19 janvier 2009 10:55
À : hobbit at hswn.dk
Objet : RE: [hobbit] hoobit relay
The bbproxy source code is held in source_dir/bbproxy/
If you have installed the Hobbit server then the bbproxy binaries will be in ~hobbit/server/bin/bbproxy
I would recommend looking at the man pages for bbproxy(8) and maybe bbmessage.cgi(8) as well.
Others may have example config files that I cannot provide which will help too.
|\/|artin
-----Original Message-----
From: Evelyne Simon [mailto:ESimon at aquitaine-valley.fr]
Sent: 19 January 2009 09:42
To: hobbit at hswn.dk
Subject: [hobbit] hoobit relay
Importance: High
Hello
I would install a bb relay on linux
How can I to do this
thanks
SIMON Evelyne
Aquitaine Valley
Rue de l'Hermite
BP 70081
33523 Bruges
tel : 05.56.11.91.72
Fax : 05.56.11.22.23
esimon at aquitaine-valley.fr
*************************************************************************************
The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way.
The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security at colt.net and delete the message and any attachments without retaining any copies.
Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses.
No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party.
Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.