Hi Tom Thanks for the guidance. I have just built the machine for the bridge. I installed the AG software but only ran the BridgeServer.py I did not think about the bridgeserver needing the certificate installed. I'll try importing a certificate tomorrow. Regarding the sluggishness. I had a 1 Ghz P3 running Fedora. If I started the machine and ran the VenueServer and BridgeServer the first few connections were fine. After a short period of time any request for connection to the VenueServer took a very long time upto 5 mins before it would connect. I spoke to Paul from Manchester during the retreat and he commented that he had seen this before and that he thought it was due to the BridgeServer taking a lot of process time. He said it was better to run the BridgeServer on its own. I did a few experiments the other day and found that once the machine was in its slow state, killing the bridge allowed the Venue Server to respond very much faster. So it looks as if Pauls thoughts are correct. I have a spare 2.8GHz P4 so I thought I would put the bridgeserver on that and leave the venueserver on the P3 I'll keep you informed Mike Quoting "Thomas D. Uram" <tu...@mcs.anl.gov>:
> > > Mike Daley wrote: >> I have been running a Bridgeserver and venue server on the same >> machine for a while but it becomes very sluggish. >> I was advised to run the bridgeserver on another machine. > I'd be interested to know the reasons for the sluggishness. Can you > comment on that? >> From what I can see the config file would stay the same but I >> cannot see the bridge. >> Do I have to configure something in the Venue server to tell it >> where the bridge is. >> Any suggestions would be appreciated. >> Thanks >> Mike >> > I would check these couple things: > > - That the hostname of the venue server resolves properly from the > bridge machine. > - If you're bridging an entire venue server, check that the certificate > in use on the bridge > machine is authorized to make the GetVenues call on the venue server. > > Let us know if this resolves the problem (It creates a complete record > of the problem and > fix in the mailing list archives.) > > Tom ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
