-----Original Message-----
From: Charles Bacon [mailto:[EMAIL PROTECTED]
Sent: Mon 9/17/2007 5:33 PM
To: Lengyel, Florian
Cc: [email protected]
Subject: Re: [gt-user] logicalHost -- when does globus decide to use hostname?
On Sep 17, 2007, at 4:23 PM, Lengyel, Florian wrote:
> What's the connectionString in $GL/etc/globus_wsrf_rft/jndi-
> config.xml ? You can make sure using the psql command that the user/
> password in there are working to insert rows to the database listed
> there.
>
> <name>
> connectionString
> </name>
> <value>
> jdbc:postgresql://m248.gc.cuny.edu/rftDatabase
> </value>
> </parameter>
>
>
> The user is globus and the password is the one that I set with
> createuser -P globus
From the error message, it sounds like you might need to grant
additional privileges to that user. I would check the postgresql
logfile to see what error message is indicated by the server. I'm
surprised, as I'd think the owner/creator of the table should be
allowed to insert new rows into it automatically.
Charles
I should mention that I'm using postgres 8.1
A tail of /usr/local/pgsql/data/serverlog shows
ERROR: permission denied for relation factory
ERROR: permission denied for relation transfer
ERROR: permission denied for relation request
ERROR: permission denied for relation factory
[EMAIL PROTECTED] /usr/local/pgsql/data $
Creating the role didn't grant any privileges
postgres=# \c rftDatabase
You are now connected to database "rftDatabase".
rftDatabase=# \z
Access privileges for database "rftDatabase"
Schema | Name | Type | Access privileges
--------+------------+-------+-------------------
public | factory | table |
public | request | table |
public | requestid | table |
public | restart | table |
public | transfer | table |
public | transferid | table |
(6 rows)
rftDatabase=#
And the schema creation sql didn't add them either.
So
rftDatabase=# grant all privileges ON factory to globus;
GRANT
rftDatabase=# \z
Access privileges for database "rftDatabase"
Schema | Name | Type | Access privileges
--------+------------+-------+-----------------------------------------------------
public | factory | table |
{postgres=arwdRxt/postgres,globus=arwdRxt/postgres}
public | request | table |
public | requestid | table |
public | restart | table |
public | transfer | table |
public | transferid | table |
(6 rows)
rftDatabase=# grant all privileges ON request to globus;
GRANT
rftDatabase=# grant all privileges ON requestid to globus;
GRANT
rftDatabase=# grant all privileges ON restart to globus;
GRANT
rftDatabase=# grant all privileges ON transfer to globus;
GRANT
rftDatabase=# grant all privileges ON transferid to globus;
GRANT
rftDatabase=# \z
Access privileges for database "rftDatabase"
Schema | Name | Type | Access privileges
--------+------------+-------+-----------------------------------------------------
public | factory | table |
{postgres=arwdRxt/postgres,globus=arwdRxt/postgres}
public | request | table |
{postgres=arwdRxt/postgres,globus=arwdRxt/postgres}
public | requestid | table |
{postgres=arwdRxt/postgres,globus=arwdRxt/postgres}
public | restart | table |
{postgres=arwdRxt/postgres,globus=arwdRxt/postgres}
public | transfer | table |
{postgres=arwdRxt/postgres,globus=arwdRxt/postgres}
public | transferid | table |
{postgres=arwdRxt/postgres,globus=arwdRxt/postgres}
(6 rows)
rftDatabase=#
To see if I'm still getting exceptions with debugging enabled, I restarted
globus--I'm not
getting the errors I was seeing (the previous RFT errors were removed with the
creation
of the rftDatabase and modification of pg_bha.conf, but enabling RFT debugging
in
$GLOBUS_LOCATION/container-log4j.properties revealed more errors; these are now
gone:
m248 globus_wsrf_rft # /etc/init.d/globus restart
Stopping Globus container. PID: 12168
Container stopped
Starting Globus container. PID: 14243
m248 globus_wsrf_rft # tail -f /home/m248/globus/gt4/var/container.log
2007-09-17 17:53:43,132 DEBUG factory.ReliableFileTransferFactoryService
[main,<init>:129] Registration to MDS enabled
2007-09-17 17:53:44,951 DEBUG service.ReliableFileTransferImpl
[main,<init>:340] maximum active allowed:100
2007-09-17 17:53:44,991 DEBUG database.RFTDatabaseSetup
[main,setupDBConnection:162] Setting up db : maximum active connection is 20
2007-09-17 17:53:44,993 DEBUG database.RFTDatabaseSetup
[main,setupDBConnection:164] Setting up db : maximum idle connection is 10
2007-09-17 17:53:44,995 DEBUG database.RFTDatabaseSetup
[main,setupDBConnection:166]
dbOptionsjdbc:postgresql://m248.gc.cuny.edu/rftDatabase globus
globusRFT16753786 org.postgresql.Driver 20 1 -1 10
2007-09-17 17:53:47,486 DEBUG service.ReliableFileTransferHome
[main,initialize:61] Loading the RFT home's list of resource keys
2007-09-17 17:53:47,511 DEBUG service.ReliableFileTransferHome
[main,initialize:68] Number of RFT resources to be recovered:0
Starting SOAP server at: https://10.10.32.248:8443/wsrf/services/
With the following services:
[1]: https://10.10.32.248:8443/wsrf/services/AdminService
[2]: https://10.10.32.248:8443/wsrf/services/AuthzCalloutTestService
[3]: https://10.10.32.248:8443/wsrf/services/CASService
[4]: https://10.10.32.248:8443/wsrf/services/ContainerRegistryEntryService
[5]: https://10.10.32.248:8443/wsrf/services/ContainerRegistryService
[6]: https://10.10.32.248:8443/wsrf/services/CounterService
[7]: https://10.10.32.248:8443/wsrf/services/DefaultIndexService
[8]: https://10.10.32.248:8443/wsrf/services/DefaultIndexServiceEntry
[9]: https://10.10.32.248:8443/wsrf/services/DefaultTriggerService
[10]: https://10.10.32.248:8443/wsrf/services/DefaultTriggerServiceEntry
[11]: https://10.10.32.248:8443/wsrf/services/DelegationFactoryService
[12]: https://10.10.32.248:8443/wsrf/services/DelegationService
[13]: https://10.10.32.248:8443/wsrf/services/DelegationTestService
[14]: https://10.10.32.248:8443/wsrf/services/InMemoryServiceGroup
[15]: https://10.10.32.248:8443/wsrf/services/InMemoryServiceGroupEntry
[16]: https://10.10.32.248:8443/wsrf/services/InMemoryServiceGroupFactory
[17]: https://10.10.32.248:8443/wsrf/services/IndexFactoryService
[18]: https://10.10.32.248:8443/wsrf/services/IndexService
[19]: https://10.10.32.248:8443/wsrf/services/IndexServiceEntry
[20]: https://10.10.32.248:8443/wsrf/services/ManagedExecutableJobService
[21]: https://10.10.32.248:8443/wsrf/services/ManagedJobFactoryService
[22]: https://10.10.32.248:8443/wsrf/services/ManagedMultiJobService
[23]: https://10.10.32.248:8443/wsrf/services/ManagementService
[24]: https://10.10.32.248:8443/wsrf/services/NotificationConsumerFactoryService
[25]: https://10.10.32.248:8443/wsrf/services/NotificationConsumerService
[26]: https://10.10.32.248:8443/wsrf/services/NotificationTestService
[27]: https://10.10.32.248:8443/wsrf/services/PersistenceTestSubscriptionManager
[28]: https://10.10.32.248:8443/wsrf/services/ReliableFileTransferFactoryService
[29]: https://10.10.32.248:8443/wsrf/services/ReliableFileTransferService
[30]: https://10.10.32.248:8443/wsrf/services/RendezvousFactoryService
[31]: https://10.10.32.248:8443/wsrf/services/ReplicationService
[32]: https://10.10.32.248:8443/wsrf/services/SampleAuthzService
[33]: https://10.10.32.248:8443/wsrf/services/SecureCounterService
[34]: https://10.10.32.248:8443/wsrf/services/SecurityTestService
[35]: https://10.10.32.248:8443/wsrf/services/ShutdownService
[36]: https://10.10.32.248:8443/wsrf/services/SubscriptionManagerService
[37]: https://10.10.32.248:8443/wsrf/services/TestAuthzService
[38]: https://10.10.32.248:8443/wsrf/services/TestRPCService
[39]: https://10.10.32.248:8443/wsrf/services/TestService
[40]: https://10.10.32.248:8443/wsrf/services/TestServiceRequest
[41]: https://10.10.32.248:8443/wsrf/services/TestServiceWrongWSDL
[42]: https://10.10.32.248:8443/wsrf/services/TriggerFactoryService
[43]: https://10.10.32.248:8443/wsrf/services/TriggerService
[44]: https://10.10.32.248:8443/wsrf/services/TriggerServiceEntry
[45]: https://10.10.32.248:8443/wsrf/services/Version
[46]: https://10.10.32.248:8443/wsrf/services/WidgetNotificationService
[47]: https://10.10.32.248:8443/wsrf/services/WidgetService
[48]: https://10.10.32.248:8443/wsrf/services/gsi/AuthenticationService
[49]: https://10.10.32.248:8443/wsrf/services/mds/test/execsource/IndexService
[50]:
https://10.10.32.248:8443/wsrf/services/mds/test/execsource/IndexServiceEntry
[51]: https://10.10.32.248:8443/wsrf/services/mds/test/subsource/IndexService
[52]:
https://10.10.32.248:8443/wsrf/services/mds/test/subsource/IndexServiceEntry
2007-09-17 17:54:13,282 INFO impl.DefaultIndexService
[ServiceThread-11,processConfigFile:107] Reading default registration
configuration from file:
/home/m248/globus/gt4/etc/globus_wsrf_mds_index/hierarchy.xml
So far so good.
[EMAIL PROTECTED] ~ $ globusrun-ws -s -submit -c /bin/date
Delegating user credentials...Done.
Submitting job...Done.
Job ID: uuid:93d6b2fe-6569-11dc-9cfa-0002b323da69
Termination time: 09/18/2007 22:01 GMT
Current job state: Active
Current job state: CleanUp-Hold
Mon Sep 17 18:01:47 EDT 2007
Current job state: CleanUp
Current job state: Done
Destroying job...Done.
Cleaning up any delegated credentials...Done.
[EMAIL PROTECTED] ~ $
And so granting permissions to the tables of the rftDatabase for the globus
user seems
to have worked. It may have worked differently for postgres 7.3 (though I don't
recall
not having to set permissions on any database I've installed, unless those were
granted
automatically in some sql script...).
Many thanks for your assistance.
FL
