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

Jump to bottom

Uploading file replaces file with (non-working) link to temp. file #7744

Closed
cyberduck opened this issue Jan 19, 2014 · 10 comments
Closed

Uploading file replaces file with (non-working) link to temp. file #7744

cyberduck opened this issue Jan 19, 2014 · 10 comments
Assignees
@dkocher
Labels
bug sftp SFTP Protocol Implementation thirdparty Issue caused by third party
Milestone
4.4.4

Comments

@cyberduck
Copy link
Collaborator

f9f949d created the issue

Since a few days, I run into a serious problem when using Cyberduck to access an sftp server: when I open a file on a server, edit it locally and then save the file, the file is not uploaded correctly by Cyberduck back to the server. A temporary file is uploaded, but then the original file is replaced with a link to the temporary file - which doesn't work. The same task done with another program works without problems, so I assume it has to do with Cyberduck.
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please update to the latest snapshot build available and post the transcript from the log drawer (⌘-L) of the Transfers window.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

This is possibly fixed in 19f8789.

@cyberduck
Copy link
Collaborator Author

f9f949d commented

I updated to the latest snapshot build (14219), but the problem persists.

I feel that my previous description is a bit misleading. I don't manually download the file, edit the copy on my local machine, and then manually upload again (this works without problems). I double-click on the file in Cyberduck, it opens in my editor (Aquamacs), I edit the file, click on save and it should be automatically uploaded back to the server. This doesn't work correctly, as described above (but only with files in certain folders). Since I do the editing "in-place", there is no log in the Transfers window.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please post the transcript from the log drawer (⌘-L) from the browser window.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:3 tex-pun]:

as described above (but only with files in certain folders).

What is different with these folders from others working?

@cyberduck
Copy link
Collaborator Author

f9f949d commented

Replying to [comment:4 dkocher]:

Please post the transcript from the log drawer (⌘-L) from the browser window.


SSH_FXP_STAT
SSH_FXP_ATTRS
SSH_FXP_STAT
SSH_FXP_ATTRS
SSH_FXP_STAT
SSH_FXP_ATTRS
SSH_FXP_STAT
SSH_FXP_ATTRS
SSH_FXP_STAT
SSH_FXP_ATTRS
SSH_FXP_STAT
SSH_FXP_ATTRS
SSH_FXP_REMOVE
SSH_FXP_STATUS
SSH_FXP_RENAME
SSH_FXP_STATUS
SSH_FXP_SETSTAT
SSH_FXP_STATUS
No such file

@cyberduck
Copy link
Collaborator Author

f9f949d commented

Replying to [comment:5 dkocher]:

Replying to [comment:3 tex-pun]:

as described above (but only with files in certain folders).

What is different with these folders from others working?

The access rights etc. are exactly the same, the only difference I can see at the moment is that the non-working folders are under a different filesystem (FraunhoferFS) than the others (NFS).

@cyberduck
Copy link
Collaborator Author

@dkocher commented

From the transcript it looks like the SSH_FXP_RENAME operation is failing silently on the server as subsequently when requesting the file it fails with SSH_FX_NO_SUCH_FILE.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Set the hidden property editor.upload.temporary to disable the use of temporary name on upload when uploading changes from the editor on save.

defaults write ch.sudo.cyberduck editor.upload.temporary false

@cyberduck
Copy link
Collaborator Author

f9f949d commented

This works like a charm! Thanks!

@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.
Assignees

@dkocher dkocher

Labels
bug sftp SFTP Protocol Implementation thirdparty Issue caused by third party
Projects
None yet
Milestone
4.4.4
Development

No branches or pull requests
2 participants
@dkocher @cyberduck