On Tue, 3 May 2005, Laurence wrote:
> Can you run on your MON node the following command
> /opt/edg/bin/rgma-client-check
[root@golias26 etc]# /opt/edg/bin/rgma-client-check
*** Running R-GMA client tests on golias26.farm.particle.cz ***
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 proxycache, 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 ***
--
Jiri Kosina
Institute of Physics, Academy of sciences of the Czech Republic
|