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 <[email protected]> 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@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
