New citrine release- 4.8.104?

21

Hi Elvin,

We have tested the 4.8.105 version and we are happy with all the tests we have run.We will push this version in to production tomorrow.

The main thing was that an attempt to copy via TPC a file that is not on disk resulted in the following (impressive looking) error

-bash-4.2$ gfal-copy --copy-mode pull https://antares-preprod.stfc.ac.uk:9000/eos/antarespreprodtier1/dteam/random_100MB https://webdav.echo.stfc.ac.uk:1094/dteam:scratch/random_100MB
Copying https://antares-preprod.stfc.ac.uk:9000/eos/antarespreprodtier1/dteam/random_100MB [FAILED] after 1s
gfal-copy error: 5 (Input/output error) - TRANSFER ERROR: Copy failed (3rd pull). Last attempt: Transfer failure: Remote side failed with status code 500; error message: " Error | CERN <!-- THIS IS THE DEFAULT FRAMEWORK CSS IT’S A BIT HEAVY FOR THIS DOCUMENT SO WE’LL CALL JUST THE STYLESHEETS WE NEED <link href=

and exit code 5 (instead of 0 which is good) and also no stub created in the destination

Just to report (as a minor issue for EOS 5 rather then EOS 4) that a stub is created if a direct (instead of TPC) webdav transfer of an unstaged file is attempted

bash-4.2$ gfal-copy https://antares-preprod.stfc.ac.uk:9000/eos/antarespreprodtier1/dteam/random_300MB .
Copying https://antares-preprod.stfc.ac.uk:9000/eos/antarespreprodtier1/dteam/random_300MB [FAILED] after 0s
gfal-copy error: 5 (Input/output error) - Result HTTP 500 : Unexpected server error: 500 , while readding after 1 attempts
-bash-4.2$ ls -lrt random_300MB
-rwxr-xr-x 1 georgep esc 0 Sep 13 16:20 random_300MB

George

22

Hi George,

Thanks for your feedback and happy to hear things are working as expected for you.

As far as the “unusual” error message is concerned, we provide this error message “page” for errors that don’t have an obvious standard HTTP error msg. In this particular case, we don’t have a specific error message for EIO (5).

Concerning the leftover files from the gfal-copy command, this I think you should open a ticket with the FTS team and have it fixed. It’s not something we can control from EOS.

Thanks,
Elvin

23

Hi @esindril, (cc. also @Mihai_Popescu),
We are now seeing the effect of this fix in production. While the fix appears to work, the error message is incomprehensible to shifters and anyone else; e.g. [1].
Maybe this message can be fixed in FTS or Gfal, if there’s no possibility to improve it in EOS ?

[1]
TRANSFER [5] TRANSFER ERROR: Copy failed (3rd pull). Last attempt: Transfer failure: Remote side failed with status code 500; error message: " Error | CERN <!-- THIS IS THE DEFAULT FRAMEWORK CSS IT’S A BIT HEAVY FOR THIS DOCUMENT SO WE’LL CALL JUST THE STYLESHEETS WE NEED <link href=

24

Hi James,

Indeed, the error message is not nice - this is just the default error page content what EOS gives back. We can definitely fix this in EOS, but only on the v5 version as we don’t plan any new v4 release.
The correct error code should at least make FTS work properly in such cases.

Cheers,
Elvin