#1 Downloading <filename> failed

Open
opened 1 year ago by rfabbri · 9 comments

Hi, I always get this error message when trying to download a file from the dataset: "Downloading failed: authorisation failed or remote storage unavailable". I can unlock the file without problems. Could you help me to resolve and get the data? Thanks

Hi, I always get this error message when trying to download a file from the dataset: "Downloading <filename> failed: authorisation failed or remote storage unavailable". I can unlock the file without problems. Could you help me to resolve and get the data? Thanks
Andrey Vinogradov commented 1 year ago
Owner

Hello, Rachele, I will write to the G-node support team right now. -Andrey

Hello, Rachele, I will write to the G-node support team right now. -Andrey

Hi Rachele!

did you successfully log into the gin client on your machine? I usually get this kind of error message when there is no logged in user.

Hi Rachele! did you successfully log into the gin client on your machine? I usually get this kind of error message when there is no logged in user.
Rachele Fabbri commented 1 year ago
Poster

Hi Michael,

Yes, I successfully logged into gin client. I tried to download a file from the dataset within an hard disk with lot of disk space available. The download starts but it stops at 18,6%. I tried with two different files and always the download stops at 18,6%.

Hi Michael, Yes, I successfully logged into gin client. I tried to download a file from the dataset within an hard disk with lot of disk space available. The download starts but it stops at 18,6%. I tried with two different files and always the download stops at 18,6%.

Hi Rachele,

I double checked, but so far I was not able to reproduce the error you are experiencing, on my end the reported file download alright.

Could you check the gin client log for further details? You should be able to find them at c:\users{user}\appdata\local\g-node\gin\gin.log. You can backup and clear the log, then directly start the download. Maybe this gives more insight into why the download stops on your end.

Hi Rachele, I double checked, but so far I was not able to reproduce the error you are experiencing, on my end the reported file download alright. Could you check the gin client log for further details? You should be able to find them at c:\users\{user}\appdata\local\g-node\gin\gin.log. You can backup and clear the log, then directly start the download. Maybe this gives more insight into why the download stops on your end.
Andrey Vinogradov commented 1 year ago
Owner

Hi Rachele, Could you, please, inform me whether you are able to solve the problem? Thank you, -Andrey

Hi Rachele, Could you, please, inform me whether you are able to solve the problem? Thank you, -Andrey
Rachele Fabbri commented 1 year ago
Poster

Hi Andrey,

unfortunately I am still trying to resolve the issue.

Here the gin client log: 2023/02/01 14:01:27 === LOGINIT === 2023/02/01 14:01:27 VERSION: GIN command line client 1.12 Build 001474 (b3e038038a) git: 2.31.0.windows.1 git-annex: 8.20210224-gf951847c6 2023/02/01 14:01:27 COMMAND: gin.exe get-content hPSC_20517_MEA1_DIV14.h5 2023/02/01 14:01:27 CWD: D:\PhD\Comparative_MEA_dataset\Data\hPSC_MEA1 2023/02/01 14:01:27 Loading token [server gin] C:\Users\fabbr\AppData\Roaming\g-node\gin\gin.token 2023/02/01 14:01:27 env GIT_SSH_COMMAND=ssh -i C:/Users/fabbr/AppData/Roaming/g-node/gin/gin.key -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes -o 'UserKnownHostsFile="C:\Users\fabbr\AppData\Roaming\g-node\gin\known_hosts"' 2023/02/01 14:01:27 Running shell command (Dir: D:\PhD\Comparative_MEA_dataset\Data\hPSC_MEA1): git rev-parse --show-toplevel 2023/02/01 14:01:27 env GIT_SSH_COMMAND=ssh -i C:/Users/fabbr/AppData/Roaming/g-node/gin/gin.key -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes -o 'UserKnownHostsFile="C:\Users\fabbr\AppData\Roaming\g-node\gin\known_hosts"' 2023/02/01 14:01:27 Running shell command (Dir: D:\PhD\Comparative_MEA_dataset\Data\hPSC_MEA1): git config --local --get annex.version 2023/02/01 14:01:27 GetContent 2023/02/01 14:01:27 ExpandGlobs: Checking for glob expansion for hPSC_20517_MEA1_DIV14.h5 2023/02/01 14:01:27 env GIT_SSH_COMMAND=ssh -i C:/Users/fabbr/AppData/Roaming/g-node/gin/gin.key -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes -o 'UserKnownHostsFile="C:\Users\fabbr\AppData\Roaming\g-node\gin\known_hosts"' 2023/02/01 14:01:27 Running shell command (Dir: D:\PhD\Comparative_MEA_dataset\Data\hPSC_MEA1): git annex get --json-progress hPSC_20517_MEA1_DIV14.h5 2023/02/01 14:01:57 Error during AnnexGet 2023/02/01 14:01:57 2023/02/01 14:01:57 EXIT OK 2023/02/01 14:01:57 === LOGEND ===

