 |
 |
@pmusset, from the xrootd server log file you sent to Andy, i see these lines:
[2021-02-22 14:53:53.567882 +0000][Debug ][XrdClHttp ] Opened: [log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out" rel="nofollow">https:[log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out?
Posix::Stat([log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out" rel="nofollow">https:[log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out?)
[2021-02-22 14:53:53.605503 +0000][Debug ][XrdClHttp ] Stat-ed URL: [log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out" rel="nofollow">https:[log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out?
210222 14:53:53 106 XrdPfc_Cache: info Attach() [log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out" rel="nofollow">https:[log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out?
210222 14:53:53 106 XrdPfc_Cache: debug GetFile /eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out, io 0x7f1fdc180250
210222 14:53:53 106 XrdPfc_IO: debug initCachedStat got stat from client res = 0, size = 268435456 [log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out" rel="nofollow">https:[log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out?
This tells me that the xrdcl-http stat() request was successful because it got the correct file size. I can do the same thing using xrdfs root://eoseulake.cern.ch/ stat /eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out (with my ATLAS or dTeam certificate).
BTW, xrdcl-http open() was also successful, but I guess open() is probably meaningless in HTTP protocol. It is only meaningful in the Davix library.
Later in the xrootd server log, I see:
210222 14:53:53 106 XrdPfc_IO: dump Read() 0x7f1fdc180250 off: 0 size: 262144 [log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out" rel="nofollow">https:[log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out?
...
[2021-02-22 14:53:53.638951 +0000][Debug ][XrdClHttp ] Read 0 bytes, at offset 0, from URL: [log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out" rel="nofollow">https:[log in to unmask]:443//eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out?
...
210222 14:53:53 105 XrdPfc_File: error ProcessBlockResponse Wrong number of bytes received, assuming remote/local file size mismatch, unlinking local files and initiating shutdown of File object /eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out
...
210222 14:53:53 106 XrdPfc_File: error Read() io 0x7f1fdc180250, block 0 finished with error 121 remote I/O error /eos/eulake/tests/rucio_test/eulake_1/ESCAPE_CCIN2P3_RAHAL_test/1f/50/tes2_iorandom_256MB_1.out
After seeing this, I tried to use curl to copy (with my ATLAS and dTeam certificates). Though I got a "HTTP/1.1 200 OK", the content I got back is not your data but a html file telling me "There was an error loading the page you requested — This page may have been deleted or moved." along with a few links to CERN and a CERN logo.
So, question: what certificate should I use to access this file. If I don't have the right x509 certificate, I expect the web server NOT to tell me "HTTP/1.1 200 OK" but something like "HTTP/1.1 403" (btw, if I don't have an x509 certificate at all, and use the -k option with curl, I do get "HTTP/1.1 403 token authorization failed").
So what a mess in the world of industry standard?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
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