This issue has been resolved. Wanted to let others know what the issue
was.
My $GLOBUS_LOCATION/etc/globus_wsrf_gram_LSF/gluerp-config.xml had
<?xml version="1.0" encoding="UTF-8"?>
<!-- Configuration file for the MDS GLUECE resource property provider
-->
<ns1:ResourcePropertyProviderConfigArray xmlns:ns1="http://mds.globus.org/rpprovider/2005/08
">
<ns1:resourcePropertyProviderConfiguration>
<ns1:resourcePropertyName xmlns:mds="http://mds.globus.org/glue/ce/1.1
">
mds:GLUECE </ns1:resourcePropertyName>
<ns1:resourcePropertyImpl>
org.globus.mds.usefulrp.rpprovider.GLUEResourceProperty </
ns1:resourcePropertyImpl>
<ns1:resourcePropertyElementProducers>
<ns1:className>
org
globus
mds.usefulrp.rpprovider.producers.SchedulerInfoElementProducer </
ns1:className>
<ns1:arguments>
libexec/globus-scheduler-provider-lsf </ns1:arguments>
<ns1:transformClass>
org
globus
mds.usefulrp.rpprovider.transforms.GLUESchedulerElementTransform </
ns1:transformClass>
<ns1:period>
300 </ns1:period>
<ns1:className>
org.globus.mds.usefulrp.glue.GangliaElementProducer
</ns1:className>
<ns1:arguments>
<myhostnamehere>
</ns1:arguments>
<ns1:arguments>
<myportnumberhere>
</ns1:arguments>
<ns1:transformClass>
org
globus.mds.usefulrp.rpprovider.transforms.GLUEComputeElementTransform
</ns1:transformClass>
<ns1:period>
300
</ns1:period>
</ns1:resourcePropertyElementProducers>
</ns1:resourcePropertyProviderConfiguration>
</ns1:ResourcePropertyProviderConfigArray>
It had to be
<?xml version="1.0" encoding="UTF-8"?>
<!-- Configuration file for the MDS GLUECE resource property provider
-->
<ns1:ResourcePropertyProviderConfigArray xmlns:ns1="http://mds.globus.org/rpprovider/2005/08
">
<ns1:resourcePropertyProviderConfiguration>
<ns1:resourcePropertyName xmlns:mds="http://mds.globus.org/glue/ce/1.1
">
mds:GLUECE </ns1:resourcePropertyName>
<ns1:resourcePropertyImpl>
org.globus.mds.usefulrp.rpprovider.GLUEResourceProperty </
ns1:resourcePropertyImpl>
<ns1:resourcePropertyElementProducers>
<ns1:className>
org
globus
mds.usefulrp.rpprovider.producers.SchedulerInfoElementProducer </
ns1:className>
<ns1:arguments>
libexec/globus-scheduler-provider-lsf </ns1:arguments>
<ns1:transformClass>
org
globus
mds.usefulrp.rpprovider.transforms.GLUESchedulerElementTransform </
ns1:transformClass>
<ns1:period>
300 </ns1:period>
</ns1:resourcePropertyElementProducers>
<ns1:resourcePropertyElementProducers>
<ns1:className>
org.globus.mds.usefulrp.glue.GangliaElementProducer
</ns1:className>
<ns1:arguments>
<myhostnamehere>
</ns1:arguments>
<ns1:arguments>
< myportnumberhere>
</ns1:arguments>
<ns1:transformClass>
org
globus.mds.usefulrp.rpprovider.transforms.GLUEComputeElementTransform
</ns1:transformClass>
<ns1:period>
300
</ns1:period>
</ns1:resourcePropertyElementProducers>
</ns1:resourcePropertyProviderConfiguration>
</ns1:ResourcePropertyProviderConfigArray>
That fixed it.
Prakash
On Oct 20, 2010, at 5:40 PM, Prakash Velayutham wrote:
Hi,
I am running GT 4.2.1 and GridWay 5.6.1.
I installed the Globus Toolkit with LSF as the local DRMS. After the
installation, I was able to lookup partial information about LSF
(queues, free nodes, slots etc.), like GridWay's gwhost comes up
with NULL values for most information except free/used/total slots
where it showed the correct values. So, my gridway jobs will stay
pending all the time.
To give more info, wsrf-query shows info about the scheduler
(queues) if I disable ganglia glue portion, and obviously does not
show information about the compute elements themselves. Once I
enable ganglia glue, information about the compute hosts show up in
wsrf-query, but LSF queue information is lost.
I followed the Ganglia GLUE documentation, added that piece and
gwhost now shows good information about everything, but has lost the
free/used/total slots information. So, gridway is still unable to
submit jobs to the DRMS.
Anyone here that can help?
Thanks,
Prakash
