en:navody:faq:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
en:navody:faq:start [19.04.2018 10:31]
danecek@cesnet.cz
en:navody:faq:start [03.05.2018 14:51]
danecek@cesnet.cz
Line 304: Line 304:
  
 __Solution:​__ __Solution:​__
-Time slot for moving your data is two weeks (14 dayssince you received first email notification. After that period is your access to the Data Storage restricted from the reason ​of moving ​other groups of users. In case you did not finish moving of your data, please contact Data Storage Administrators and they will provide you additional access to the Data Storage.+That issue can be caused by two reasons. First is expired membership in particular virtual organization ​(VOor expiration ​of data moving ​period
  
 +In case of suspicion for VO membership expiration, please check your inbox and make sure, that you prolonged your membership in particular VO. If you didn't do so, you can easily submit prolongation request (link can be found in the email notification about membership prolongation). Your membership (access to the data storage) will be prolonged/​activated **until 60 min after request being approved by VO admin**.  ​
 +
 +Did you exceed data moving period? Time slot for moving your data is two weeks (14 days) since you received first email notification. After that period is your access to the Data Storage restricted from the reason of moving other groups of users. In case you did not finish moving of your data, please contact Data Storage Administrators and they will provide you additional access to the Data Storage.
 +
 +=== I want to move my data, but I got problem with permissions. ===
 +__Problem description:​__
 +I tried to transfer my data using Globus/​rsync protocol, but I got problem with low permissions,​ see the log below:
 +
 +<​code>​Error (transfer)
 +      Endpoint: ducesnet#​globusonline (d8eb370a-6d04-11e5-ba46-22000b92c6ec)
 +      Server: globus.du1.cesnet.cz:​2811
 +      File: /​~/​VO_storage-cache_tape/​backups/​tests/​fLLgaxLv2R1/​4Hcy5vd98A0
 +      Command: RETR ~/​VO_storage-cache_tape/​backups/​tests/​fLLgaxLv2R1/​4Hcy5vd98A0
 +      Message: Fatal FTP response
 +      ---
 +      Details: 500-Command failed. : globus_l_gfs_file_open ​ failed.\r\n500-globus_xio:​ Unable to open file  ​
 +      /​exports/​home/​username/​VO_storage-cache_tape/​VO_storage-cache_tape/​backups/​tests/​fLLgaxLv2R1/​4Hcy5vd98A0\r\n500- ​
 +      globus_xio: ​ System error in open: Permission denied\r\n500-globus_xio:​ A system ​ call failed: Permission denied\r\n500 End.\r\n
 +</​code>​
 +
 +<note important>​That issue is typically related to an encrypted files, or files generated by any backup toll.</​note>​
 +
 +__Solution:​__
 +That issue can be solved by checking and setting correct permissions on desired files/​directories directly on the data storage. In case you use any system from Windows family, you can use [[en:​navody:​terminal_windows:​start#​moba_permissions|this tutorial]].
 +
 +Please connect to the data storage using ssh protocol.
 +
 +<​code>​ssh username@ssh.du1.cesnet.cz</​code>​
 +
 +Now go to the directory, which you wish to check. Here is obvious which files are causing the issue. It is **test1 a testfile1**.
 +
 +<​code>​username@store:​~>​cd VO_storage-cache_tape
 +username@store:​~/​VO_storage-cache_tape>​ls -alh
 +total 84K
 +drwx-----T ​   4 username storage ​ 82 May  3 09:57 .
 +drwxr-x--- 1378 root     ​storage 56K May  3 13:30 ..
 +d--------- ​   2 username storage ​ 10 May  3 09:56 test1
 +drwxr-xr-x ​   2 username storage ​ 10 May  3 09:56 test2
 +---------- ​   1 username storage ​  0 May  3 09:56 testfile1
 +-rw-r--r-- ​   1 username storage ​  0 May  3 09:56 testfile2
 +</​code>​
 +
 +If you wish to look for problematic files/​directories in the directory tree, you can use following command:
 +
 +<​code>#​ find -L . -perm +u-rwx,​g-rwx,​o-rwx</​code>​
 +
 +Alternatively you can use find command and simultaneously correct missing permissions,​ see below:
 +
 +<​code>#​ find -L . -perm +u-rwx,​g-rwx,​o-rwx -exec chmod u+rX '​{}'​ \;</​code>​
  
Last modified:: 26.05.2023 11:09