[AG-TECH] AG3 Bridge issue

[Fred Dech]

Andrew,

That's encouraging to hear that some of the bugs are worked out in the
current CVS version.
I think I'll give that code a try.

Thanks.

--fred

On Fri, Apr 27, 2007 at 09:44AM, Andrew A Rowley said:
> Hi,
> 
> We used to have this problem with the bridge, but we are now running some of the CVS code for this, and it appears to be stable.  We found the issue was that the bridge appeared to be running out of ports (this would show up as a NoFreePortsError showing up in the VenueClient.log file when the client tries to use the bridge).  This was because the bridge was not indicating that the port was not in use when it detected the bridge process stopping.  The only difference between this and your problem was that the bridge continued to show in the list in our case, so this may be a different problem...
> 
> Regarding the problem with not having bridges listed, this will also be fixed in the next version - all bridges will be listed with a cache and also a choice of the ordering of the bridges.
> 
> 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 April 2007 18:37
> > To: Eddy Diaz
> > Cc: AG TECH
> > Subject: Re: [AG-TECH] AG3 Bridge issue
> > 
> > Same problem for me with Slackware 11.0. Its an ongoing problem. I
> > have to restart the Bridge, then restart the client several times
> > before our bridge is shown. In the next release will there be an
> > option to always use 1 bridge instead of having a list?
> > 
> > 
> > On 4/26/07, Eddy Diaz <edd-diaz at uniandes.edu.co> wrote:
> > > I have the same problem with fedora core 4 and 6
> > >
> > > Eddy Johel Diaz Murcia edd-diaz at uniandes.edu.co
> > > Estudiante de Maestría en Ingeniería de Sistemas y computación
> > > Asistente graduado del Grupo IMAGINE Universidad de los Andes
> > > Carrera 1 N° 18A-10 Bloque W, Bogotá, Colombia
> > > Laboratorio de Informática Gráfica Teléfono: +57(1) 339 4949 Extensión
> > 3462
> > >
> > >
> > > -----Mensaje original-----
> > > De: owner-ag-tech at mcs.anl.gov [mailto:owner-ag-tech at mcs.anl.gov] En
> > nombre
> > > de Fred Dech
> > > Enviado el: Jueves, 26 de Abril de 2007 10:36 a.m.
> > > Para: AG TECH
> > > Asunto: [AG-TECH] AG3 Bridge issue
> > >
> > > Hi.
> > >
> > > I've been running a bridge on and off for some time and still run into
> > > the same annoying issue.  After the Bridge process runs for some period
> > of
> > > time and the amount of activity (Quickbridge processes spawned and
> > > destroyed)
> > > goes past a certain point, the Bridge stops functioning properly.  It no
> > > longer identifies itself to the registry and no new entries are added
> > > to the log file.  I've tried different FC5 and FC6 platforms, assuming
> > that
> > > this problem was machine specific, but this behavior has not changed.  I
> > > also tried running Bridge as root, thinking that I was running into some
> > > kind
> > > of restricted buffer limit.  No difference.
> > >
> > > The last thing normally logged is some attempts to create new bridges:
> > > 04/25/07 14:26:31 -1208707392 Toolkit     Bridge:57 INFO  Bridge
> > request:
> > > mcast 224.2.207.27 59822
> > > 04/25/07 14:26:31 -1208707392 Toolkit     BridgeFactory.py:110 INFO
> > Method
> > > CreateBridge called
> > > 04/25/07 14:26:31 -1208707392 Toolkit     BridgeFactory.py:116 INFO
> > > Allocated port = 50076
> > > 04/25/07 14:26:31 -1208707392 Toolkit     BridgeFactory.py:123 INFO  -
> > using
> > > existing bridge
> > >
> > > and the BridgeFactory uses an existing bridge.
> > >
> > > Then the last item in the log is usually the destruction of all the
> > bridges.
> > > After that the Bridge might as well not be running, because it doesn't
> > show
> > > up in the registry.
> > > The only think to do at this point is to kill and restart the bridge.
> > >
> > > Does this sound familiar to anyone?
> > > I'd appreciate any comments or suggestions.
> > >
> > > Thanks.
> > >
> > > --fred
> > >
> > >
> >