Hi Andrey, unfortunately I am still trying to resolve the issue. Here the gin client log: 2023/02/01 14:01:27 === LOGINIT === 2023/02/01 14:01:27 VERSION: GIN command line client 1.12 Build 001474 (b3e038038a6be25034de12f00b3fc10df26b785f) git: 2.31.0.windows.1 git-annex: 8.20210224-gf951847c6 2023/02/01 14:01:27 COMMAND: gin.exe get-content hPSC_20517_MEA1_DIV14.h5 2023/02/01 14:01:27 CWD: D:\PhD\Comparative_MEA_dataset\Data\hPSC_MEA1 2023/02/01 14:01:27 Loading token [server gin] C:\Users\fabbr\AppData\Roaming\g-node\gin\gin.token 2023/02/01 14:01:27 env GIT_SSH_COMMAND=ssh -i C:/Users/fabbr/AppData/Roaming/g-node/gin/gin.key -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes -o 'UserKnownHostsFile="C:\Users\fabbr\AppData\Roaming\g-node\gin\known_hosts"' 2023/02/01 14:01:27 Running shell command (Dir: D:\PhD\Comparative_MEA_dataset\Data\hPSC_MEA1): git rev-parse --show-toplevel 2023/02/01 14:01:27 env GIT_SSH_COMMAND=ssh -i C:/Users/fabbr/AppData/Roaming/g-node/gin/gin.key -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes -o 'UserKnownHostsFile="C:\Users\fabbr\AppData\Roaming\g-node\gin\known_hosts"' 2023/02/01 14:01:27 Running shell command (Dir: D:\PhD\Comparative_MEA_dataset\Data\hPSC_MEA1): git config --local --get annex.version 2023/02/01 14:01:27 GetContent 2023/02/01 14:01:27 ExpandGlobs: Checking for glob expansion for hPSC_20517_MEA1_DIV14.h5 2023/02/01 14:01:27 env GIT_SSH_COMMAND=ssh -i C:/Users/fabbr/AppData/Roaming/g-node/gin/gin.key -o IdentitiesOnly=yes -o StrictHostKeyChecking=yes -o 'UserKnownHostsFile="C:\Users\fabbr\AppData\Roaming\g-node\gin\known_hosts"' 2023/02/01 14:01:27 Running shell command (Dir: D:\PhD\Comparative_MEA_dataset\Data\hPSC_MEA1): git annex get --json-progress hPSC_20517_MEA1_DIV14.h5 2023/02/01 14:01:57 Error during AnnexGet 2023/02/01 14:01:57 2023/02/01 14:01:57 EXIT OK 2023/02/01 14:01:57 === LOGEND ===

Could you try running the following command from the root of the repository?

gin git annex get -v --json-progress Data/hPSC_MEA1/hPSC_20517_MEA1_DIV14.h5

