I can confirm that there are problems with R-GMA but the problems are
not specifically with the registry we are attempting to track down and
resolve the problems.
There are a few sites that have reconfigured their MON boxes as secure
but have not opened up their firewalls to allow access via the secure
port( default 8443 ). This is causing us some problems tracing the
problems and so we will be asking that the offending sites be added to
the deny policy of the ACL at the registry until it is confirmed that
access can be obtained.
Alastair
On Thu, 2005-12-15 at 17:44, David McBride wrote:
> On Thu, 2005-12-15 at 16:59 +0000, Alastair Duncan wrote:
>
> > Hi David,
> >
> > Could you confirm what rgma rpm versions you are using on the server and
> > client please.
>
> The clients are using whatever is included with the relocatable
> worker-node tar-ball distribution dated October 19th. (An update of the
> client-side distribution is blocked pending an updated release actually
> being available!)
>
> Ther version numbers for the server-side R-GMA packages are
> inconsistent:
>
> % rpm -qa|grep rgma
> glite-rgma-api-cpp-4.1.14-1
> glite-rgma-stubs-servlet-java-4.1.12-1
> glite-rgma-log4j-4.1.5-1
> glite-rgma-log4cpp-4.1.4-0
> glite-rgma-api-python-4.1.13-1
> glite-rgma-api-java-4.1.5-1
> glite-rgma-command-line-4.1.13-1
> glite-rgma-gin-4.1.16-1
> glite-rgma-base-4.1.19-1
> glite-rgma-api-c-4.1.11-1
> glite-rgma-system-tests-4.1.7-1
>
> I am attempting an upgrade to the versions currently available in the
> LCG-2_6_0 updates directory, however this is blocked pending a
> resolution of various package conflicts between the LCG and RHEL
> repositories.[*].
>
> Let me know if you require further information.
>
> Cheers,
> David
>
> [* Grr; LCG should _not_ be distributing packages provided by the base
> distribution in their archive -- RHEL already provide a version of
> Net::SSLeay that works, thankyouverymuch..]
|