On Thursday 02 August 2007 04:34, Mike D'Arcy wrote:
Hi Mike,
thanks for that information. Now I created a gluece-config.xml for
every GRAM MJFS and for the DefaultIndexService via the mds-gluerp-configure
tool:
===================
mds-gluerp-configure fork ganglia
/opt/d-grid/globus/gt405/etc/gram-service-Fork/gluerp-config.xml
mds-gluerp-configure pbs ganglia
/opt/d-grid/globus/gt405/etc/gram-service-PBS/gluerp-config.xml
mds-gluerp-configure gw ganglia
/opt/d-grid/globus/gt405/etc/gram-service-GW/gluerp-config.xml
mds-gluerp-configure none ganglia
/opt/d-grid/globus/gt405/etc/globus_wsrf_mds_index/ganglia-config.xml+
===================
This is my DefaultIndexService config:
=======================
<service name="DefaultIndexService" provider="Handler" use="literal"
style="document">
<parameter name="providers"
value="org.globus.mds.usefulrp.rpprovider.ResourcePropertyProviderCollection
org.globus.wsrf.impl.servicegroup.ServiceGroupRegistrationProvider
GetRPProvider
GetMRPProvider
QueryRPProvider
DestroyProvider
SetTerminationTimeProvider
SubscribeProvider
GetCurrentMessageProvider"/>
<parameter name="rpProviderConfigFile"
value="/etc/globus_wsrf_mds_index/ganglia-config.xml"/>
<parameter name="scope" value="Application"/>
<parameter name="allowedMethods" value="*"/>
<parameter name="handlerClass"
value="org.globus.axis.providers.RPCProvider"/>
<parameter name="className"
value="org.globus.mds.index.impl.DefaultIndexService"/>
<wsdlFile>share/schema/mds/index/index_service.wsdl</wsdlFile>
</service>
========================
Again, the Ganglia information appears in the container.log but not in the
services.
I guess this issue is related to:
2007-08-02 09:45:35,716 ERROR rpprovider.ResourcePropertyProviderTask
[Timer-4,timerExpired:159] Unhandled exception during execution of
org.globus.mds.usefulrp.glue.GangliaElementProducer :
java.lang.IllegalArgumentException: Argument name is null
Any ideas whats going wrong here?
Best wishes,
Thomas
> Hi Thomas,
>
> If you want to publish ganglia information in a GRAM MJFS (rather than
> the Index service), similar to 4.0.4, then there must be an appropriate
> configuration block in the "gluerp-config.xml" configuration file for
> each gram managed job factory service that is going to publish the data.
> By default, the system creates this file in the $G_L/etc dir of each
> GRAM MJFS that publishes the GLUECE RP.
>
> However, this default configuration file is only setup to enable the
> scheduler info provider. You have will have to manually enable support
> for ganglia or other custom info providers. This is similar to how
> 4.0.4 and previous releases worked. The main difference for the
> administrator now is that there is a bit more substance to the
> configuration file, which is actually a good thing since it allows much
> more parameter control than the previous mechanism did.
>
> There is a simple utility program called mds-gluerp-configure, located
> in $GLOBUS_LOCATION/bin, that you can use to generate a file with basic
> default settings for using the ganglia provider when ganglia is running
> on the local host and using the default port.
>
> Here's an example of running it for a GRAM PBS MJFS:
>
> mds-gluerp-congfigure pbs ganglia
> $GLOBUS_LOCATION/etc/grassm-service-PBS/gluerp-config.xml
>
>
> Looking at your example below, if you want to just setup ganglia for use
> in the Index Service you could do:
>
> mds-gluerp-congfigure none ganglia
> $GLOBUS_LOCATION/etc/globus_wsrf_mds_index/ganglia-config.xml
>
> But note that you would have to make sure the Index service descriptor
> "rpProviderConfigFile" parameter points to the "ganglia-config.xml" file
> that you generated, relative to the $G_L, as Neill mentioned.
>
> The configuration block that is generated by the program should not need
> to be modified if ganglia is running on the local host and port.
> Otherwise, simply edit the host/port arguments contained within the
> config file.
>
> Regards,
> Mike
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Neill Miller
> > Sent: Wednesday, August 01, 2007 7:43 AM
> > To: Thomas Bruesemeister
> > Cc: Gabriel Mateescu; [email protected]; Stefan Berner;
> > Helmut Heller; [EMAIL PROTECTED]
> > Subject: Re: [gt-user] GT4.0.5/MDS & Ganglia
> >
> > Hello Thomas,
> >
> > On Wed, Aug 01, 2007 at 10:35:26AM +0200, Thomas Bruesemeister wrote:
> > > I added the following line to the server-config.wsdd in
> >
> > $GLOBUS_LOCATION/etc/globus_wsrf_mds_index to
> >
> > > the DefaultIndexService element:
> > >
> > > <parameter name="rpProviderConfigFile"
> >
> > value="/opt/d-grid/globus/gt405/etc/globus_wsrf_mds_usefulrp/g
> > luece-rpprovider-config.xml"/>
> >
> > > The value attribute points to the absolute path of the
> >
> > rpprovider-config
> >
> > > which has been copied from the example
> >
> > (gluece-rpprovider-sample-config.xml):
> >
> > As the beginning of the documentation says, adding this line does
> > nothing without enabling the provider by adding the Java class file to
> > the server-config.wsdd file. Also, it doesn't want an absolute path,
> > but rather a path relative to the GLOBUS_LOCATION. For example, this
> > is what the example shows (and is probably what you want):
> >
> > <parameter name="rpProviderConfigFile"
> > value="/etc/globus_wsrf_mds_usefulrp/gluece-rpprovider-sample-
> > config.xml"/>
> >
> > I'd recommend copying the *entire* config block and cut and pasting it
> > to replace the default one so you can see the differences instead of
> > trying to add just the changes.
> >
> > > As far as I can estimate there are no changes required in
> >
> > this file (we use
> >
> > > PBS and a standard Ganglia Setup)
> >
> > Yes, that file should be ok for your setup it sounds.
> >
> > -Neill.
--
Thomas Bruesemeister
Astronomisches Rechen-Institut
am Zentrum für Astronomie
der Universität Heidelberg
Fon: +49 (0)6221 54-1834
Fax: +49 (0)6221 54-1888
[EMAIL PROTECTED]
