Re: [gt-user] start container with error

John Bresnahan Mon, 12 Jan 2009 09:42:48 -0800

mehdi ahangar wrote:

All DearsI installed GT4 on SUSE10.1 from binary package, but


which specific version are you using?

when start container this error apear:

glo...@ahangar:/> $GLOBUS_LOCATION/bin/globus-start-container

2007-10-03T23:08:51.189+03:30 ERROR seg.SchedulerEventGenerator [SEG-fork-Thread,run:230] SEG Terminated with/home/globus/gt4/libexec/globus-scheduler-event-generator: /home/globus/gt4/libexec/globus-scheduler-event-

generator: cannot execute binary file

Unable to connect to database.Cannot get a connection, pool exhausted. Caused byorg.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool exhausted

        at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:183)
        at java.sql.DriverManager.getConnection(DriverManager.java:525)
        at java.sql.DriverManager.getConnection(DriverManager.java:193)
        at 
org.globus.transfer.reliable.service.database.RFTDatabaseSetup.getDBConnection(RFTDatabaseSetup.java:261)

at org.globus.transfer.reliable.service.database.ReliableFileTransferDbAdapter.setSchemaVersion(ReliableFileTransferDbAdapter.java:441)

        at 
org.globus.transfer.reliable.service.database.ReliableFileTransferDbAdapter.setup
(ReliableFileTransferDbAdapter.java:155)
        at 
org.globus.transfer.reliable.service.ReliableFileTransferImpl.<init>(ReliableFileTransferImpl.java:78)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:494)

        at java.lang.Class.newInstance0(Class.java:350)
        at java.lang.Class.newInstance(Class.java:303)
        at 
org.globus.axis.providers.RPCProvider.getNewServiceInstance(RPCProvider.java:120)
        at 
org.globus.axis.description.ServiceDescUtil.initializeProviders(ServiceDescUtil.java:214)
        at 
org.globus.axis.description.ServiceDescUtil.initializeService(ServiceDescUtil.java:163)
        at 
org.globus.wsrf.container.ServiceManager$InitPrivilegedAction.initialize(ServiceManager.java:384)
        at 
org.globus.wsrf.container.ServiceManager$InitPrivilegedAction.run(ServiceManager.java:396)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:396)
        at org.globus.gsi.jaas.GlobusSubject.runAs(GlobusSubject.java:60)
        at org.globus.gsi.jaas.JaasSubject.doAs(JaasSubject.java:100)
        at 
org.globus.wsrf.container.ServiceManager.initializeService(ServiceManager.java:271)
        at 
org.globus.wsrf.container.ServiceManager.start(ServiceManager.java:177)
        at 
org.globus.wsrf.container.ServiceDispatcher.startServices(ServiceDispatcher.java:799)
        at 
org.globus.wsrf.container.ServiceDispatcher.init(ServiceDispatcher.java:435)
        at 
org.globus.wsrf.container.ServiceContainer.start(ServiceContainer.java:252)
        at 
org.globus.wsrf.container.ServiceContainer.<init>(ServiceContainer.java:212)
        at 
org.globus.wsrf.container.GSIServiceContainer.<init>(GSIServiceContainer.java:42)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at 
org.globus.wsrf.container.ServiceContainer.createContainer(ServiceContainer.java:168)
        at 
org.globus.wsrf.container.ServiceContainer.startSecurityContainer(ServiceContainer.java:606)
        at 
org.globus.wsrf.container.ServiceContainer.main(ServiceContainer.java:539)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.globus.bootstrap.BootstrapBase.launch(BootstrapBase.java:114)
        at 
org.globus.bootstrap.ContainerBootstrap.main(ContainerBootstrap.java:40)

Caused by:java.util.NoSuchElementException: Could not create a validated object, cause: A read-only user or a user in a read-

only database is not permitted to disable read-only mode on a connection.

atorg.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:806)

        at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:175)
        ... 41 more

2007-10-03T23:08:56.551+03:30 ERROR service.ReliableFileTransferImpl [main,oldLog:179] Unable to setup databasedriver with pooling.Unable to connect to database.Cannot get a connection, pool exhausted [Caused by: Cannot get aconnection, pool exhausted]2007-10-03T23:08:57.244+03:30 WARN service.ReliableFileTransferHome [main,oldLog:190]All RFT requests will fail and all GRAM jobs that require file staging will fail.Unable to connect todatabase.Cannot get a connection, pool exhausted [Caused by: Cannot get a connection, pool exhausted]

Starting SOAP server at https://127.0.0.2:8443/wsrf/services/
With the following services:

