Cyberduck Mountain Duck CLI

#7474 closed defect (fixed)

Upload Failing & Losing Working File

Reported by: mattgrosswork Owned by: dkocher
Priority: normal Milestone: 4.4
Component: ftp Version: 4.3.1
Severity: normal Keywords:
Cc: Architecture: Intel
Platform: Windows 7

Description (last modified by dkocher)

Hey All, so every now and again (until the last few days, when it started happening several times an hour) Cyberduck gives me an Upload failed message when I save whatever file I'm editing with the message:

200TYPE is now 8-bit binary

NOOP
213 UTIME OK
TYPE I
200Zzz...
PASV 200 TYPE is now 8-bit binary

Hitting try again never works, so I hit cancel, close and reopen cyberduck, and all but the first 50-200 lines of the file I was working on are gone. This pretty much makes cyberduck unusable, but it seems to happen almost entirely on one server that I'm working in. (Using Brackets as my text editor by the way)

Any ideas? Let me know if there's more that I need to upload. It could totally be an issue with my server, but I'm pretty foreign to server management, so I really have no idea.

Transcript:

226-File successfully transferred
226 0.296 seconds (measured here), 193.41 Kbytes per second
NOOP
200 Zzz...
SITE CHMOD 644 /usm/wp-content/themes/usm/style.css
200 Permissions changed on /usm/wp-content/themes/usm/style.css
MFMT 20131004210353 /usm/wp-content/themes/usm/style.css
213 UTIME OK
NOOP
200 Zzz...
TYPE I
200 TYPE is now 8-bit binary
PASV
227 Entering Passive Mode (50,87,134,243,153,134)
STOR /usm/wp-content/themes/usm/style.css
150 Accepted data connection
ABOR
426 Transfer aborted
NOOP
226-Transfer aborted
226 0.043 seconds (measured here), 33.47 Kbytes per second
SITE CHMOD 644 /usm/wp-content/themes/usm/style.css
200 Zzz...
MFMT 20131004210356 /usm/wp-content/themes/usm/style.css
200 Permissions changed on /usm/wp-content/themes/usm/style.css
NOOP
213 UTIME OK
TYPE I
200 Zzz...
PASV
200 TYPE is now 8-bit binary

Apologies for the bad formatting too.

Change History (8)

comment:1 follow-up: Changed on Oct 4, 2013 at 9:13:54 PM by mattgrosswork

This probably isn't the right spot to post this either.

comment:2 in reply to: ↑ 1 Changed on Oct 5, 2013 at 8:26:41 AM by dkocher

  • Milestone set to 4.4

Replying to mattgrosswork:

This probably isn't the right spot to post this either.

That is the right place.

comment:3 Changed on Oct 5, 2013 at 8:27:18 AM by dkocher

  • Description modified (diff)

comment:4 Changed on Oct 5, 2013 at 11:37:46 AM by dkocher

  • Resolution set to fixed
  • Status changed from new to closed

In r13111. Please update to the latest snapshot build available.

comment:5 follow-up: Changed on Oct 5, 2013 at 6:03:00 PM by mattgrosswork

Updating now, should I expect the issue to be fixed, or is this a testing and feedback thing?

Thanks

comment:6 in reply to: ↑ 5 Changed on Oct 5, 2013 at 6:30:57 PM by dkocher

Replying to mattgrosswork:

Updating now, should I expect the issue to be fixed, or is this a testing and feedback thing?

Thanks

It is expected to be fixed.

comment:7 follow-up: Changed on Oct 5, 2013 at 6:35:25 PM by mattgrosswork

Well, it hasn't failed on me so far today. That's a good sign.

Thanks again.

comment:8 in reply to: ↑ 7 Changed on Oct 5, 2013 at 6:56:17 PM by dkocher

Replying to mattgrosswork:

Well, it hasn't failed on me so far today. That's a good sign.

Thanks again.

Thanks for the feedback.

Note: See TracTickets for help on using tickets.