Skip to content
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

permission problem results in timed out error upload failed #5520

Closed
cyberduck opened this issue Dec 7, 2010 · 2 comments
Closed

permission problem results in timed out error upload failed #5520

cyberduck opened this issue Dec 7, 2010 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Dec 7, 2010

113d2cc created the issue

Recently updated to 3.8.1
After update to 3.8 probably, this error started.
Cyberduck connects fine, transfer window opens, and the message, "prepare "filename.ext" and hangs for about a minute. It then says it is retrying, and displays in transfer window the message "getting size "filename.ext". After about a minute of that, cyberduck disconnects with the error message upload failed, read timed out.

Have repaired permissions a number of times, no change.

Running cyberduck 3.8.1 on OSX 10.6.5

Cyberduck 2.8 on 10.5.8 on another mac on the same network works fine uploading same files.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 9, 2010

@dkocher commented

Can you paste the transcript from the log drawer of the Transfer window.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Dec 10, 2010

@dkocher commented

Please reopen this issue if you have the transcript available and any related output from system.log in Applications/Utilities/Console.app.

Loading

@cyberduck cyberduck closed this Dec 10, 2010
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant