On Sat, Apr 30, 2005 at 06:56:27PM +0200, David Groep wrote:
> Hi Torsten,
>
> Below is en excerpt from our syslog:
>
> * RGMA ("glite" version 4.0) is ********* broken again, and the error
> messages are close to useless:
>
> rgma> latest select * from ServiceStatus;
> RGMA exception occurred: Consumer__start_Timeinterval:HTML
> returned instead of XML. This usually means either there is a problem
> with the proxy cache, e.g. it is unable to find the R-GMA server; or an
> unhandled exception in the R-GMA servlet. The title of the HTML document
> is: Apache Tomcat/4.1 - Error report
>
> does not make much sens if the underlying error is not shown. I had
> to use tcpdump to get that error, which traces down to missing JARs
> in the distribution (see "Kyriakos G. Ginis" mail on LCG-ROLLOUT titled
> Re: [LCG-ROLLOUT] R-GMA and LCG-2.4.0 for the solution).
>
> But try this:
>
> The solution may be to uninstall and re-install the tomcat4 and
> edg-java-security
> RPMs. see:
>
> http://www.listserv.rl.ac.uk/cgi-bin/webadmin?A2=ind0504&L=lcg-rollout&F=&S=&P=35907
>
This problem was seen during the EGEE3 meeting in Athens - Laurence
and others were working on it. Haven't the instructions been updated
yet?
Steve
> (thanks again Kyriakos for saving my day :-)
>
> When I get to it I'll file a bugreport on R-GMA since from TCP-DUMP I
> *did* get a decent error message. R-GMA just did not propagate the useful
> stuff to the
> user :-)
>
>
>
> Torsten Harenberg wrote:
> >Dear list,
> >
> >after upgrading to 2.4 I get negative results from the rgma-client-check
> >script:
> >
> >bash-2.05a$ /opt/edg/bin/rgma-client-check
> >
> >*** Running R-GMA client tests on grid-lcg.physik.uni-wuppertal.de ***
> >
> >Checking C API: Failed to declare table.
> ><Error parsing XMLResponse from servlet (may just the servlet URL that
> >is wrong - check rgma.conf).>
> >Failure
> >Checking C++ API: R-GMA application error in PrimaryProducer.
> >HTML returned instead of XML. This usually means either there is a
> >problem with the proxy cache, e.g. it is unable to find the R-GMA
> >server; or an unhandled exception in the R-GMA servlet. The title of
> >the HTML document is: Apache Tomcat/4.1 - Error report
> >Success
> >Checking Python API: RGMA Error
> >StreamProducer__declareTable_StringString:HTML returned instead of XML.
> >This usually means either there is a problem with the proxy cache, e.g.
> >it is unable to find the R-GMA server; or an unhandled exception in the
> >R-GMA servlet. The title of the HTML document is: Apache Tomcat/4.1 -
> >Error report
> >
> >Failure
> >Checking Java API: Failed to contact PrimaryProducer service.
> >org.glite.rgma.RemoteException
> > at org.glite.rgma.stubs.PrimaryProducerStub.declareTable(Unknown
> >Source) at PrimaryProducerExample.main(Unknown Source)
> >Failure
> >
> >Checking for safe arrival of tuples, please wait... ERROR: Failed to
> >instantiate Consumer
> >There should be 4 tuples, there was only:
> >
> >*** R-GMA client test failed ***
> >
> >bash-2.05a$
> >bash-2.05a$ cat /opt/edg/etc/rgma/rgma.conf
> >Archiver=http://grid-lcg.physik.uni-wuppertal.de:8080/R-GMA/ArchiverServlet
> >Consumer=http://grid-lcg.physik.uni-wuppertal.de:8080/R-GMA/ConsumerServlet
> >StreamProducer=http://grid-lcg.physik.uni-wuppertal.de:8080/R-GMA/StreamProducerServlet
> >
> >LatestProducer=http://grid-lcg.physik.uni-wuppertal.de:8080/R-GMA/LatestProducerServlet
> >
> >CanonicalProducer=http://grid-lcg.physik.uni-wuppertal.de:8080/R-GMA/CanonicalProducerServlet
> >
> >DataBaseProducer=http://grid-lcg.physik.uni-wuppertal.de:8080/R-GMA/DBProducerServlet
> >
> >Registry=http://lcgic01.gridpp.rl.ac.uk:8080/R-GMA/RegistryServlet
> >Schema=http://lcgic01.gridpp.rl.ac.uk:8080/R-GMA/SchemaServlet
> >XMLConverter=/opt/edg/etc/rgma/XMLResponse.xsd
> >leapsecLocation=/opt/edg/etc/rgma/leapsec.dat
> >
> >Any ideas where to look?
> >
> >Thanks,
> >
> > Torsten
> >
> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
> ><> <>
> ><> Torsten Harenberg [log in to unmask] <>
> ><> Bergische Universitaet <>
> ><> FB C - Physik Tel.: +49 (0)202 439-3521 <>
> ><> Gaussstr. 20 Fax : +49 (0)202 439-2811 <>
> ><> 42097 Wuppertal <>
> ><> <>
> ><><><><><><><>< Of course it runs NetBSD http://www.netbsd.org ><>
