file upload 'max retries exceeded' messages

Description

User is uploading data and experiencing the following errors (attached for more detail). User is not sure whether file is eventually uploaded correctly and what to do to solve the error problem.

Uploading [###-----------------]17.01% 920.0MB/5.3GB PEC_ASD_Yale-UCSF_CBC_Epigenomics_Input_HiSeq2000_HSB126.fastq HTTPSConnectionPool(host='s3.amazonaws.com', port=443): Max retries exceeded with url: /proddata.sagebase.org/3324352/d1080939-ad12-4aa2-bedf-11f137e02686/PEC_ASD_Yale-UCSF_CBC_Epigenomics_Input_HiSeq2000_HSB126.fastq/81?AWSAccessKeyId=AKIAIV5XCDRXPWB67YRQ&Expires=1458316175&Signature=YUm%2Ftnctmb6cAFfOKv19DOqcJCE%3D (Caused by <class 'socket.error'>: [Errno 104] Connection reset by peer)Encountered an exception: <class 'requests.exceptions.ConnectionError'>. Retrying...

Environment

None

Activity

Show:
Chris Bare
March 18, 2016, 5:46 PM

Thanks for the report. From the output attached, it looks like the client was getting errors from S3, retrying, and succeeding.

I agree that it's not good to show the end user a bunch of scary error messages. Implementing logging (SYNPY-231) will help by capturing this kind of output and only showing errors when we've given up retrying.

Kristen Dang
March 18, 2016, 5:50 PM

Great, thanks. I will message back to the user that the uploads are finishing correctly, and there is nothing they need to do about the error messages since they are from S3.

Kenneth Daily
October 4, 2016, 6:41 PM

Confirmed, closing.

Assignee

Larsson Omberg

Reporter

Kristen Dang

Labels

None

Validator

Kenneth Daily

Development Area

None

Release Version History

None

Components

Fix versions

Affects versions

Priority

Major
Configure