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
I/O Error with multipart uploads #6391
Comments
In general it should help to increase the connection timeout in Preferences → Connection if there are I/O errors such as |
Hi! Default settings is 30 sec. I change to 60 sec (max) to this settings, but nothing change. My net speed is not bad, 20/10Mbit. I see not alwasy failed these sample uploads, but very often. Test: Kill Cyberduck instances from taskmanager, and delete all uncompleted multipart upload with S3 browser, after: Upload these samples in four times, -settings:* timeout for opening connection 60sec (max). Retry failed networking task is unchecked (default) After error, I see in S3 browser tools/uncompleted multipart uploads, and found, file is "TestFile_100MB-02.dat" and broken is 3 parts. This feature not bad, this is new feature request? :) |
Tested on 9333, result is same: upload failed, socket closed. |
Tested on 9352, result is same: upload failed, socket closed. I think this is very important error. |
Tested on 9359. Preferences/Connection/Timeout is default (30 sec). I see this version works better than olders, I repeat this upload 10 times (start cyberduck, upload sample files, close cyberduck). Results: 8 times: OK. I repeat this test later... ps.: I get crashed often, if after upload is finished, I click transfer window/clean up button (default this button is invisible). |
Due to such issues we use multipart uploads as of 5GB only now. |
Hi!
Upload two (test) files cause error. Files: see attached files.
Log:
Tested on 9319, 9320
Attachments
testfiles_100MB.7z
(29.2 KiB)The text was updated successfully, but these errors were encountered: