[AG-TECH] Network and Bridge Questions

[Christoph Willing]

On 16/11/2011, at 2:39 PM, Christoph Willing wrote:

> I think I've found the problem - the previous fix was incomplete. In
> fact the previous fix worked with python 2.6 systems (which is what we
> were concerned about at the time) but gave the problem to python 2.5
> systems which were OK before the fix.
>
> I'll submit the fix and build new Debuntu

A new accessgrid3.2 package which includes the new fix is now  
available for Debian Squeeze - just update/upgrade.


chris


> & Slackware packages and
> Doug will hopefully make new packages for Fedora etc. However it may
> take a while before they're all done; if you want to manually fix
> existing installations, here are the steps:
>
> 1. find the file AGXMLRPCServer.py
>    (on lenny, /usr/lib/pymodules/python2.{5,6}/AccessGrid3/AccessGrid/
> AGXMLRPCServer.py)
>    In that file, search for the line:
>         if sys.version < (2,6):
>    change it to
>         if sys.version_info < (2,6):
>
> 2. in that same file, near the beginning before all the import lines,
> insert a new line:
>        import sys
>
>
> chris
>
>
> On 15/11/2011, at 10:42 PM, Miguel A. Sáez Llorente wrote:
>
>> On 11/11/2011, at 4:24 AM, JULIAN CASTRO wrote:
>>> And second, we have a problem with our bridge trying to make it
>>> appear in the list of bridges: clients can see the bridge when
>>> clicking in “find additional bridges” but only in the first 5
>>> minutes after starting the bridge in the server. After that, no
>>> client can see the bridge, but if it is in the cache of bridges it
>>> is possible to connect to the bridge and it works. The problem is
>>> “discovering the bridge”. If we copy the cache file with our bridge
>>> on it in the clients pc´s,  they can connect to the bridge but it
>>> is not a good approach.
>>
>> Hello,
>>
>> I'm having exactly the same issue. I recently migrated my AG server
>> to a new machine with a Debian Squeeze (2.6.32-5-686). I can start
>> the bridge without any problem. Here is the the 'ps' output:
>>
>> 1201      2146 11.0 10.5  49336 26712 ?        S    13:15   0:00 /
>> usr/bin/python /usr/bin/Bridge3.py --name=ES.USC --location=Spain --
>> registryUrl=http://www.accessgrid.org/registry/peers.txt
>>
>> But, same as Julian, the clients can only see the bridge the first
>> few minutes after starting the bridge... I also get a new process
>> running when this happens:
>>
>> 1201      2418  0.3  0.2   1736   640 ?        S    13:20   0:00 /
>> usr/bin/QuickBridge -g 233.4.200.18 -m 10002 -u 51688 -i 600
>>
>> At first i thought it was because i wasn't declaring some of the
>> variables like the --registryurl but doing so doesn't help either.
>> I also tried running the bridge manually instead of running it as a
>> service inside an script: Bridge3.py -n ES.USC -l Spain .
>>
>> And last, i also made sure my server is using python2.5 as default
>> instead of 2.6 if that helps with something.
>>
>> Any help on this will be very much appreciated.
>>
>> Regards,
>> -- 
>> ====================================================
>> Miguel A. Sáez Llorente
>> Soporte tareas multimedia - ATIC
>>
>> Univ. Santiago de Compostela (USC)
>> Rúa de José María Suárez Núñez (Campus Sur) - Pavellón de Servicios
>> 15705 Santiago de Compostela - SPAIN
>>
>> E-mail: miguelangel.saez at usc.es
>> Tel:    (+34 881811000) ext. 13035 / Directo 881813035
>> Tel AG: (+34 881811000) ext. 16273 / Directo 881970144
>> Fax:    +34  981547070
>> Web:    http://www.usc.es/atic
>>
>> https://connectnow.acrobat.com/miguelangelsaez770
>>
>> ====================================================
>
> Christoph Willing              +61 7 3365 8316
> Research Computing Centre
> University of Queensland
>
>
>

Christoph Willing              +61 7 3365 8316
Research Computing Centre
University of Queensland