[AG-TECH] AG 2.4 and 3.0 servers

[Jeremy Mann]

Andrew, thank you very much for the answer to my question. I now have
AG3.0.2 with a bridge on our 2.4 server living happily together. One
more question though, I see the text chat is now Jabber so I assume I
have to install a Jabber server so text chat will work. What do you
recommend as the Jabber server? I'm running Linux BTW.


On 9/27/06, Andrew A Rowley <Andrew.Rowley at manchester.ac.uk> wrote:
> Hi,
>
> The config for bridge3.py is all on the command line e.g.:
> Bridge -p <listenport> -r <udpStart> <udpEnd> -n <name> -l <location> -u http://www.accessgrid.org/registry/peers.txt
>
> where <listenport> is the tcp port your bridge listens to requests on, <udpStart> to <udpEnd> is the port range that will be used by the bridge, <name> is the name of your bridge that will appear in the list and <location> is where your bridge is (displayed in the preferences).  The "-u" option allows you to specify the registry.  This is best left as above for now.
>
> I think the client will choose the bridge with the smallest ping time by default, so it should choose your own one, but you can make it by selecting yours from the list instead of selecting "Unicast".
>
> Andrew :)
>
> ============================================
> Access Grid Support Centre,
> RSS Group,
> Manchester Computing,
> Kilburn Building,
> University of Manchester,
> Oxford Road,
> Manchester,
> M13 9PL,
> UK
> Tel: +44(0)161-275 0685
> Email: Andrew.Rowley at manchester.ac.uk
>
> > -----Original Message-----
> > From: owner-ag-tech at mcs.anl.gov [mailto:owner-ag-tech at mcs.anl.gov] On
> > Behalf Of Jeremy Mann
> > Sent: 26 September 2006 15:43
> > To: Thomas D. Uram
> > Cc: ag-tech at mcs.anl.gov
> > Subject: Re: [AG-TECH] AG 2.4 and 3.0 servers
> >
> > Thanks the reply Tom. Fortunately, I figured that out a few minutes
> > after sending the message ;) One more thing though, is the bridge3.py
> > config file the same as 2.4? Also, if I host a bridge for 3.0.2 will
> > the client automatically choose the local bridge or will it choose one
> > of the preconfigured unicast bridges?
> >
> >
> > On 9/26/06, Thomas D. Uram <turam at mcs.anl.gov> wrote:
> > > Jeremy:
> > >
> > > The main port for the server is specified on the command line.
> > > You need to add this option to the command line:
> > >
> > > --port=9000
> > >
> > > It's been suggested that this be added to the config file to avoid
> > > this problem.
> > >
> > > Tom
> > >
> > >
> > > On 9/26/06 9:08 AM, Jeremy Mann wrote:
> > > > I'm trying to configure an AG 3.x server to work on our AG 2.4
> > > > machine. Everything installed fine and I've searched this mailing list
> > > > for the requirements to run them on the same machine. I have 2.4 on
> > > > the  800x ports and 3.0 on 900x. However, when I start the
> > > > VenueServer3.py with my config file it says:
> > > >
> > > > ag at ag1:~$ VenueServer3.py -c VenueServer3.cfg
> > > > Network error running server; an application is already running on one
> > > > of the ports required
> > > >
> > > > My config file is:
> > > >
> > > > [VenueServer]
> > > > defaultVenue = 00000108b4c7937d0081006f004500a70fd
> > > > performanceReportFile =
> > > > dataStorageLocation = Data
> > > > venuePathPrefix = Venues
> > > > eventPort = 9002
> > > > serverPrefix = VenueServer
> > > > performanceReportFrequency = 0
> > > > encryptAllMedia = 1
> > > > addressMask = 17
> > > > addressAllocationMethod = random
> > > > dataPort = 9006
> > > > textPort = 9004
> > > > baseAddress = 224.2.230.0
> > > > houseKeeperFrequency = 300
> > > > persistenceFilename = VenueServer3.dat
> > > > backupServer =
> > > >
> > > > Thanks for any help!
> > > >
> > > >
> > >
> >
> >
> > --
> > Jeremy
> >
>
>


-- 
Jeremy