-
Hello, "Adding a file" $ dirac-dms-add-file /biomed/user/c/creatis/vip/data/groups/Applications/fsl_bet-test/6.0.1/bin/fsl_bet-test.sh.tar.gz fsl_bet-test.sh.tar.gz SBG-disk -dd
2022-03-23 10:36:25 UTC dirac-dms-add-file NOTICE:
Uploading /biomed/user/c/creatis/vip/data/groups/Applications/fsl_bet-test/6.0.1/bin/fsl_bet-test.sh.tar.gz
2022-03-23 10:36:26 UTC dirac-dms-add-file/DIRAC.Resources.Storage.StorageElement/SE[SBG-disk] VERBOSE: Failure in plugin to perform putFile Plugin: GFAL2_HTTPS lfn: /biomed/user/c/creatis/vip/data/groups/Applications/fsl_bet-test/6.0.1/bin/fsl_bet-test.sh.tar.gz error Operation not permitted ( 1 : Failed to copy file fsl_bet-test.sh.tar.gz to destination url https://sbgse1.in2p3.fr/dpm/in2p3.fr/home/biomed/user/c/creatis/vip/data/groups/Applications/fsl_bet-test/6.0.1/bin/fsl_bet-test.sh.tar.gz: [1] DESTINATION OVERWRITE DavPosix::unlink HTTP 403 : Permission refused )
2022-03-23 10:36:29 UTC dirac-dms-add-file NOTICE: Successfully uploaded file to SBG-disk "Removing a file" $ drm /biomed/user/c/creatis/vip/data/groups/Applications/fsl_bet-test/6.0.1/bin/fsl_bet-test.sh.tar.gz
ERROR /biomed/user/c/creatis/vip/data/groups/Applications/fsl_bet-test/6.0.1/bin/fsl_bet-test.sh.tar.gz: Communication error on send ( 70 : GError('globus_ftp_client: the server responded with an error 530 Login denied ', 70)) Invalid exchange ( 52 : GError('Failed to delete file (Invalid exchange)', 52))
0 object(s) removed in total
1 object(s) failed removal in total Thank in advance. |
Beta Was this translation helpful? Give feedback.
Answered by
fstagni
Apr 29, 2022
Replies: 1 comment
-
I realize that this one was never answered. It seems to me that in both cases the errors depend from the storage element themselves, and that are not DIRAC specific issues. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
fstagni
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I realize that this one was never answered. It seems to me that in both cases the errors depend from the storage element themselves, and that are not DIRAC specific issues.