Sergei,
Make sure your postgresql database is up and running.
If you didn't change the default port for postgresql (5432),
your connnection string should be
jdbc:postgresql://localhost/rftDatabase
If the port is different, specify
jdbc:postgresql://localhost:<port>/rftDatabase
The location of the postgresql installation on disk is not
important to connect to the server. I suggest you make sure that
you can connect to the database on localhost using postgresql
commandline tools first.
2811 is the gridftp port, you seem to mix gridftp servers with
database servers. The use of the database in RFT is only
to persist data, but has nothing to do with gridftp servers.
-Martin
Sergei Smolov wrote:
> Thank you, Martin!
> But the thing is that I've created the rftDatabase in my localhost. What
> should be the connectionString in this case?
> I've tried to use such variant:
>
> <parameter>
> <name>
> connectionString
> </name>
> <value>
> jdbc:postgresql://<hostname>:2811/rftDatabase
> </value>
> </parameter>
>
> where I've written <hostname> as the part of Simple CA certificate (i.e.
> when I configured the SImpleCA, I've written <hostname> string in
> certificate) and port 2811 - because I've started globus-gridftp from this
> port:
>
> $GLOBUS_LOCATION/sbin/globus-gridftp-server -p 2811
>
> My rftDatabase is installed in $GLOBUS_LOCATION/var/rftDatabase. Maybe, my
> port and hostname values are incorrect - but what should be correct for the
> localhost?
> Great thanks in advance
>
>
> 2009/4/11, Martin Feller <[email protected]>:
>> The connectionString in the DB section is wrong in your jndi-config.xml
>> Must not be $GLOBUS_LOCATION/var/rftDatabase, but should be
>> jdbc:postgresql://<host>[:<port>]/rftDatabase
>> Also check
>> http://www.globus.org/toolkit/docs/latest-stable/data/rft/admin/#rft-postgresql
>>
>>
>> -Martin
>>
>>
>> Sergei Smolov wrote:
>>> Hello, List!
>>> I've installed Globus Toolkit 4.2.1 and PostgreSQL 7.3.2 for RFT testing.
>>> Then I execute the following commands:
>>>
>>> ./postmaster -D <data directory address> -o -i
>>>
>>> $GLOBUS_LOCATION/sbin/globus-gridftp-server -p 2811
>>>
>>> $GLOBUS_LOCATION/bin/globus-start-container
>>>
>>> When I try to start container, I get the following error:
>>>
>>> Unable to connect to database.No suitable driver found for
>>> /home/ssedai/GlobusToolkit/var/rftDatabase. Caused by
>> java.sql.SQLException:
>>> No suitable driver found for /home/ssedai/GlobusToolkit/var/rftDatabase
>>> at java.sql.DriverManager.getConnection(DriverManager.java:602)
>>> at java.sql.DriverManager.getConnection(DriverManager.java:185)
>>> at
>>>
>> org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:48)
>>> at
>>>
>> org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290)
>>> at
>>>
>> org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:771)
>>> at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:175)
>>> at java.sql.DriverManager.getConnection(DriverManager.java:582)
>>> at java.sql.DriverManager.getConnection(DriverManager.java:207)
>>> 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:513)
>>> at java.lang.Class.newInstance0(Class.java:355)
>>> at java.lang.Class.newInstance(Class.java:308)
>>> 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:513)
>>> 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:597)
>>> at org.globus.bootstrap.BootstrapBase.launch(BootstrapBase.java:114)
>>> at
>> org.globus.bootstrap.ContainerBootstrap.main(ContainerBootstrap.java:40)
>>> 2009-04-09T16:01:14.200+04:00 ERROR service.ReliableFileTransferImpl
>>> [main,oldLog:179] Unable to setup database driver with pooling.Unable to
>>> connect to database.No suitable driver found for
>>> /home/ssedai/GlobusToolkit/var/rftDatabase [Caused by: No suitable driver
>>> found for /home/ssedai/GlobusToolkit/var/rftDatabase]
>>> 2009-04-09T16:01:15.409+04:00 WARN service.ReliableFileTransferHome
>>> [main,oldLog:190] All RFT requests will fail and all GRAM jobs that
>> require
>>> file staging will fail.Unable to connect to database.No suitable driver
>>> found for /home/ssedai/GlobusToolkit/var/rftDatabase [Caused by: No
>> suitable
>>> driver found for /home/ssedai/GlobusToolkit/var/rftDatabase]
>>> 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/IndexServiceEntry
>>> 2009-04-09T16:01:38.670+04:00 INFO impl.DefaultIndexService
>>> [ServiceThread-56,performDefaultRegistrations:261]
>>> guid=2e5fffb0-24fe-11de-a137-e0183b4b1b86
>>> event=org.globus.mds.index.performDefaultRegistrations.end status=0
>>>
>>> Perhaps this error is connected with incorrect configuration file
>>> $GLOBUS_LOCATION/etc/globus_wsrf_rft/jndi-config.xml
>>> I've such strings in this file (others are default strings, but these
>> I've
>>> changed):
>>>
>>> <parameter>
>>> <name>
>>> driverName
>>> </name>
>>> <value>
>>> org.postgresql.Driver
>>> </value>
>>> </parameter>
>>> <parameter>
>>> <name>
>>> connectionString
>>> </name>
>>> <value>
>>> $GLOBUS_LOCATION/var/rftDatabase
>>> </value>
>>>
>>> What should be the correct jndi-config.xml file?
>>> Thanks in advance.
>>
>
>
