Cyberduck Mountain Duck CLI

#4288 closed defect (thirdparty)

upload finishes then reuploads again

Reported by: shreddogz@… Owned by: dkocher
Priority: high Milestone:
Component: core Version: 3.4.1
Severity: normal Keywords: upload, restart, large files
Cc: Architecture:
Platform: Mac OS X 10.6


I have a problem where i upload bigger files (typically 200mb+) and when it gets to the end of the file it will do one of three things:

  1. finish normally, happens about 10% of the time
  1. gives an error message about:
      I/O Error: Upload failed
      Read timed out.
      Toggle Transcript:
      TYPE I
      200 TYPE is now 8-bit binary
      227 Entering Passive Mode (74,52,68,98,185,96)
      STOR [filename]
      150 Accepted data connection
  1. gives the error message and automatically restarts uploading from the beginning

sometimes the error message from 2 will just stay up until i click cancel but it will show that the file is the same size as the one i uploaded so i think it completed well, sometimes the message will go away (if i leave it on but dont do anything for a while) and it will show the file has uploaded successfully.

log drawer shows nothing.

i have only had this problems since snow leopard has been around but before that uploaded large files and have never had a problem. the type of files ive been uploading have been iso, dmg, cdr, zip, etc.

Cyberduck: 3.4.1 (5780)/5780
Mac OS X: 10.6.2

if this ticket is already existent somewhere else, please feel free to delete or close it and point it to the other one. also, feel free to email me if any additional info is needed.

Change History (2)

comment:1 Changed on Apr 1, 2010 at 4:00:41 PM by dkocher

  • Platform set to Mac OS X 10.6
  • Resolution set to thirdparty
  • Status changed from new to closed

The error message Read timed out says that the response from the server was incomplete after the connection timeout which is set to 30 seconds by default in Preferences → Connection → Timeouts. It seems your connection to the server is unreliable. Try to increase the timeout and/or try to identify the culprit of the latency.

comment:2 Changed on Apr 1, 2010 at 4:01:58 PM by dkocher

Also refer to Common Problems?.

Note: See TracTickets for help on using tickets.
swiss made software