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
Read timed out failure for large file upload #10834
Comments
|
The log indicates that Upload with temporary filename is enabled. |
I cannot seem to reproduce the issue
|
Please post the transcript from the log drawer of the Transfers window. Choose ⌘-L on Mac or right-click the toolbar from the Transfers window and choose Log on Windows. |
Updated to latest 7.1.2, still happens.
|
Replying to [comment:4 dkocher]:
dkocher, as stated, the issue is with large files. Please try with uploads >2GB, not a PNG. |
I enabled debugging defaults write ~/Library/Preferences/ch.sudo.cyberduck.plist logging debug The debug log is chock full of pretty-private data - client folders, files, usernames, anything transferred that's in the history... basically everything except passwords. Not great at all for sharing online. But I was able to scrub things though, and attached. The test file name is "Complete performance.mp4".
This would seem to suggest that the issue is not about file size, but lengthy transfers, that get identified as failed & timed out even though they didn't and were successful. If I'm not mistaken, I canceled the operation at 18:58:36. |
Please check the server logs for any reason why it stops responding. |
This one has me astonished... Steps to reproduce:
My guess is that the threshold is 2GB: I uploaded a 1.1GB file that did not exhibit that behavior, followed by a 3.2GB file that did.
I have experienced this behavior in two different systems working with different files and different FTP servers.
Same behavior.
This has been reproducible, happens every time to me.
Tried with "upload with temporary filename" both enabled and disabled - same behavior.
"Always overwrite when reloading" has always been disabled, and "Existing files" is set to "Prompt".
Only workaround I found is... to use FileZilla. It doesn't exhibit this problem at all, with the same files and FTP server.
Needless to say, this is pretty insane/maddening. But I've been loyal to Cyberduck for years and am willing to help troubleshooting this.
Log attached as file.
Attachments
Cyberduck debug log 20191108.txt
(806.4 KiB)Cyberduck_log_10834.txt
(5.4 KiB)The text was updated successfully, but these errors were encountered: