-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error propagation from caching proxy / posix layer to remote client #613
Comments
The above error was observed at NERSC ... I can not reproduce it at UCSD with current master. However, I do get "no such file or directory" error which is misleading. It seems proper reporting would require a new type of error message that would make it clear the problem is on the server/cache and not with the client setup. Client: [2017-11-16 12:25:03.069588 -0800][Debug ][XRootD ] [xrd-cache-1.t2:7777] Handling error while processing kXR_open (file: /store/user/matevz/A_FILE, mode: 00, flags: kXR_open_read kXR_async kXR_retstat ): [ERROR] Error response: Unknown error 3011. Server log: 171116 12:19:36 3530654 ofs_open: matevz.3530817:20@localhost Unable to open /store/user/matevz/A_FILE; no such file or directory |
What do you propose beng the correct message?
…On Thu, 16 Nov 2017, Matev Tadel wrote:
The above error was observed at NERSC ... I can not reproduce it at UCSD with current master.
However, I do get "no such file or directory" error which is misleading. It seems proper reporting would require a new type of error message that would make it clear the problem is on the server/cache and not with the client setup.
Client:
[2017-11-16 12:25:03.069588 -0800][Debug ][XRootD ] [xrd-cache-1.t2:7777] Handling error while processing kXR_open (file: /store/user/matevz/A_FILE, mode: 00, flags: kXR_open_read kXR_async kXR_retstat ): [ERROR] Error response: Unknown error 3011.
[2017-11-16 12:25:03.069640 -0800][Debug ][File ] ***@***.***://xrd-cache-1.t2:7777//store/user/matevz/A_FILE] Open has returned with status [ERROR] Server responded with an error: [3011] Unable to open /store/user/matevz/A_FILE; no such file or directory
[2017-11-16 12:25:03.069651 -0800][Debug ][File ] ***@***.***://xrd-cache-1.t2:7777//store/user/matevz/A_FILE] Error while opening at xrd-cache-1.t2:7777: [ERROR] Server responded with an error: [3011] Unable to open /store/user/matevz/A_FILE; no such file or directory
[0B/0B][100%][==================================================][0B/s]
Run: [ERROR] Server responded with an error: [3011] Unable to open /store/user/matevz/A_FILE; no such file or directory
Server log:
171116 12:19:36 3530654 ofs_open: ***@***.*** Unable to open /store/user/matevz/A_FILE; no such file or directory
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#613 (comment)
|
It should make it clear to the user that the problem is on the server side and that cache operators should be contacted to resolve the issue. I was thinking about "Server-side configuration problem (can not authenticate to remote origin)" to make it clear it is not this clients authentication that is failing. How clear are the error codes you are getting from client in the first place? |
When caching proxy fails to connect to origin server due to missing CA packages (and possibly due to any authorization related problem) the report on the connecting client reports this as "too many levels of symbolic links".
E.g. from xrdcp
bash-4.1$ xrdcp root://cori21-224.nersc.gov:1094//store/mc/RunIISummer17PrePremix/Neutrino_E-10_gun/GEN-SIM-DIGI-RAW/MCv1_92X_upgrade2017_realistic_v8-v1/110012/265C18D7-C575-E711-8124-A0369FC5D5D8.root /dev/null
[0B/0B][100%][==================================================][0B/s]
Run: [ERROR] Server responded with an error: [3005] Unable to open /store/mc/RunIISummer17PrePremix/Neutrino_E-10_gun/GEN-SIM-DIGI-RAW/MCv1_92X_upgrade2017_realistic_v8-v1/110012/265C18D7-C575-E711-8124-A0369FC5D5D8.root; too many levels of symbolic links
The text was updated successfully, but these errors were encountered: