Hi Tom: First, I followed the sample I found in the document entitled "How to Run a Bridge Server". On page 2 the format is described as:
[BridgeServer] # the id field is assigned by the system; users can omit this line id = <unique id of this bridge server> name = <name of your institution> location = <location of your institution> qbexec = /usr/bin/QuickBridge # ONE of the following mutually exclusive options can be specified venue = <URL of venue to bridge> venueFile = <file containing URLs of venues to bridge> venueServer = <URL of venue server to bridge> venueServerFile = <file containing URLs of venue servers to bridge> The latter part, that of the mutually exclusive parts, does not seem to agree with the format described in AccessGrid/bin/BridgeServer.py. There I read: [BridgeServer] name = Argonne location = Chicago qbexec = /usr/bin/QuickBridge # use this port range for the bridge server as a whole portMin = 30000 portMax = 40000 # Lobby of ag-2 server [https://ag-2:8000/Venues/default] type = Venue # use this special port range for this venue portMin = 24000 portMax = 24006 # Entire transitional venue server [https://vv2.mcs.anl.gov:9000/VenueServer] type = VenueServer Thanks, -- Socrates On Wed, 19 Jan 2005 17:39:29 -0600, Thomas D. Uram <[email protected]> wrote: > Socrates: > > I'd like to update the document if there's a problem. I know the document > describes the > config file used by the BridgeServer in both versions 2.2 and 2.3. If you > used the > appropriate example config, and there was a problem with it, let me know so I > can fix it. > > Thanks, > > Tom > > > Socrates wrote: > > Hi, > > > > Thanks for the response. > > > > In my case the problem has to do with wrong syntax in the > > BridgeServer's config file. I was following the guidelines I found in > > one of the docs in the toolkit describing the BridgeServer, but > > unfortunately the document is outdated. > > > > The source code (AccessGrid/bin/BridgeServer.py) has a working sample > > config in the beginning. > > > > QuickBridge process doesn't get killed though when BridgeServer quits. > > > > Thanks, > > -- > > Socrates. > > > > > > > > On Wed, 19 Jan 2005 13:00:55 -0800, Todd Zimmerman <[email protected]> wrote: > > > >>Not sure if this is your issue - but I've just run into something very > >>similar - it was caused by our bridgeserver certificate not being > >>authorized to connect to the venueserver (two different machines - two > >>different certificates). > >> > >>I added the bridgeserver DN to the venueserver administrators list and > >>it worked after that. > >> > >>Giving administrator access is a bit extreme, obviously - and I'd like > >>to narrow the scope of authorization; however, I wasn't sure which > >>'Actions' the bridgeserver was required to be authorized for. Any > >>advice from other admins would be great! > >> > >>Todd > >> > >>-- > >>Collaboration & Visualization Technician > >>WestGrid - www.westgrid.ca > >>IRMACS - www.irmacs.com > >>Ph. 604.268.6979 > >>Todd Zimmerman - [email protected] > >> > >> > >>Socrates wrote: > >> > >>>Hi, > >>> > >>>I'm trying to run a bridge on my local server but it doesn't seem to work. > >>> > >>>I start the BridgeServer.py script with a config file containing the > >>>URI of the server (want all Venues bridged). I start the Client on > >>>another machine but the "unicast" option in the menu is still grayed > >>>out. > >>> > >>>WiKi says that the Lucky Labrador Venue is bridged by Argonne: > >>>( > >>>http://www-unix.mcs.anl.gov/fl/research/accessgrid/wiki/moin.cgi/BridgedVenues > >>>) > >>> > >>>Starting my Client on that room doesn't enable "unicast" on the menu > >>>either. > >>> > >>>Any ideas? This is all Fedora Core 3. No errors reported in > >>>BridgeServer.log, VenueServer.log or VenueClient.log. > >>> > >>>Thanks, > >> > > > > > -- Socrates.
