Print

Print


Hi Wei,


Yes, sorry, that is what I wanted to say: the file for some reason is not written on the destination.


Thanks for spotting the lines in the output; this is indeed the output from the client side. I am not sure how to extract the output from the xrdcp-tpc.sh


I have tried sth like


ofs.tpc echo scan all pgm /usr/bin/xrdcp-tpc.sh


but I cant see anything. The xrdcp command on the client actually hangs up in this case...


Reminder: the xrdcp-tpc.sh contains only these two lines


export XrdSecPROTOCOL=host
echo $1 $2 >> /tmp/tpc.log$(date +%H%M%S)


and the result of the echo is


xroot://p06636710b64343.cern.ch:1095//04/36435/05422528-a162-11e8-b5f9-a310691b2def?tpc.key=0913
fa9a0e3f24075ca4bcbf&[log in to unmask] alice:/04/36435/0
5422528-a162-11e8-b5f9-a310691b2def


George





________________________________
From: Yang, Wei <[log in to unmask]>
Sent: 02 April 2019 20:41:15
To: Patargias, George (STFC,RAL,SC); Hanushevsky, Andrew B.
Cc: xrootd-l; Tim Adye
Subject: Re: XRootD TPC error

Hi George,

I guess you meant "Unfortunately the file is NOT in the destination ..."?

According to the attached output (xrdcp.tpc.out, which you previously attached), line 2179 show the actual transfer started (thought the progress bar always show zero - a problem fixed in xrootd 4.9.0), and line 2330, 2350, 2371 shows that the transfer was successful.

I understand that the xrdcp.tpc.out is the output of the client xrdcp command. Do you have a corresponding xrdcp-tpc.sh log? (and better the xrdcp output inside the xrdcp-tpc.sh)?

regards,
--
Wei Yang  |  [log in to unmask]  |  650-926-3338 (O)