[1]: https://127.0.0.2:8443/wsrf/services/AdminService
[2]: https://127.0.0.2:8443/wsrf/services/AttachmentTestService
[3]: https://127.0.0.2:8443/wsrf/services/AuthzCalloutTestService
[4]: https://127.0.0.2:8443/wsrf/services/CASService
[5]: https://127.0.0.2:8443/wsrf/services/ContainerRegistryEntryService
[6]: https://127.0.0.2:8443/wsrf/services/ContainerRegistryService
[7]: https://127.0.0.2:8443/wsrf/services/CounterService
[8]: https://127.0.0.2:8443/wsrf/services/DefaultIndexService
[9]: https://127.0.0.2:8443/wsrf/services/DefaultIndexServiceEntry
[10]: https://127.0.0.2:8443/wsrf/services/DelegationFactoryService
[11]: https://127.0.0.2:8443/wsrf/services/DelegationService
[12]: https://127.0.0.2:8443/wsrf/services/DelegationTestService
[13]: https://127.0.0.2:8443/wsrf/services/DeployService
[14]: https://127.0.0.2:8443/wsrf/services/GKrellmService
[15]: https://127.0.0.2:8443/wsrf/services/InMemoryServiceGroup
[16]: https://127.0.0.2:8443/wsrf/services/InMemoryServiceGroupEntry
[17]: https://127.0.0.2:8443/wsrf/services/InMemoryServiceGroupFactory
[18]: https://127.0.0.2:8443/wsrf/services/IndexFactoryService
[19]: https://127.0.0.2:8443/wsrf/services/IndexService
[20]: https://127.0.0.2:8443/wsrf/services/IndexServiceEntry
[21]: https://127.0.0.2:8443/wsrf/services/JWSCoreVersion
[22]: https://127.0.0.2:8443/wsrf/services/LoggingService
[23]: https://127.0.0.2:8443/wsrf/services/ManagedExecutableJobService
[24]: https://127.0.0.2:8443/wsrf/services/ManagedJobFactoryService
[25]: https://127.0.0.2:8443/wsrf/services/ManagedMultiJobService
[26]: https://127.0.0.2:8443/wsrf/services/ManagementService
[27]: https://127.0.0.2:8443/wsrf/services/NotificationConsumerFactoryService
[28]: https://127.0.0.2:8443/wsrf/services/NotificationConsumerService
[29]: https://127.0.0.2:8443/wsrf/services/NotificationTestService
[30]: https://127.0.0.2:8443/wsrf/services/PersistenceTestSubscriptionManager
[31]: https://127.0.0.2:8443/wsrf/services/QueryTestService
[32]: https://127.0.0.2:8443/wsrf/services/RPParamTestService
[33]: https://127.0.0.2:8443/wsrf/services/ReliableFileTransferFactoryService
[34]: https://127.0.0.2:8443/wsrf/services/ReliableFileTransferService
[35]: https://127.0.0.2:8443/wsrf/services/RendezvousFactoryService
[36]: https://127.0.0.2:8443/wsrf/services/ReplicationService
[37]: https://127.0.0.2:8443/wsrf/services/SAMLAuthzTestService
[38]: https://127.0.0.2:8443/wsrf/services/SampleAuthzService
[39]: https://127.0.0.2:8443/wsrf/services/SecureCounterService
[40]: https://127.0.0.2:8443/wsrf/services/SecurityTestService
[41]: https://127.0.0.2:8443/wsrf/services/ShutdownService
[42]: https://127.0.0.2:8443/wsrf/services/SubscriptionManagerService
[43]: https://127.0.0.2:8443/wsrf/services/TestAuthzService
[44]: https://127.0.0.2:8443/wsrf/services/TestCASService
[45]: https://127.0.0.2:8443/wsrf/services/TestEnumService
[46]: https://127.0.0.2:8443/wsrf/services/TestLoginModuleService
[47]: https://127.0.0.2:8443/wsrf/services/TestPDPService
[48]: https://127.0.0.2:8443/wsrf/services/TestParamAuthzService
[49]: https://127.0.0.2:8443/wsrf/services/TestRPCService
[50]: https://127.0.0.2:8443/wsrf/services/TestService
[51]: https://127.0.0.2:8443/wsrf/services/TestServiceRequest
[52]: https://127.0.0.2:8443/wsrf/services/TestServiceWrongWSDL
[53]: https://127.0.0.2:8443/wsrf/services/TriggerFactoryService
[54]: https://127.0.0.2:8443/wsrf/services/TriggerRegistrationService
[55]: https://127.0.0.2:8443/wsrf/services/TriggerRegistrationServiceEntry
[56]: https://127.0.0.2:8443/wsrf/services/TriggerService
[57]: https://127.0.0.2:8443/wsrf/services/Version
[58]: https://127.0.0.2:8443/wsrf/services/WidgetNotificationService
[59]: https://127.0.0.2:8443/wsrf/services/WidgetService
[60]: https://127.0.0.2:8443/wsrf/services/gsi/AuthenticationService
[61]: https://127.0.0.2:8443/wsrf/services/mds/test/execsource/IndexService
[62]: https://127.0.0.2:8443/wsrf/services/mds/test/execsource/IndexServiceEntry
[63]: https://127.0.0.2:8443/wsrf/services/mds/test/httpsource/IndexService
[64]: https://127.0.0.2:8443/wsrf/services/mds/test/httpsource/IndexServiceEntry
[65]: https://127.0.0.2:8443/wsrf/services/mds/test/subsource/IndexService
[66]: https://127.0.0.2:8443/wsrf/services/mds/test/subsource/IndexServiceEntry
[67]: https://127.0.0.2:8443/wsrf/services/mds/test/usefulrp/IndexService
[68]: https://127.0.0.2:8443/wsrf/services/mds/test/usefulrp/IndexService
Entry

2007-10-03T23:09:01.239+03:30 ERROR seg.SchedulerEventGenerator [SEG-fork-Thread,run:230] SEG Terminated with/home/globus/gt4/libexec/globus-scheduler-event-generator: /home/globus/gt4/libexec/globus-scheduler-event-generator: cannot execute binary file-----------------------------------------------------------------------------------------------------------------------------

also globus-scheduler-event-generator is in expected location.
i read a lot of mail in mailing list but dont find any

mail same this error.what is your sugesstion?please help mewith the best regards, Ahangar

Re: [gt-user] start container with error

Reply via email to