-
Notifications
You must be signed in to change notification settings - Fork 5
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
Authentication error with aspera #122
Comments
I'm getting the same error with Webi-cli 7.3.0 and IBM Aspera Connect version 4.2.10 (749). My work method is also the same: I used the same script that I successfully used to upload last year. Now I keep getting errors over the past couple of days. Actually, I was getting a different error yesterday:
I have also tried FTP (which is my second option, as it did not work before), which returns this error:
Which gives me the impression that there may be some problem with the server. However, interestingly, uploading files 'manually' using (Sorry if this seems to go a bit off-topic. I just really hope the ENA can help us get our data uploaded!) |
I have found a workaround to upload raw reads! What I ended up doing is uploading the fastq files with the
So far I have only tested this with reads (fastq files). I am not sure if it works with other data types as well (e.g. assemblies). |
See error message:
`INFO : Your application version is 7.2.1
INFO : Please upgrade to Webin-CLI version 7.0.1 or later if you see the following error: Failed to initialise validator. Could not retrieve BioSample.
INFO : Uploading files to : webin.ebi.ac.uk
INFO : Creating report file: /scratch/d85/yc1401/Genome_submission/./webin-cli.report
WARN : Aspera upload failed. Client exit code : 1
WARN : Client error :
Session Stop (Error: failed to authenticate)
ascp: failed to authenticate, exiting.
WARN : Retrying file upload.
WARN : Aspera upload failed. Client exit code : 1
WARN : Client error :
Session Stop (Error: failed to authenticate)
ascp: failed to authenticate, exiting.
`
Aspera used to work for me and I am using exactly the same script. The only difference is upgrading webin-cli from 7.1.1 to 7.2.1, which shouldn't matter. Or could the be a sever issue?
The text was updated successfully, but these errors were encountered: