Transfers keep disconnecting and not resuming

[florianlamberty@…]

After upgrading to the new version, the ftp transfers fail every 3-4 megabyte. The Automatic resume is not kicking in, and I have to click on the resume button every minute to keep it going.

Version: Version 3.0 (3966) Mac Version 10.5.2 build 9C7010

Error is very annoying.

[anonymous]

The VSFTP Log only shows this:

Thu May 15 15:34:36 2008 [pid 14716] CONNECT: Client "192.168.100.200"
Thu May 15 15:34:37 2008 [pid 14715] [upload] OK LOGIN: Client "192.168.100.200"
Thu May 15 15:40:10 2008 [pid 15474] CONNECT: Client "192.168.100.200"
Thu May 15 15:40:11 2008 [pid 15473] [upload] OK LOGIN: Client "192.168.100.200"
Thu May 15 15:41:33 2008 [pid 15488] CONNECT: Client "192.168.100.200"
Thu May 15 15:41:33 2008 [pid 15487] [upload] OK LOGIN: Client "192.168.100.200"
Thu May 15 15:44:40 2008 [pid 15522] CONNECT: Client "192.168.100.200"
Thu May 15 15:44:40 2008 [pid 15521] [upload] OK LOGIN: Client "192.168.100.200"
Thu May 15 15:46:01 2008 [pid 15523] [upload] FAIL DOWNLOAD: Client "192.168.100.200", "/Transfer/SimulationCrash.Avi", 5915950 bytes, 72.17Kbyte/sec

is there a log in the programm?

[dkocher]

What is your setting in Preferences → Connection → Timeout for opening connections?

[florianlamberty@…]

I changed that to 45 seconds, changed it to 60 seconds - but to no success. Filezilla and the other version(s) are working fine with this FTP Server.

[dkocher]

Please post the transcript from View → Log Drawer. Can you find any related output in the console.log (/Applications/Utilities/Console.app)?

Also, is it possible to get an account on this server?

[florianlamberty@…]

Hello!

The Log drawers just shows:

226 Directory send OK.
NOOP
200 NOOP ok.
NOOP
200 NOOP ok.
NOOP
200 NOOP ok.
NOOP
200 NOOP ok.

The transfer gets to 4-5 mb and then it just stops. No retry as far as I can tell. At least not 9 every 20 seconds like I configured.

Access isn´t easily possible - the server is not accessable from the internet. But I´ll have to check if it might be possible.

[florianlamberty@…]

Oh this might be something:

From the console log:

5/16/08 2:41:06 PM [0x0-0xa30a3].ch.sudo.cyberduck[891] 2008-05-16 14:41:06,110 [main] FATAL ch.cyberduck.ui.cocoa.CDMainApplication - Event for unknown runnable:0 

[dkocher]

Please uncheck 'Send 'no operation' command to keep connection alive in Cyberduck → Preferences → Connection until this is fixed.

[dkocher]

In r3984.

[anonymous]

I'd like this feature to be PUT BACK IN Cyberduck please. I'm downgrading and will not update until this feature is back.

Thanks