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

File shows Upload Complete, but does not arrive #3306

Closed
cyberduck opened this issue Jul 9, 2009 · 1 comment
Closed

File shows Upload Complete, but does not arrive #3306

cyberduck opened this issue Jul 9, 2009 · 1 comment
Assignees
Labels
bug core thirdparty Issue caused by third party

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Jul 9, 2009

b2a1857 created the issue

FTP file did not arrive but does show:
Upload Complete
13.9 KB of 13.9 KB
Thursday, July 9, 2009 11:01:36 AM US/Central

Log:

220 Ready for user
USER sxmh9001
331 Need password.
PASS ********
230 sxmh9001 logged in, proceed
FEAT
500 Unrecognized command
NOOP
200 Command okay.
CWD /send
250 CWD command successful.
STAT /send
211 BCHSEP = NONE
PASV
227 Entering Passive Mode. (209,95,232,130,40,77)
LIST -a
125 Data connection already open; transfer starting.
226 Transfer complete.
PASV
227 Entering Passive Mode. (209,95,232,130,40,78)
LIST
125 Data connection already open; transfer starting.
drw-rw-rw-   2  sxmh9001 users        1024 Jul  9 16:01 commit
226 Transfer complete.
PASV
227 Entering Passive Mode. (209,95,232,130,40,79)
STOR InventoryExport-CyberDuckTest.txt
125 Data connection already open; transfer starting.
226 Transfer complete.
SITE CHMOD 644 InventoryExport-CyberDuckTest.txt
501 Command argument syntax error: CHMOD 644 InventoryExport-CyberDuckTest.txt
SITE UTIME InventoryExport-CyberDuckTest.txt 20090709155132 20090709155132 20090709155132 UTC
501 Command argument syntax error: UTIME InventoryExport-CyberDuckTest.txt 20090709155132 20090709155132 20090709155132 UTC
QUIT
221 Closing control connection.
@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 6, 2009

@dkocher commented

Looks all correct.

@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.
Labels
bug core thirdparty Issue caused by third party
Projects
None yet
Development

No branches or pull requests

2 participants