On 4/2/19, 4:35 AM, "George Patargias - UKRI STFC" <[log in to unmask]> wrote:

    Hi Wei ,


    Thanks for this. No, unfortunatelly the file is in the destination although in the xrootd-proxy.log


    190402 12:32:42 1476486 acc_Audit: alicesgm.3563:[log in to unmask] grant unix [log in to unmask] create alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def

    Best,


    George




    ________________________________
    From: Yang, Wei <[log in to unmask]>
    Sent: 01 April 2019 20:55:54
    To: Patargias, George (STFC,RAL,SC); Hanushevsky, Andrew B.
    Cc: xrootd-l; Tim Adye
    Subject: Re: XRootD TPC error

    Hi George,

    It seems to me the TPC was successful.  Can you check the destination if the file is there?

    regards,
    --
    Wei Yang  |  [log in to unmask]  |  650-926-3338(O)

    ?-----Original Message-----
    From: George Patargias - UKRI STFC <[log in to unmask]>
    Date: Monday, March 25, 2019 at 9:55 AM
    To: Wei Yang <[log in to unmask]>, Andrew Hanushevsky <[log in to unmask]>
    Cc: xrootd-l <[log in to unmask]>, Tim Adye <[log in to unmask]>
    Subject: Re: XRootD TPC error

        Hi Wei,

        I am running xrootd 4.8.5-1, on both client and server side. I defined "export XrdSecPROTOCOL=host" in xrdpc-tpc.sh. The script
        contains an echo of $1 and $2 args and nothing else.

        I attach the xrdcp.tpc.out that I got from running on the client the following:

        /usr/bin/xrdcp -d 3 --tpc only "root://eosalice.cern.ch:1094//04/36435/05422528-a162-11e8-b5f9-a310691b2def?authz=`cat eos_env`" "root://ceph-dev-gw3.gridpp.rl.ac.uk/alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def?authz=`cat ral_env`" > xrdcp.tpc.out 2>&1


        Thanks again,


        George

        ________________________________
        From: Yang, Wei <[log in to unmask]>
        Sent: 22 March 2019 22:20:14
        To: Patargias, George (STFC,RAL,SC); Hanushevsky, Andrew B.
        Cc: xrootd-l; Tim Adye
        Subject: Re: XRootD TPC error

        Hi George,

        What version of xrootd are you using in xrootd@ceph? (I hope you are running 4.8.x ... anyway, don't upgrade until we communicate this clear:--).

        In your xrdcp-tpc.sh script, can you define "export XrdSecPROTOCOL=host" before you run xrdcp? this will force the client and the server to only use the "host" protocol.

        It maybe also useful to run the xcdcp-tpc.sh script by hand, as if you are in the TPC environment (and perhaps with -d 3 option to the xrdcp) so that we can get a better picture of what was going on.


        regards
        --
        Wei Yang  |  [log in to unmask]  |  650-926-3338 (O)


        On 3/22/19, 9:37 AM, "[log in to unmask] on behalf of George Patargias - UKRI STFC" <[log in to unmask] on behalf of [log in to unmask]> wrote:

            Hi Wei,


            Thanks again for this suggestion. So, I set up xrootd@ceph to have


            sec protocol host
            sec.protbind ceph-dev-gw3.gridpp.rl.ac.uk only host


            But I still get the same error


            Run: [ERROR] Server responded with an error: [3005] [ERROR] Server responded with an error: [3010] Unable to open - tpc origin mismatch /04/36435/05422528-a162-11e8-b5f9-a310691b2def; operation not permitted


            When I wrap the TPC xrdcp command in a script


            ofs.tpc pgm /usr/bin/xrdcp-tpc.sh


            that contains only the line


            echo $1 $2 >> /tmp/tpc.log$(date +%H%M%S)


            (which shows that the getway hostname is removed)


            There is no error but no file is written either

            [0B/249B][  0%][>                                                 ][0B/s]


            And when I try, in the same script, to concatenate the the getway hostname with the arg $2, I get again the above error.


            I still can't understand what information (cgi..? i.e. gateway hostaname?) is lost,  at what level and why...


            Thanks again,


            George










            ________________________________
            From: Yang, Wei <[log in to unmask]>
            Sent: 07 March 2019 17:34:16
            To: Patargias, George (STFC,RAL,SC); Hanushevsky, Andrew B.
            Cc: xrootd-l; Tim Adye
            Subject: Re: XRootD TPC error

            Hi George,

            Sometimes the backend storage also has its own AA. Your CEPH probably has one. The easiest is to setup xroot@CEPH to allow a particular user to do anything, or a particular host (the proxy host) to do anything.

            The relevant Xrootd security protocols that allows a particular user are "sss" and "unix". The xrootd security protocol to allow a particular host is "host". "sss" is reasonably secure and fast. "unix" and "host" aren't secure. The following URL talk about the xrootd security protocols:

            http://www.xrootd.org/doc/dev49/sec_config.htm#_Toc517294117

            regards,
            --
            Wei Yang  |  [log in to unmask]  |  650-926-3338 (O)


            On 3/7/19, 7:22 AM, "George Patargias - UKRI STFC" <[log in to unmask]> wrote:

                Hi Wei,


                Thanks for this. I am not sure I quite understand. I thought that the proxy is in charge of the authentication since it has the directive


                ofs.authlib /usr/lib64/libXrdAliceTokenAcc.so


                I thought that the storage (i.e xrootd@ceph) does trust the proxy but if not, how can it be set up to do so?


                George

                ________________________________
                From: Yang, Wei <[log in to unmask]>
                Sent: 28 February 2019 13:34:23
                To: Hanushevsky, Andrew B.; Patargias, George (STFC,RAL,SC)
                Cc: xrootd-l; Tim Adye
                Subject: Re: XRootD TPC error

                So we have encounter this kind of issue several times, not just with ALICE but with all proxies that have backend storages that require authentication. I think the way proxy and storage should be setup is to have storage trust the proxy and allow the proxy to do full access. The frontend proxy will be in charge of authentication and authorization.

                --
                Wei Yang  |  [log in to unmask]  |  650-926-3338 (O)


                On 2/28/19, 2:07 PM, "Andrew Hanushevsky" <[log in to unmask]> wrote:

                    Hi George,

                    So, yes, the extra cgi information is stripped out. That happens at the
                    client level since it is shouldn't be needed as the authroization has
                    already been preformed. However, since the target is actually another
                    xrootd server, not the local destination, that auth info is needed. I
                    assume that going via root://ceph-dev-gw3.gridpp.rl.ac.uk/ is the only way
                    you can get it into Ceph?

                    Andy

                    On Thu, 28 Feb 2019, George Patargias - UKRI STFC wrote:

                    > Thanks for this.
                    >
                    >
                    > The result of "echo $1 $2" in the /usr/bin/xrdcp-tpc.sh  is
                    >
                    >
                    > xroot://p06253977e28726.cern.ch:1095//04/36435/05422528-a162-11e8-b5f9-a310691b2def?tpc.key=1e3850e932d533255c77d70c&tpc.
                    > [log in to unmask] alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >
                    >
                    > THen I try to do a s string concatenation in the script along the lines
                    >
                    >
                    > targ="root://ceph-dev-gw3.gridpp.rl.ac.uk/"$2
                    >
                    >
                    > and the result of "echo $1 $targ "
                    >
                    >
                    > xroot://p06253977e28726.cern.ch:1095//04/36435/05422528-a162-11e8-b5f9-a310691b2def?tpc.key=1e3850e932d533255c77d70c&tpc.
                    > [log in to unmask] root://ceph-dev-gw3.gridpp.rl.ac.uk/alice:/04/36435/05422528-a162-
                    > 11e8-b5f9-a310691b2def
                    >
                    >
                    > which looks correct
                    >
                    >
                    > the last line of the script is /usr/bin/xrdcp $1 $targ
                    >
                    >
                    > but still the error is
                    >
                    >
                    > 190228 12:41:48 1173324 ofs_TPC: alicesgm.13093:[log in to unmask] alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def [ERROR] Server responded with an error: [3010] Unable to locate alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def; permission denied
                    >
                    >
                    >
                    >
                    >
                    >
                    >
                    >
                    >
                    >
                    > ________________________________
                    > From: Yang, Wei <[log in to unmask]>
                    > Sent: 28 February 2019 11:18:26
                    > To: Hanushevsky, Andrew B.; Patargias, George (STFC,RAL,SC)
                    > Cc: xrootd-l; Tim Adye
                    > Subject: Re: XRootD TPC error
                    >
                    > that (cgi was chopped off) was my initial guess. It would be nice if /usr/bin/xrdcp-tpc.sh logs out what is $1 and $2
                    >
                    > --
                    > Wei Yang  |  [log in to unmask]  |  650-926-3338 (O)
                    >
                    >
                    > On 2/28/19, 9:54 AM, "Andrew Hanushevsky" <[log in to unmask]> wrote:
                    >
                    >    It looks like this is wrapping a push request (i.e. you are writing the
                    >    file to a URL whch is not the local host). That means the user doing the
                    >    xrdcp must be authorized to do so at the destination. It would help if the
                    >    script printed the actual command that will be executed. It may very well
                    >    be that the cgi is not passed through because the assumption is tat TPC
                    >    will occur post authorization on the local host otherwise it's really not
                    >    TPC.
                    >
                    >    Andy
                    >
                    >
                    >      On Wed, 27 Feb 2019, George Patargias - UKRI STFC wrote:
                    >
                    >    > Hi Wei,
                    >    >
                    >    >
                    >    > Just to reiterate what I am trying to do.
                    >    >
                    >    >
                    >    > This command seems to work ok (standard xrdcp, no tpc)
                    >    >
                    >    >
                    >    > xrdcp "root://eosalice.cern.ch:1094//04/36435/05422528-a162-11e8-b5f9-a310691b2def?authz=`cat eos_env`" "root://ceph-dev-gw3.gridpp.rl.ac.uk:1094/alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def?authz=`cat ral_env`"
                    >    >
                    >    >
                    >    > Then I try to run
                    >    >
                    >    >
                    >    > xrdcp --tpc only "root://eosalice.cern.ch:1094//04/36435/05422528-a162-11e8-b5f9-a310691b2def?authz=`cat eos_env`" "root://ceph-dev-gw3.gridpp.rl.ac.uk:1094/alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def?authz=`cat ral_env`"
                    >    >
                    >    >
                    >    > using the directive:  ofs.tpc pgm /usr/bin/xrdcp-tpc.sh
                    >    >
                    >    >
                    >    > where the script contains
                    >    >
                    >    > /usr/bin/xrdcp $1 root://ceph-dev-gw3.gridpp.rl.ac.uk/$2
                    >    >
                    >    >
                    >    > But,   Run: [ERROR] Server responded with an error: [3005] [ERROR] Server responded with an error: [3010] Unable to locate alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def; permission denied
                    >    >
                    >    >
                    >    > and from the xrootd.log   (may be the ?authz=...) are chopped off...
                    >    >
                    >    >
                    >    > 190227 11:32:28 1024027 XrootdXeq: alicesgm.8331:[log in to unmask] pvt IPv4 login as alicesgm
                    >    > 190227 11:32:28 1024027 acc_Audit: alicesgm.8331:[log in to unmask] grant unix [log in to unmask] stat alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >    > No lfn2pfn mapping for alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >    > 190227 11:32:28 1024027 ofs_stat: alicesgm.8331:[log in to unmask] Unable to locate alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def; no such file or directory
                    >    > 190227 11:32:28 1024027 acc_Audit: alicesgm.8331:[log in to unmask] grant unix [log in to unmask] stat alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >    > No lfn2pfn mapping for alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >    > 190227 11:32:28 1024027 ofs_stat: alicesgm.8331:[log in to unmask] Unable to locate alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def; no such file or directory
                    >    > 190227 11:32:28 1024027 acc_Audit: alicesgm.8331:[log in to unmask] grant unix [log in to unmask] create alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >    > No lfn2pfn mapping for alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >    > No lfn2pfn mapping for alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >    > 190227 11:32:28 1024312 XrootdXeq: xrootd.1024936:21@ceph-dev-gw3 pub IP46 login as xrootd
                    >    > 190227 11:32:28 1024312 acc_Audit: xrootd.1024936:21@ceph-dev-gw3 deny unix [log in to unmask] stat alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >    > 190227 11:32:28 1024312 ofs_stat: xrootd.1024936:21@ceph-dev-gw3 Unable to locate alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def; permission denied
                    >    > 190227 11:32:28 1024312 acc_Audit: xrootd.1024936:21@ceph-dev-gw3 deny unix [log in to unmask] stat alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >    > 190227 11:32:28 1024312 ofs_stat: xrootd.1024936:21@ceph-dev-gw3 Unable to locate alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def; permission denied
                    >    > 190227 11:32:28 1024312 XrootdXeq: xrootd.1024936:21@ceph-dev-gw3 disc 0:00:00
                    >    > 190227 11:32:28 1024933 ofs_Run: /usr/bin/xrdcp-tpc.sh ended with status 54
                    >    > 190227 11:32:28 1024933 ofs_TPC: alicesgm.8331:[log in to unmask] alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def [ERROR] Server responded with an error: [3010] Unable to locate alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def; permission denied
                    >    > No lfn2pfn mapping for alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def
                    >    > 190227 11:32:29 1024027 XrootdXeq: alicesgm.8331:[log in to unmask] disc 0:00:01
                    >    >
                    >    >
                    >    >
                    >    >
                    >    >
                    >    >
                    >    >
                    >    >
                    >    >
                    >    > ________________________________
                    >    > From: Yang, Wei <[log in to unmask]>
                    >    > Sent: 20 February 2019 09:13:33
                    >    > To: Patargias, George (STFC,RAL,SC); xrootd-l
                    >    > Cc: Tim Adye; Johnson, Ian (STFC,RAL,SC)
                    >    > Subject: Re: XRootD TPC error
                    >    >
                    >    > HI George,
                    >    >
                    >    > In your /usr/bin/xrdcp-tpc.sh, can you log to a file what is the $1 and $2? I wonder if ?authz=`cat ...` was chopped off when TPC passes $1 and $2 to  the script. If so, I will need to discuss with Andy to see if there is a solution.
                    >    >
                    >    > regards,
                    >    > --
                    >    > Wei Yang  |  [log in to unmask]  |  650-926-3338(O)
                    >    >
                    >    > ?-----Original Message-----
                    >    > From: George Patargias - UKRI STFC <[log in to unmask]>
                    >    > Date: Wednesday, February 20, 2019 at 1:07 AM
                    >    > To: Wei Yang <[log in to unmask]>, xrootd-l <[log in to unmask]>
                    >    > Cc: Tim Adye <[log in to unmask]>, Ian Johnson - UKRI STFC <[log in to unmask]>
                    >    > Subject: Re: XRootD TPC error
                    >    >
                    >    >    Hi Wei,
                    >    >
                    >    >
                    >    >    The command I use to manualy copy the file from eosalice is the one that the ALICE client uses and I showed it in the previous email.
                    >    >
                    >    >
                    >    >    /usr/bin/xrdcp --tpc only --force --path --posc --nopbar -ODeos.app=transfer-3rd "root://eosalice.cern.ch:1094//04/36435/05422528-a162-11e8-b5f9-a310
                    >    >        691b2def?authz=`cat eos_env`" "root://ceph-dev-gw3.gridpp.rl.ac.uk:1094/alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def?authz=`cat ral_env`"
                    >    >
                    >    >
                    >    >    Thanks,
                    >    >
                    >    >    George
                    >    >
                    >    >    ________________________________
                    >    >    From: Yang, Wei <[log in to unmask]>
                    >    >    Sent: 15 February 2019 17:30:01
                    >    >    To: Patargias, George (STFC,RAL,SC); xrootd-l
                    >    >    Cc: Tim Adye; Johnson, Ian (STFC,RAL,SC)
                    >    >    Subject: Re: XRootD TPC error
                    >    >
                    >    >    Hi George,
                    >    >    I guess I missed the ALICE specific part. If you are to manually copy a file from EOSalice, what is the command to use?
                    >    >    regards,
                    >    >    --
                    >    >    Wei Yang  |  [log in to unmask]  |  650-926-3338 (O)
                    >    >
                    >    >
                    >    >    On 2/15/19, 2:04 AM, "George Patargias - UKRI STFC" <[log in to unmask]> wrote:
                    >    >
                    >    >        Hi Wei,
                    >    >
                    >    >
                    >    >        Thanks for this suggestion. I set in  /etc/xrootd/xrootd-proxy.cfg
                    >    >
                    >    >
                    >    >        ofs.tpc pgm /usr/bin/xrdcp-tpc.sh
                    >    >
                    >    >
                    >    >        where  /usr/bin/xrdcp-tpc.sh contains
                    >    >
                    >    >
                    >    >        #!/bin/bash
                    >    >
                    >    >        /usr/bin/xrdcp $1 root://ceph-dev-gw3.gridpp.rl.ac.uk/$2
                    >    >
                    >    >
                    >    >        I tried to run again the command (as run by ALICE)
                    >    >
                    >    >
                    >    >        /usr/bin/xrdcp --tpc only --force --path --posc --nopbar -ODeos.app=transfer-3rd "root://eosalice.cern.ch:1094//04/36435/05422528-a162-11e8-b5f9-a310
                    >    >        691b2def?authz=`cat eos_env`" "root://ceph-dev-gw3.gridpp.rl.ac.uk:1094/alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def?authz=`cat ral_env`"
                    >    >
                    >    >
                    >    >        But I get again an error
                    >    >
                    >    >
                    >    >        Prepare: [ERROR] Server responded with an error: [3010] Unable to locate alice:/04/36435/05422528-a162-11e8-b5f9-a310691b2def; permission denied
                    >    >
                    >    >        Best,
                    >    >
                    >    >
                    >    >        George
                    >    >
                    >    >
                    >    >        ________________________________
                    >    >        From: Yang, Wei <[log in to unmask]>
                    >    >        Sent: 14 February 2019 17:14:56
                    >    >        To: Patargias, George (STFC,RAL,SC); xrootd-l
                    >    >        Cc: Tim Adye; Johnson, Ian (STFC,RAL,SC)
                    >    >        Subject: Re: XRootD TPC error
                    >    >
                    >    >        Hi George,
                    >    >
                    >    >        Thanks for the clarification. I think the problem is with the command you use for TPC. Since you use /usr/bin/xrdcp in the ofs.tpc directive, the actual copy command xrootd proxy will run is
                    >    >
                    >    >        /usr/bin/xrdcp $1 $2
                    >    >
                    >    >        where $1 is root://eos/file, and $2 is /ECHO_path/file
                    >    >
                    >    >        This obviously won't work because the proxy instance doesn't have acces to /ECHO_path/file. What you can do is to replace /usr/bin/xrdcp by a script, say xrdcp-tpc.sh. In the script, you do
                    >    >
                    >    >        /usr/bin/xrdcp $1 root://ral_ceph/$2
                    >    >
                    >    >        Can you give this a try?
                    >    >
                    >    >        regards,
                    >    >        --
                    >    >        Wei Yang  |  [log in to unmask]  |  650-926-3338 (O)
                    >    >
                    >    >
                    >    >        On 2/14/19, 4:45 AM, "George Patargias - UKRI STFC" <[log in to unmask]> wrote:
                    >    >
                    >    >
                    >    >            Hi Wei,
                    >    >
                    >    >
                    >    >            Thanks, I actually work with Ian on this.
                    >    >
                    >    >
                    >    >            1) There are two xrootd systemd processes running on the Ceph gateway: xroot@proxy and [log in to unmask] So as far as I understand these are two instances. The ofs.tpc directive is placed in the config of [log in to unmask]
                    >    >
                    >    >
                    >    >            2), The source is an eos instance. the ALICE people don't have direct access to that service but they can contance the eos admins.
                    >    >
                    >    >
                    >    >            3) The destination at RAL is a Ceph endpoint and all the errors I see, I pasted in the initial email.
                    >    >
                    >    >
                    >    >            Best,
                    >    >
                    >    >
                    >    >            George
                    >    >
                    >    >
                    >    >
                    >    >
                    >    >
                    >    >            ________________________________
                    >    >            From: Yang, Wei <[log in to unmask]>
                    >    >            Sent: 12 February 2019 20:21:08
                    >    >            To: Patargias, George (STFC,RAL,SC); xrootd-l
                    >    >            Cc: Tim Adye; Johnson, Ian (STFC,RAL,SC)
                    >    >            Subject: Re: XRootD TPC error
                    >    >
                    >    >            Hi George,
                    >    >
                    >    >            I am not sure I have a clear picture. I am adding Tim Adye and Ian Johnson who are working with us on the ATLAS experiment side. I will start describing the issue we saw and I will have a few questions on what you see.
                    >    >
                    >    >            The CEPH plugin for Xrootd uses a single slash at the beginning of the path. So for a CEPH endpoint, the URL looks like root://host/path/file (the path/file are object id I guess), while all other xrootd endpoints use double slash like root://host//path/file. Xrootd TPC doesn't like single slash. Skipping the gory details about single vs double slashes, we agree the we will modify CEPH plugin to use double slash.
                    >    >
                    >    >            There is also a workaround by configuring the peer (not your end) to use "ofs.tpc oids ... ". We prefer not to use this in production, and to stick to the above change.
                    >    >
                    >    >            For the error you see, I need a bit more info about the setup and what you did:
                    >    >
                    >    >            1) is the xrootd TPC and ceph plugin run in same instance of Xrootd ? Or are they in separate instances. We know using separate instances (even on the same host) should work. I don't know whether anyone tried to run them in the same instance.
                    >    >            2) If the CEPH endpoint is the destination, do you see any error in TPC?
                    >    >            3) If the CEPH endpoint is the source, do you see any error in TPC.
                    >    >
                    >    >            In both 2) and 3), what is the error message in the CEPH xrootd server and from the client side?
                    >    >
                    >    >            Regarding the config line "ofs.tpc pgm /usr/bin/xrdcp -f --nopbar". I think it is best not to add "--nopbar". Some clients like FTS need this progress bar to determine that a long transfer is alive.
                    >    >
                    >    >            Also, for debugging purpose, /usr/bin/xrdcp can be replaced by a shell script. xrootd will pass the source (in URL format, root://remote-host//path/file) and destination (in /localpath/file) to the script. By using a script, you can log whatever you want to a file.
                    >    >
                    >    >            Also, depend on your setup, if the TPC isn't writing to the local storage, you will have to use a script (we can get to that later when we get answer about 1).
                    >    >
                    >    >            regards,
                    >    >            --
                    >    >            Wei Yang  |  [log in to unmask]  |  650-926-3338 (O)
                    >    >
                    >    >
                    >    >            On 2/12/19, 2:52 AM, "George Patargias - UKRI STFC" <[log in to unmask]> wrote:
                    >    >
                    >    >                Yes, we use the same Ceph back-end plug-in for XRootD
                    >    >
                    >    >                on the dev and production gateways in RAL.
                    >    >
                    >    >
                    >    >                Thanks,
                    >    >
                    >    >
                    >    >                George
                    >    >
                    >    >                ________________________________
                    >    >                From: Yang, Wei <[log in to unmask]>
                    >    >                Sent: 11 February 2019 19:31:55
                    >    >                To: Patargias, George (STFC,RAL,SC); xrootd-l
                    >    >                Subject: Re: XRootD TPC error
                    >    >
                    >    >                Does the xrootd gateway use the same plugin for CEPH, like what RAL uses?
                    >    >
                    >    >                --
                    >    >                Wei Yang  |  [log in to unmask]  |  650-926-3338(O)
                    >    >
                    >    >                ?-----Original Message-----
                    >    >                From: <[log in to unmask]> on behalf of George Patargias - UKRI STFC <[log in to unmask]>
                    >    >                Date: Monday, February 11, 2019 at 9:04 AM
                    >    >                To: xrootd-l <[log in to unmask]>
                    >    >                Subject: XRootD TPC error
                    >    >
                    >    >                    Hello,
                    >    >
                    >    >
                    >    >                    We have set up a pool and an xrootd gateway on our Ceph dev cluster for ALICE. Three out four tests (add, get, rm) are green
                    >    >                    but the TPC test currently fails.
                    >    >
                    >    >
                    >    >                    On the ALICE side the error is
                    >    >
                    >    >
                    >    >                    xrdcp (TPC==1) exited with exit code 54: [ERROR] Server responded with an error: [3005] [ERROR] Server responded with an error: [3011] No such file or directory
                    >    >
                    >    >
                    >    >                    When I try to copy the file on, I get
                    >    >
                    >    >
                    >    >                    Run: [ERROR] Server responded with an error: [3005] [ERROR] Server responded with an error: [3010] Unable to open - tpc origin mismatch /04/36435/05422528-a162-11e8-b5f9-a310691b2def; operation not permitted
                    >    >
                    >    >                    I use this directive
                    >    >
                    >    >                    ofs.tpc pgm /usr/bin/xrdcp -f --nopbar
                    >    >
                    >    >
                    >    >                    Is it in the wrong place in the config file (see attached xrootd-proxy.cfg)? Or is there anything missing from it?
                    >    >
                    >    >
                    >    >                    Many thanks in advance,
                    >    >
                    >    >
                    >    >                    George
                    >    >
                    >    >
                    >    >                    ########################################################################
                    >    >                    Use REPLY-ALL to reply to list
                    >    >
                    >    >                    To unsubscribe from the XROOTD-L list, click the following link:
                    >    >                    https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
                    >    >
                    >    > ########################################################################
                    >    > Use REPLY-ALL to reply to list
                    >    >
                    >    > To unsubscribe from the XROOTD-L list, click the following link:
                    >    > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
                    >    >
                    >
                    >
                    >




            ########################################################################
            Use REPLY-ALL to reply to list

            To unsubscribe from the XROOTD-L list, click the following link:
            https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1







########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1