In your find item response from this command:
"""
$GLOBUS_LOCATION/bin/globus-replication-finditems -e g16_new_replicator.epr
-N raj_file <ns1:FindItemsResponse xmlns:ns1="
http://www.globus.org/namespaces/2005/05/replica/replicator";> <ns1:items
xsi:type="ns1:ReplicationItemType" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance";>
<ns1:uri xsi:type="xsd:string" xmlns:xsd="http://www.w3.org/2001/XMLSchema
">raj_file</ns1:uri>
<ns1:priority xsi:type="xsd:int" xmlns:xsd="
http://www.w3.org/2001/XMLSchema";>1000</ns1:priority>
<ns1:status
xsi:type="ns1:ReplicationItemStatusEnumerationType">Failed</ns1:status>
<ns1:errorMessage xsi:type="xsd:string" xmlns:xsd="
http://www.w3.org/2001/XMLSchema";>No sources for item:
raj_file</ns1:errorMessage>
<ns1:destinations xsi:type="ns1:DestinationType">
<ns1:uri xsi:type="xsd:string" xmlns:xsd="
http://www.w3.org/2001/XMLSchema
">gsiftp://g16.grid/tmp/new_raj.txt</ns1:uri>
<ns1:status
xsi:type="ns1:DestinationStatusEnumerationType">Pending</ns1:status>
</ns1:destinations>
</ns1:items>
</ns1:FindItemsResponse>
"""
The errorMessage (above) says "No sources for item: raj_file". You might first
check that the file is in the RLS's index. Use:
globus-rls-cli query rli lfn raj_file rls://g16.grid:39281
Also you should check the container's log file (or stdout depending on how you
are using it). To get DRS messages turn up its log level.
See this instruction:
http://www.globus.org/toolkit/docs/4.0/techpreview/datarep/admin-index.html#s-datarep-admin-troubleshooting
-----Original Message-----
From: Rajendar K [mailto:[EMAIL PROTECTED]
Sent: Thu 3/27/2008 10:33 PM
To: Robert Schuler
Subject: Re: [gt-user] Regarding DRS
Hi Robert,
I have done the updates as you said , the below is the command
which i done to
confirm the existence
[EMAIL PROTECTED] ~]# globus-rls-admin -a rls://g16.grid
rls://g16.grid
globus_rls_client: RLI already exists: rls://g16.grid:39281
After that , i done the same procedure, But the same errror comes, stating
that the status as TERMINATED
The lfn which iam trying is that of the "raj_file" which exists when i query
globus-rls-cli query wildcard lrc lfn "*" rls://g16.grid:39281
raj_file: gsiftp://g16.grid/tmp/raj_test.txt
file raj_test.txt exists.......
cat /tmp/raj_test.txt
Hai This is Raj
The request file which i have created is the raj_request.req
cat /tmp/raj_request.req
raj_file gsiftp://g16.grid/tmp/new_raj.txt
According to the actual procedure, a new file name "new_raj.txt" should be
created. (Am i right upto this?)
The following is the list of steps which i have done and the results........
/usr/local/globus-4.0.5/bin/globus-replication-create -d -s
https://172.16.10.17:8443/wsrf/services/ReplicationService -C
g16_new_credential.epr -V g16_new_replicator.epr file:///tmp/raj_request.req
Argument:
Option: debug
Value: null
Argument:
Option: saveEpr
Value: g16_new_replicator.epr
Argument:
Option: service
Value: https://172.16.10.17:8443/wsrf/services/ReplicationService
Argument:
Option: delegatedCredential
Value: g16_new_credential.epr
Service endpoint: Address:
https://172.16.10.17:8443/wsrf/services/ReplicationService
Creating Replicator...
Replicator created.
/usr/local/globus-4.0.5/bin/globus-replication-start -e
g16_new_replicator.epr --debug
Start operation was successful
/usr/local/globus-4.0.5/bin/wsrf-get-property -e g16_new_replicator.epr "{
http://www.globus.org/namespaces/2005/05/replica/replicator}status";
<ns1:status xmlns:ns1="
http://www.globus.org/namespaces/2005/05/replica/replicator
">Terminated</ns1:status>
/usr/local/globus-4.0.5/bin/wsrf-get-property -e g16_new_replica tor.epr "{
http://www.globus.org/namespaces/2005/05/replica/replicator}count";
<ns1:count xmlns:ns1="
http://www.globus.org/namespaces/2005/05/replica/replicator";>
<ns1:total>1</ns1:total>
<ns1:finished>0</ns1:finished>
<ns1:failed>1</ns1:failed>
<ns1:terminated>0</ns1:terminated>
</ns1:count>
$GLOBUS_LOCATION/bin/globus-replication-finditems -e g16_new_replicator.epr
-N raj_file <ns1:FindItemsResponse xmlns:ns1="
http://www.globus.org/namespaces/2005/05/replica/replicator";> <ns1:items
xsi:type="ns1:ReplicationItemType" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance";>
<ns1:uri xsi:type="xsd:string" xmlns:xsd="http://www.w3.org/2001/XMLSchema
">raj_file</ns1:uri>
<ns1:priority xsi:type="xsd:int" xmlns:xsd="
http://www.w3.org/2001/XMLSchema";>1000</ns1:priority>
<ns1:status
xsi:type="ns1:ReplicationItemStatusEnumerationType">Failed</ns1:status>
<ns1:errorMessage xsi:type="xsd:string" xmlns:xsd="
http://www.w3.org/2001/XMLSchema";>No sources for item:
raj_file</ns1:errorMessage>
<ns1:destinations xsi:type="ns1:DestinationType">
<ns1:uri xsi:type="xsd:string" xmlns:xsd="
http://www.w3.org/2001/XMLSchema
">gsiftp://g16.grid/tmp/new_raj.txt</ns1:uri>
<ns1:status
xsi:type="ns1:DestinationStatusEnumerationType">Pending</ns1:status>
</ns1:destinations>
</ns1:items>
</ns1:FindItemsResponse>
On 3/27/08, Robert Schuler <[EMAIL PROTECTED]> wrote:
>
> Hi, Rajendar,
>
>
>
> The user's guide could be better - I'll make some improvement to clarify
> this.
>
>
>
> What's probably missing is that your file "/tmp/whatever" needs to be
> registered in the RLS server:
>
>
>
> $G_L/bin/globus-rls-cli create whatever
> gsiftp://your-gftp-server/tmp/whatever rls://your-rls-server
>
>
>
> Also, your RLS catalog (called a "LRC") will need to send "updates" of the
> catalog's index to an RLS index service (called an "RLI"). To have an RLS
> sends updates to itself you do this:
>
>
>
> $G_L/bin/globus-rls-admin -a rls://localhost rls://localhost
>
>
>
> (replacing localhost with something else if appropriate)
>
>
>
> Then back to DRS. Now, you can have DRS lookup 'whatever' in the RLS and
> replicate it to 'gsiftp://newlocation'.
>
>
>
> I suspect that's the missing step. This needs fixing in the DRS docs.
>
>
>
> rob
>
>
> ------------------------------
>
> *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Rajendar K
> *Sent:* Thursday, March 27, 2008 7:13 AM
> *To:* [email protected]
> *Subject:* [gt-user] Regarding DRS
>
>
>
> Hi all,
> I have installed RLS server and i have the same problem with related
> to DRS as posted by the issues
> named
> "*[gt-user] simple DRS attempt fails"-- as posted by *Adam
> Bazinet *on *Mon, 11 Feb 2008
>
> Any solutions to overcome this problem and to realise the DRS ?
> *
> -------------------------------------------------------------------------------------------------------
> I'm trying to get a simple DRS example working. Here's what I've done:
>
> [EMAIL PROTECTED]:~> globus-rls-cli query lrc lfn whatever rlsn://lysine
> whatever: gsiftp://lysine:2811/tmp/whatever
>
> the file exists:
>
> [EMAIL PROTECTED]:~> cat /tmp/whatever
> something!
>
> and i've followed the instructions, pretty much to the letter, here: **
> http://www.globus.org/toolkit/docs/4.0/techpreview/datarep/user-index.html
> *<http://www.globus.org/toolkit/docs/4.0/techpreview/datarep/user-index.html>
> *
>
> here's my request file:
>
> [EMAIL PROTECTED]:~> cat testrun.req
> whatever gsiftp://lysine:2811/tmp/whatever2
>
> actually starting it seems to go OK...
>
> [EMAIL PROTECTED]:~> globus-replication-create --debug --start -s **
> https://lysine:8443/wsrf/services/ReplicationService*<https://lysine:8443/wsrf/services/ReplicationService>
> * -C mycredential.epr -V
> myreplicator.eprfile:///fs/mikehomes/gt4admin/testrun.req
> Argument:
> Option: saveEpr
> Value: myreplicator.epr
> Argument:
> Option: start
> Value: null
> Argument:
> Option: delegatedCredential
> Value: mycredential.epr
> Argument:
> Option: service
> Value:
> **https://lysine:8443/wsrf/services/ReplicationService*<https://lysine:8443/wsrf/services/ReplicationService>
> *
> Argument:
> Option: debug
> Value: null
> Service endpoint: Address: **
> https://lysine:8443/wsrf/services/ReplicationService*<https://lysine:8443/wsrf/services/ReplicationService>
> *
>
> Creating Replicator...
> Replicator created.
> Starting Replicator...
> Replicator started.
>
> BUT... the file "/tmp/whatever2" is not created. And, it seems the thing
> was terminated:
>
> [EMAIL PROTECTED]:~> wsrf-get-property -e myreplicator.epr "{**
> http://www.globus.org/namespaces/2005/05/replica/replicator}status*<http://www.globus.org/namespaces/2005/05/replica/replicator%7Dstatus>
> *" <ns1:status xmlns:ns1="**
> http://www.globus.org/namespaces/2005/05/replica/replicator*<http://www.globus.org/namespaces/2005/05/replica/replicator>
> *">Terminated</ns1:status>
>
> Any idea what's going wrong here?
>
> Thanks,
> Adam
>
> -------------------------------------------------------------------------------------------------------------------------------------
> *-----
> with regards,
> Raj,
> Research Associate,MIT.
>
--
Raj,
Research Associate,MIT.
