search

enasequence / webin-cli

Webin command line submission program.
Apache License 2.0
30 stars 5 forks source link

Authentication error with aspera #122

Open YibiChen opened 5 months ago

YibiChen commented 5 months ago

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?

samnooij commented 4 months ago

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:

WARN : Aspera upload failed. Client exit code : 1
WARN : Client error :

Session Stop (Error: Server aborted session: Error 13 (EACCES) creating destination path "/fire/staging/era/upload/Webin-52850/webin-cli/reads/LUMC_QRD001")

I have also tried FTP (which is my second option, as it did not work before), which returns this error:

ERROR: Last received FTP Reply. ReplyCode : 550, ReplyStrings : [550 Create directory operation failed.]
ERROR: Failed to create directory "LUMC_QRD001" on FTP server. Failed to upload files to server because of a system error.
ERROR: Some or all submissions failed. Please see application logs.

Which gives me the impression that there may be some problem with the server.

However, interestingly, uploading files 'manually' using ascp as described here did not give me errors before today. So I think I have sent some files to the ENA, but they don't show up in the web interface, so now I'm not sure what happened to those files. Right now this option also doesn't work and I checked my credential by logging in on the webinterface and that works fine, so the problem should not be with the credentials.

(Sorry if this seems to go a bit off-topic. I just really hope the ENA can help us get our data uploaded!)

samnooij commented 4 months ago

I have found a workaround to upload raw reads! What I ended up doing is uploading the fastq files with the ascp command as I linked earlier. Then I uploaded the associated metadata using the 'interactive' method described here. So in short:

  1. upload fastq files using ascp
  2. download the spreadsheet template (TSV file) in the web interface
  3. fill in the spreadsheet with the correct metadata
  4. upload the spreadsheet in the web interface

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).