Hi, Sorry, my bad, replace "ForkResourceConfiguration" in $GLOBUS_LOCATION/etc/gram-service-Loadleveler/jndi-config.xml by "LoadlevelerResourceConfiguration" and maybe "<!-- LRM configuration: Fork -->" by "<!-- LRM configuration: Loadleveler -->"
-Martin Asish M Madhu wrote: > Hello, > > I did as you said. But while starting container I am getting below error: > > > > ------------------------------------------------------------------------------ > > 2009-08-25 18:00:41,383 ERROR digester.Digester [main,java:?] End event > threw exception > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62) > at java.lang.reflect.Method.invoke(Method.java:391) > at > org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:252) > at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:256) > at org.apache.commons.digester.Rule.end(Rule.java:276) > at > org.apache.commons.digester.Digester.endElement(Digester.java(Compiled > Code)) > at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown > Source) > at > org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown > Source) > at > org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown > Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at org.apache.commons.digester.Digester.parse(Digester.java:1567) > at > org.globus.wsrf.jndi.JNDIUtils.parseJNDIConfig(JNDIUtils.java:202) > at > org.globus.wsrf.jndi.JNDIUtils.processJNDIFile(JNDIUtils.java:303) > at org.globus.wsrf.jndi.JNDIUtils.initializeDir(JNDIUtils.java:275) > at > org.globus.wsrf.container.ServiceManager.start(ServiceManager.java:132) > at > org.globus.wsrf.container.ServiceDispatcher.init(ServiceDispatcher.java:127) > at > org.globus.wsrf.container.GSIServiceDispatcher.init(GSIServiceContainer.java:93) > at > org.globus.wsrf.container.ServiceContainer.start(ServiceContainer.java:242) > at > org.globus.wsrf.container.ServiceContainer.<init>(ServiceContainer.java:197) > at > org.globus.wsrf.container.GSIServiceContainer.<init>(GSIServiceContainer.java:45) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:44) > at java.lang.reflect.Constructor.newInstance(Constructor.java:315) > at > org.globus.wsrf.container.ServiceContainer.createContainer(ServiceContainer.java:138) > at > org.globus.wsrf.container.ServiceContainer.startSecurityContainer(ServiceContainer.java:452) > at > org.globus.wsrf.container.ServiceContainer.main(ServiceContainer.java:408) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) > at java.lang.reflect.Method.invoke(Method.java:391) > at org.globus.bootstrap.BootstrapBase.launch(BootstrapBase.java:95) > at org.globus.bootstrap.Bootstrap.main(Bootstrap.java:37) > Caused by: javax.naming.NameAlreadyBoundException: Name > ForkResourceConfiguration is already bound in this Context > at org.apache.naming.NamingContext.bind(Unknown Source) > at org.apache.naming.NamingContext.bind(Unknown Source) > at org.apache.naming.NamingContext.bind(Unknown Source) > at org.apache.naming.SynchronizedContext.bind(Unknown Source) > at > org.globus.wsrf.jndi.NamingContext.addServiceResource(NamingContext.java:210) > at > org.globus.wsrf.jndi.NamingContext.addService(NamingContext.java:288) > at > org.globus.wsrf.jndi.NamingContext.addSubContext(NamingContext.java:233) > ... 39 more > Failed to start container: Container failed to initialize [Caused by: Failed > to read > '/usr/local/GARUDA/GLOBUS-4.0.7/etc/gram-service-Loadleveler/jndi-config > .xml' JNDI configuration file] > > > -------------------------------------------------------------------------------------------------------------- > > I checked the permission for the file jndi-config. It was okey. What could > be the problem? > > > > Thanking you > > Asish > > On Tue, Aug 25, 2009 at 5:18 PM, Martin Feller <[email protected]> wrote: > >> Hi >> >> Replace it by this, but substitute ${GLOBUS_LOCATION} with the >> value of the environment variable ${GLOBUS_LOCATION} >> >> <?xml version="1.0" encoding="UTF-8"?> >> <jndiConfig xmlns="http://wsrf.globus.org/jndi/config";> >> >> <!-- Configuration delta (addition) fpr a Local Resource Manager --> >> >> <!-- Configuration for Managed Job *Factory* Service --> >> >> <service name="ManagedJobFactoryService"> >> <!-- LRM configuration: Fork --> >> <resource >> name="ForkResourceConfiguration" >> >> type="org.globus.exec.service.factory.FactoryResourceConfiguration"> >> <resourceParams> >> <parameter> >> <name> >> factory >> </name> >> <value> >> org.globus.wsrf.jndi.BeanFactory >> </value> >> </parameter> >> <parameter> >> <name> >> localResourceManagerName >> </name> >> <value> >> Loadleveler >> </value> >> </parameter> >> <!-- Site-specific scratchDir >> Default: ${GLOBUS_USER_HOME}/.globus/scratch >> <parameter> >> <name> >> scratchDirectory >> </name> >> <value> >> ${GLOBUS_USER_HOME}/.globus/scratch >> </value> >> </parameter> >> --> >> <parameter> >> <name> >> substitutionDefinitionsFile >> </name> >> <value> >> >> ${GLOBUS_LOCATION}/etc/gram-service-Fork/substitution-definition.properties >> </value> >> </parameter> >> <parameter> >> <name> >> substitutionDefinitionsRefreshPeriod >> </name> >> <value> >> <!-- MINUTES --> >> 480 >> </value> >> </parameter> >> <parameter> >> <name> >> enableDefaultSoftwareEnvironment >> </name> >> <value> >> false >> </value> >> </parameter> >> </resourceParams> >> </resource> >> >> </service> >> >> >> </jndiConfig> >> >> >> -Martin >> >> Asish M Madhu wrote: >>> Hello Martin, >>> >>> Please find the content of jndi-config.xml >>> ($GLOBUS_LOCATION/etc/gram-service-Loadleveler/jndi-config.xml) >>> >>> >>> >>> >> ------------------------------------------------------------------------------------------------------------- >>> <?xml version="1.0" encoding="UTF-8"?> >>> <jndiConfig xmlns="http://wsrf.globus.org/jndi/config";> >>> >>> <!-- Configuration delta (addition) fpr a Local Resource Manager --> >>> >>> <!-- Configuration for Managed Job *Factory* Service --> >>> >>> <service name="ManagedJobFactoryService"> >>> <!-- LRM configuration: Loadleveler --> >>> <resource >>> name="LoadlevelerResourceConfiguration" >>> >>> type="org.globus.exec.service.factory.FactoryResourceConfiguration"> >>> <resourceParams> >>> <parameter> >>> <name> >>> factory >>> </name> >>> <value> >>> org.globus.wsrf.jndi.BeanFactory >>> </value> >>> </parameter> >>> <parameter> >>> <name> >>> localResourceManagerName >>> </name> >>> <value> >>> Loadleveler >>> </value> >>> </parameter> >>> <parameter> >>> <name> >>> scratchDirectory >>> </name> >>> <value> >>> /.globus/scratch >>> </value> >>> </parameter> >>> </resourceParams> >>> </resource> >>> >>> </service> >>> >>> >>> </jndiConfig> >>> >>> >> ---------------------------------------------------------------------------------------------------------- >>> Thanking you >>> >>> Regards >>> Asish >>> >>> On Tue, Aug 25, 2009 at 5:03 PM, Martin Feller <[email protected]> >> wrote: >>>> We don't officially support LL, but a group on TeraGrid >>>> used LoadLeveler too. I assume it's a problem in >>>> $GLOBUS_LOCATION/etc/gram-service-Loadleveler/jndi-config.xml >>>> Please send the content of that file. >>>> >>>> -Martin >>>> >>>> Asish M Madhu wrote: >>>>> Dear All, >>>>> >>>>> I was trying to integrate GLOBUS 4.0.7 with Loadleveler (version:3) in >>>> AIX >>>>> 5.2 64 bit machine. I have installed GLOBUS 4.0.7 successfully using 64 >>>> bit >>>>> flavour. >>>>> >>>>> For integrating with Loadleveler i used the llgrid.tar file from the >>>> already >>>>> installed Loadleveler. Untared it and run the deploy.sh executable >> which >>>>> will automatically integrate Globus with existing Loadleveler. >>>>> >>>>> The installation of the integration package didnt throw any error . But >>>>> after this integration package is installed I cant start the Globus >>>>> Container. >>>>> >>>>> >>>>> I get the below error in the container.log file: >>>>> >>>>> >>>>> >>>>> vi $GLOBUS_LOCATION/var/container.log >>>>> >>>>> *"/usr/local/GARUDA/GLOBUS-4.0.7/var/container.log" 2 lines, 264 >>>> characters >>>>> Failed to start container: Failed to initialize >>>> 'ManagedJobFactoryService' >>>>> service [Caused by: ; nested exception is: >>>>> javax.naming.NamingException: Bean initialization failed [Root >>>>> exception is java.lang.RuntimeException: >> java.lang.NumberFormatException: >>>>> null]]* >>>>> ~ >>>>> >>>>> >>>>> ---------------------------- >>>>> >>>>> What could be the problem? The integration package creates the below >> file >>>> in >>>>> Globus path. >>>>> >>>>> $GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/loadleveler.pm >>>>> $GLOBUS_LOCATION/etc/gram-service/globus_gram_fs_map_config.xml >>>>> $GLOBUS_LOCATION/etc/gram-service-Loadleveler/jndi-config.xml >>>>> $GLOBUS_LOCATION/etc/grid-services/jobmanager-loadleveler >>>>> $GLOBUS_LOCATION/etc/globus-loadleveler.conf >>>>> $GLOBUS_LOCATION/libexec/globus-scheduler-provider-loadleveler >>>>> >>>>> But when i remove these files the container starts without any problem. >>>> How >>>>> can I integrate Globus with Loadleveler ? Kindly help me. >>>>> Thanks in advance >>>>> >>>>> Regards >>>>> Asish M Madhu >>>>> [email protected] >>>>> >>> >> > >
