It's a known shortcoming of the venue tree view that it recurses; we should terminate the tree.
If you could file the bug re: authorizationPolicy, that'd be great. Thanks, Tom On 8/7/06 2:45 PM, Derek Piper wrote: > > Okay, thanks. > > Sure enough doing: > > cat ../VenueServer/VenueServer.cfg | grep -v 'authorizationPolicy' > >VenueServer.cfg > > cat ../VenueServer/VenueServer.dat | grep -v 'authorizationPolicy' > >VenueServer.dat > > And then editing the AG3 VenueServer.cfg for the correct ports > yields a working AG3 and AG2 venue server with the same rooms on the > same machine. The AG2 exits/links makes the tree layout on AG3 a bit > strange since it then recurses infinitely. What's the 'approved' way > to lay out rooms on AG3? Exits back to the root? > I'll file it as a bug if you like, Tom? > > Thanks, > > Derek > > Thomas D. Uram wrote: >> Using an AG2 VenueServer.dat will work fine, with one revision: You >> should remove the 'authorizationPolicy' lines >> from VenueServer.dat. AG3 runs into trouble with those existing >> lines. This should be filed as a bug. >> >> Tom >> >> >> On 8/7/06 2:17 PM, Derek Piper wrote: >> >>> >>> Thanks, Tom, for the clarification. I've tried again this time >>> running AG2 as 900x and AG3 as 800x. I have both of them running, >>> AG2 clients can connect (I realized my problem before was that the >>> AG3 Venue Server just wouldn't die until it was sent a -9). The AG3 >>> venue server config has 5223 in its 'textPort' field now. >>> AG3 clients however still cannot connect, even with its default >>> settings (which seems that my problems are somewhere else). I get a >>> 'HTTP Digest Authorization Failed' error from the AG3 venue client >>> when trying to connect to it. Both machines are using AG 3.0.1 (the >>> Fedora Core 5 venue server machine, and the Windows client machine). >>> In starting the AG3 venue server, I copied the previous venue >>> server (2.4) data to a new directory and the AG3 venue server is >>> started from there. Is that a good idea? Will that work to recreate >>> the same setup that I have with the 2.x venue server? >>> >>> Derek >>> >>> Thomas D. Uram wrote: >>> >>>> A little clarification: >>>> >>>> - the --port argument only specifies the main port, not the related >>>> (event,data,text) ports (unfrotunately) >>>> - the event,data,text ports are specified only in the cfg file >>>> - text does _not_ use 9004 or similar in AG3; instead, textHost and >>>> textPort point at a >>>> Jabber server (using jabber.mcs.anl.gov:5223 by default) >>>> >>>> Derek: >>>> >>>> I'd suggest you modify the AG3 venueserver.cfg to specify: >>>> >>>> textHost = jabber.mcs.anl.gov >>>> textPort = 5223 >>>> >>>> and then try to start it. If you want to use your own jabber >>>> server instead, >>>> you would modify textHost accordingly. >>>> >>>> Tom >>>> >>>> >>>> >>>> >>>> On 8/7/06 12:58 PM, Derek Piper wrote: >>>> >>>>> >>>>> Yes, I originally had my 2.x server at port 8000, apparently >>>>> the default. So.. now we have two incompatible venue servers that >>>>> all want to be the same default? That was a smart idea :> >>>>> Since I already have 2.x installations around that use the one >>>>> on port 8000 as a default/home venue, I thought I'd just add AG3 >>>>> on as port 9000. Now, I guess it's possible to try it the other >>>>> way and just run to all my installations and change them. In >>>>> trying to run the AG2 venue server on port 900x, it doesn't start >>>>> its text chat thing on port 9004 either. Nothing's running on that >>>>> port. And, just like it was with AG3, a venue client can't connect >>>>> to it. >>>>> I have the ports specified in VenueServer.cfg. All, but the >>>>> 'textPort' one seem to work. The text chat thing isn't even trying >>>>> to bind to port 8004 either, so I'm not sure what's up with that. >>>>> Do I have to redo my venue server from scratch if I change the port? >>>>> I was specifying the text, event and date ports for AG3, yes. >>>>> I had them set to the 900x equivalants and a venue client couldn't >>>>> connect to it. >>>>> >>>>> Derek >>>>> >>>>> Michael Miller wrote: >>>>> >>>>>> Derek, >>>>>> >>>>>> I run AG2 on port 900x and AG3 on 800x. I specify the text, >>>>>> event and data ports for AG2 in VenueServer.cfg and everything >>>>>> seems to work fine. Are you specifying the text,event and data >>>>>> ports for AG3? >>>>>> >>>>>> myk >>>>>> >>>>>> Derek Piper wrote: >>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I've installed AG2 and AG3 venue servers on one machine, >>>>>>> with the idea of having them co-exist but running on different >>>>>>> ports. I noticed that even if I specify a port of 9000 to the >>>>>>> AG3 venue server, it still wants to listen on 8002 etc. That >>>>>>> seems a bit unhelpful. I've been able to get both of them >>>>>>> running by having a VenueServer.cfg file but, but the AG3 >>>>>>> VenueServer isn't listening for its text chat port of 9004. Does >>>>>>> the AG3 VenueServer have to listen on port 8000? I don't really >>>>>>> want to have yet another box just to run the venue server, but >>>>>>> is that the only recommended way of setting them up? >>>>>>> Another question related to this is about keeping the two >>>>>>> venue servers synchronized. For the time being, it's going to be >>>>>>> likely to have to run both side by side. It would be nice if the >>>>>>> configuration from one could be mirrored from another and >>>>>>> synchronized either by a manual or automatic operation without >>>>>>> having to perform the same edits in each. >>>>>>> Hints are appreciated. Thanks, >>>>>>> >>>>>>> Derek >>>>>>> >>>>>> >>>>> >>>> >>>> >>> >> >