It will be quite spammy on the command line, but it is calling the underlying routines downloading the file content with more information displayed. I hope that then a more detailed error message will show up.

Could you try running the following command from the root of the repository? `gin git annex get -v --json-progress Data/hPSC_MEA1/hPSC_20517_MEA1_DIV14.h5` It will be quite spammy on the command line, but it is calling the underlying routines downloading the file content with more information displayed. I hope that then a more detailed error message will show up.
Rachele Fabbri commented 1 year ago
Poster

This is the message I get:

{"command":"get","wanted":[{"here":false,"uuid":"60e198f1-0f4c-4355-8977-80a5af79f6","description":"@med068pc183"}],"note":"from origin...\nUnable to access these remotes: origin","success":false,"input":["hPSC_20517_MEA1_DIV14.h5"],"key":"MD5-s23040148932--c9561d3176","error-messages":[],"file":"hPSC_20517_MEA1_DIV14.h5"} You have enabled concurrency, but git-annex is not able to use ssh connection caching. This may result in multiple ssh processes prompting for passwords at the same time. annex.sshcaching is not set to true Transfer failed git-annex: get: 1 failed

This is the message I get: {"command":"get","wanted":[{"here":false,"uuid":"60e198f1-0f4c-4355-8977-80a5af79f65e","description":"@med068pc183"}],"note":"from origin...\nUnable to access these remotes: origin","success":false,"input":["hPSC_20517_MEA1_DIV14.h5"],"key":"MD5-s23040148932--c9561d3176fa906815af166b0fbabbf7","error-messages":[],"file":"hPSC_20517_MEA1_DIV14.h5"} You have enabled concurrency, but git-annex is not able to use ssh connection caching. This may result in multiple ssh processes prompting for passwords at the same time. annex.sshcaching is not set to true Transfer failed git-annex: get: 1 failed

I think the issue is related to this git-annex thread: no_passphrase_ask_for_the_2nd_ssh_invocation but unfortunately the thread does not offer any obvious solution.

I am not sure we can tackle this particular issue from our end, but I will keep digging. You might need to figure out which ssh client you are using and which combination of git-annex config settings for annex.sshcaching and annex.adviceNoSshCaching works with your Windows distribution.

The associated git annex man page entries are:

annex.sshcaching
    By default, git-annex caches ssh connections using ssh's 
ControlMaster and ControlPersist settings (if built using a 
new enough ssh). To disable this, set to false.

annex.adviceNoSshCaching
    When git-annex is unable to use ssh connection caching, or 
has been configured not to, and concurrency is enabled, it will 
warn that this might result in multiple ssh processes prompting 
for passwords at the same time. To disable that warning, eg if 
you have configured ssh connection caching yourself, or have 
ssh agent caching passwords, set this to false.
I think the issue is related to this git-annex thread: [no_passphrase_ask_for_the_2nd_ssh_invocation](https://git-annex.branchable.com/bugs/get__58___no_passphrase_ask_for_the_2nd_ssh_invocation/) but unfortunately the thread does not offer any obvious solution. I am not sure we can tackle this particular issue from our end, but I will keep digging. You might need to figure out which ssh client you are using and which combination of git-annex config settings for `annex.sshcaching` and `annex.adviceNoSshCaching` works with your Windows distribution. The associated git annex man page entries are: ``` annex.sshcaching By default, git-annex caches ssh connections using ssh's ControlMaster and ControlPersist settings (if built using a new enough ssh). To disable this, set to false. annex.adviceNoSshCaching When git-annex is unable to use ssh connection caching, or has been configured not to, and concurrency is enabled, it will warn that this might result in multiple ssh processes prompting for passwords at the same time. To disable that warning, eg if you have configured ssh connection caching yourself, or have ssh agent caching passwords, set this to false. ```
Sign in to join this conversation.
No Label
No Milestone
No assignee
3 Participants
Loading...
Cancel
Save
There is no content yet.