Hi,

I'm running this command xrdcp -v -d3 /bin/bash root://localhost/public/test-1 with a modified version of dCache that provides a login token as part of the redirection. I'm testing this with the current tip of the master branch (f1d4e89e22) however, I see the same behaviour with released versions of xrootd.

Here is the activity, from dCache's perspective:

level=INFO ts=2021-10-12T14:27:02.018+0200 event=org.dcache.xrootd.connection.start session=door:Xrootd-sprocket@dCacheDomain:AAXOJvZtOtA socket.remote=127.0.0.1:53898 socket.local=127.0.0.1:1094
level=INFO ts=2021-10-12T14:27:02.037+0200 event=org.dcache.xrootd.request session=door:Xrootd-sprocket@dCacheDomain:AAXOJvZtOtA request=protocol response=ok
level=INFO ts=2021-10-12T14:27:02.067+0200 event=org.dcache.xrootd.request session=door:Xrootd-sprocket@dCacheDomain:AAXOJvZtOtA request=login username=paul capver=5 pid=3597 token=?xrd.cc=de&xrd.tz=1&xrd.appname=xrdcp&xrd.info=&xrd.hostname=sprocket.desy.de&xrd.rn=v20211011-f1d4e89e2 response=ok sessionId=064D58193438155712E9505BD2E72402
level=ERROR ts=2021-10-12T14:27:02.107+0200 event=org.dcache.xrootd.request session=door:Xrootd-sprocket@dCacheDomain:AAXOJvZtOtA request=stat path=public/test-1 vfs=false response=error error.code=NotFound error.msg="No such file"
level=INFO ts=2021-10-12T14:27:02.340+0200 event=org.dcache.xrootd.request session=door:Xrootd-sprocket@dCacheDomain:AAXOJvZtOtA request=open path=public/test-1 opaque=oss.asize=1168776 mode=0644 options=0x468 response=redirect host=localhost port=33140 token=org.dcache.door=localhost:1094
level=INFO ts=2021-10-12T14:27:02.364+0200 event=org.dcache.xrootd.connection.start session=pool:pool_write@dCacheDomain:xrootd:464d6bb5 socket.remote=127.0.0.1:36418 socket.local=127.0.0.1:33140
level=INFO ts=2021-10-12T14:27:02.370+0200 event=org.dcache.xrootd.request session=pool:pool_write@dCacheDomain:xrootd:464d6bb5 request=protocol response=ok
level=INFO ts=2021-10-12T14:27:02.372+0200 event=org.dcache.xrootd.request session=pool:pool_write@dCacheDomain:xrootd:464d6bb5 request=login username=paul capver=5 pid=3597 token=?xrd.cc=de&xrd.tz=1&xrd.appname=xrdcp&xrd.info=&xrd.hostname=sprocket.desy.de&xrd.rn=v20211011-f1d4e89e2 response=ok sessionId=6454ED77F14760F6FABB3A19E430DF25
level=INFO ts=2021-10-12T14:27:02.379+0200 event=org.dcache.xrootd.request session=pool:pool_write@dCacheDomain:xrootd:464d6bb5 request=open path=public/test-1 opaque=org.dcache.uuid=6c8975d4-a045-4b39-8380-8998815463d6&org.dcache.xrootd.client=paul.3597@localhost&oss.asize=1168776 mode=0644 options=0x468 response=ok handle=0 flags=0 modtime=1970-01-01T00:00:00Z size=0
level=INFO ts=2021-10-12T14:27:02.478+0200 event=org.dcache.xrootd.request session=pool:pool_write@dCacheDomain:xrootd:464d6bb5 request=close handle=0 response=ok
level=INFO ts=2021-10-12T14:27:02.505+0200 event=org.dcache.xrootd.connection.end session=door:Xrootd-sprocket@dCacheDomain:AAXOJvZtOtA
level=INFO ts=2021-10-12T14:27:02.506+0200 event=org.dcache.xrootd.connection.end session=pool:pool_write@dCacheDomain:xrootd:464d6bb5

Perhaps the important parts are the door's replying (token=org.dcache.door=localhost:1094) and the subsequent token presented to the pool (token=?xrd.cc=de&xrd.tz=1&xrd.appname=[..etc...]).

Here are a few lines from client's perspective. First, here's the client receiving the redirection respond from the door:

[2021-10-12 14:27:02.341475 +0200][Dump   ][XRootD            ] [localhost:1094] Got kXR_redirect response to message kXR_open (file: public/test-1?oss.asize=1168776, mode: 0644, flags: kXR_new kXR_open_updt kXR_async kXR_retstat ): localhost?org.dcache.xrootd.client=paul.3597@localhost&oss.asize=1168776&org.dcache.uuid=6c8975d4-a045-4b39-8380-8998815463d6?org.dcache.door=localhost:1094, port 33140

Second, here is the client sending the kXR_login request to the pool:

[2021-10-12 14:27:02.370965 +0200][Debug  ][XRootDTransport   ] [localhost:33140.0] Sending out kXR_login request, username: paul, cgi: ?xrd.cc=de&xrd.tz=1&xrd.appname=xrdcp&xrd.info=&xrd.hostname=sprocket.desy.de&xrd.rn=v20211011-f1d4e89e2, dual-stack: false, private IPv4: true, private IPv6: false

There doesn't seem to be an error message, where xrdcp complains that the login token is invalid or rejected for some other reason, yet the kXR_login request to the pool, triggered by a redirection, does not contain the desired login token.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Use REPLY-ALL to reply to list

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