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

Transfer do not complete for larger files (1GB) #5713

Closed
cyberduck opened this issue Feb 20, 2011 · 24 comments
Closed

Transfer do not complete for larger files (1GB) #5713

cyberduck opened this issue Feb 20, 2011 · 24 comments
Assignees
Labels
bug fixed ftp-tls
Milestone

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Feb 20, 2011

69459ad created the issue

Hi -

I commonly transfer 1GB+ files from my FTP server to my home computer using cyberduck. Recently I have changed to TLS and it seems that most of the transfer stopped (without error on the transfer window) and i cannot even resumed it. The transfer usually stopped at ~700ishh MB mark for the file.

What's even stranger is that if I transfer the file again (not using resume)... it will start again and goes to completion.

For smaller 300-400MB files, they are OK. I am at a lost as to what supporting logs to give you. I would love some guidance on what additional information you need.

This has been causing alot of issues since I don't know the file is not completed ... and I have deleted the original on the server. This have lead to a few lost files. Looking forward to your investigation of the problem.


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 20, 2011

69459ad commented

1/ I have added a screen shot of the file size on the server, the file transfer window indicate the file have completed and the actual size on disk.

2/The FTP server is running ProFTPD 1.3.3a Server

Please tell me what additional information that you need.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 20, 2011

@dkocher commented

Things to try:

  • Update to the latest ProFTPd release. Currently 1.3.3d.
  • Update to the latest snapshot build of Cyberduck which has a new FTP implementation.
  • Post the transcript from the log drawer of the Transfers window.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 22, 2011

@dkocher commented

Please reopen if still an issue after following the steps above.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 22, 2011

69459ad commented

I will update with the log drawer in the next day or so. There are no large files to transfer for the last day or so.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 23, 2011

69459ad commented

I have uploaded the transcript from the log drawer. These are the sections of the log where most of the files transferred is failed in the described way... actually, might be all of them.

The exception is the transfer of Kuroshitsuji which is a restart which the original transfer prematurely terminated.

another point of note is that all of these transfer pretty much start at the same time.

I have also attached the screen shot of my preference setting. network error retry is set to 9 times

Thanks.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 27, 2011

69459ad commented

Hi - I also notice that this problem occurs more often when I have 8-9 files transferring concurrently. If I do 1 or 2 at a time, it happens much less often. Don't know if this helps.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 4, 2011

69459ad commented

hi - any thoughts on this problem? it is still consistently happening please see if I can provide more information. thanks.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 13, 2011

@dkocher commented

Can you find any related output in the system.log (/Applications/Utilities/Console.app)? Also, please update to the latest 4.0 release available.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 15, 2011

69459ad commented

I have been using 4.0.1 still with the same problem but less frequent, I will try with 4.0.2, but where can I download it? thanks.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 16, 2011

69459ad commented

Replying to [comment:10 dkocher]:

Can you find any related output in the system.log (/Applications/Utilities/Console.app)? Also, please update to the latest 4.0 release available.

some error in the system.log. I have clear the log file last night with weekly cron. only have today's log. This is on v4.0.1

Error 1 : `There are numerous errors like this one


Mar 16 22:39:15 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 2011-03-16 22:39:15,658 [background-92] ERROR ch.cyberduck.ui.cocoa.model.FinderLocal - No such file:/Volumes/usbshare1/seedbox/fileABC 2011.03.06/fileABC 2011.03.06.wmv

Error 2: Only one instance in the last 24 hrs.

Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 2011-03-16 22:24:07,129 [main] ERROR org.rococoa.callback - Exception calling method for selector clearButtonClicked:
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: java.lang.reflect.InvocationTargetException
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at java.lang.reflect.Method.invoke(Method.java:597)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.OCInvocationCallbacks.callMethod(OCInvocationCallbacks.java:155)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.OCInvocationCallbacks.access$200(OCInvocationCallbacks.java:52)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.OCInvocationCallbacks$2.callback(OCInvocationCallbacks.java:82)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at java.lang.reflect.Method.invoke(Method.java:597)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.CallbackReference$DefaultCallbackProxy.invokeCallback(CallbackReference.java:384)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.CallbackReference$DefaultCallbackProxy.callback(CallbackReference.java:414)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.Function.invokeVoid(Native Method)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.Function.invoke(Function.java:328)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.Function.invoke(Function.java:276)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.MsgSendHandler.invoke(MsgSendHandler.java:111)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.Library$Handler.invoke(Library.java:214)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at $Proxy0.syntheticSendMessage(Unknown Source)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.Foundation.send(Foundation.java:200)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.Foundation.send(Foundation.java:187)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.ObjCObjectInvocationHandler.sendOnThisOrMainThread(ObjCObjectInvocationHandler.java:254)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.ObjCObjectInvocationHandler.invokeCocoa(ObjCObjectInvocationHandler.java:222)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.ObjCObjectInvocationHandler.intercept(ObjCObjectInvocationHandler.java:185)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at ch.cyberduck.ui.cocoa.application.NSApplication$$ByRococoa.run(<generated>)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at ch.cyberduck.ui.cocoa.MainApplication.main(MainApplication.java:119)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at java.lang.reflect.Method.invoke(Method.java:597)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at apple.launcher.LaunchRunner.run(LaunchRunner.java:116)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at apple.launcher.LaunchRunner.callMain(LaunchRunner.java:51)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at apple.launcher.JavaApplicationLauncher.launch(JavaApplicationLauncher.java:52)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: Caused by: java.util.ConcurrentModificationException
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at java.util.AbstractList$Itr.next(AbstractList.java:343)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at ch.cyberduck.ui.cocoa.TransferController.clearButtonClicked(TransferController.java:1031)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	... 32 more
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: JNA: Callback org.rococoa.internal.OCInvocationCallbacks$2@14323d5 threw the following exception:
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: org.rococoa.RococoaException: Exception calling method for selector clearButtonClicked:
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.OCInvocationCallbacks.callMethod(OCInvocationCallbacks.java:159)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.OCInvocationCallbacks.access$200(OCInvocationCallbacks.java:52)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.OCInvocationCallbacks$2.callback(OCInvocationCallbacks.java:82)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at java.lang.reflect.Method.invoke(Method.java:597)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.CallbackReference$DefaultCallbackProxy.invokeCallback(CallbackReference.java:384)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.CallbackReference$DefaultCallbackProxy.callback(CallbackReference.java:414)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.Function.invokeVoid(Native Method)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.Function.invoke(Function.java:328)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.Function.invoke(Function.java:276)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.MsgSendHandler.invoke(MsgSendHandler.java:111)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at com.sun.jna.Library$Handler.invoke(Library.java:214)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at $Proxy0.syntheticSendMessage(Unknown Source)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.Foundation.send(Foundation.java:200)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.Foundation.send(Foundation.java:187)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.ObjCObjectInvocationHandler.sendOnThisOrMainThread(ObjCObjectInvocationHandler.java:254)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.ObjCObjectInvocationHandler.invokeCocoa(ObjCObjectInvocationHandler.java:222)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.ObjCObjectInvocationHandler.intercept(ObjCObjectInvocationHandler.java:185)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at ch.cyberduck.ui.cocoa.application.NSApplication$$ByRococoa.run(<generated>)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at ch.cyberduck.ui.cocoa.MainApplication.main(MainApplication.java:119)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at java.lang.reflect.Method.invoke(Method.java:597)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at apple.launcher.LaunchRunner.run(LaunchRunner.java:116)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at apple.launcher.LaunchRunner.callMain(LaunchRunner.java:51)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at apple.launcher.JavaApplicationLauncher.launch(JavaApplicationLauncher.java:52)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: Caused by: java.util.ConcurrentModificationException
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at java.util.AbstractList$Itr.next(AbstractList.java:343)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at ch.cyberduck.ui.cocoa.TransferController.clearButtonClicked(TransferController.java:1031)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at java.lang.reflect.Method.invoke(Method.java:597)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	at org.rococoa.internal.OCInvocationCallbacks.callMethod(OCInvocationCallbacks.java:155)
Mar 16 22:24:07 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 	... 27 more

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 17, 2011

@dkocher commented

Replying to [comment:14 lee.norman@…]:

Error 1 : `There are numerous errors like this one


Mar 16 22:39:15 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 2011-03-16 22:39:15,658 [background-92] ERROR ch.cyberduck.ui.cocoa.model.FinderLocal - No such file:/Volumes/usbshare1/seedbox/fileABC 2011.03.06/fileABC 2011.03.06.wmv

Have you removed this USB volume while a transfer was in progress?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 17, 2011

69459ad commented

no I have not. The transfer occurs in the middle of the night and all devices are up for the duration. Thanks for keep trying.

Replying to [comment:15 dkocher]:

Replying to [comment:14 lee.norman@…]:

Error 1 : `There are numerous errors like this one


Mar 16 22:39:15 normans-macbook-pro-15 [0x0-0x23023].ch.sudo.cyberduck[287]: 2011-03-16 22:39:15,658 [background-92] ERROR ch.cyberduck.ui.cocoa.model.FinderLocal - No such file:/Volumes/usbshare1/seedbox/fileABC 2011.03.06/fileABC 2011.03.06.wmv

Have you removed this USB volume while a transfer was in progress?

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 19, 2011

@dkocher commented

Try download to another harddisk and replicate the issue.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 20, 2011

69459ad commented

I have also notice this morning that there are quite a few illegal port command dialogue box pop-ed up and I hit retry. But the transfer did not resume after. I have attached the related transcript from log draw last night. illegalPortCmd.txt for your review. Thanks.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 20, 2011

69459ad commented

Replying to [comment:18 dkocher]:

Try download to another harddisk and replicate the issue.
OK. Will do this over the next 24 hrs and report back.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 20, 2011

69459ad commented

Replying to [comment:20 lee.norman@…]:

Replying to [comment:18 dkocher]:

Try download to another harddisk and replicate the issue.
OK. Will do this over the next 24 hrs and report back.

I have tried download to another drive (boot drive) this time and the transfer still not complete and I got illegal port command error as well. Thanks.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 22, 2011

@dkocher commented

Fixed in a24f425.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 27, 2011

69459ad commented

after upgrading to 4.0.2, when I want to start another download, I got illegal port command... same thing if i tried to resume a previous download. I cannot even start a transfer any more. bummer. I will try a few more things and report back.

uploaded the log draw in "illegal port.txt" for your reference

hope you see something.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 28, 2011

69459ad commented

Replying to [comment:23 lee.norman@…]:

after upgrading to 4.0.2, when I want to start another download, I got illegal port command... same thing if i tried to resume a previous download. I cannot even start a transfer any more. bummer. I will try a few more things and report back.

uploaded the log draw in "illegal port.txt" for your reference

hope you see something.

This sort of looking like a separate problem. Open another docket. Cannot confirm if the problem of this ticket is fixed since I cannot even make a transfer happen. Keep this ticket open please. Thanks.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 29, 2011

@dkocher commented

Replying to [comment:23 lee.norman@…]:

after upgrading to 4.0.2, when I want to start another download, I got illegal port command... same thing if i tried to resume a previous download. I cannot even start a transfer any more. bummer. I will try a few more things and report back.

uploaded the log draw in "illegal port.txt" for your reference

hope you see something.

Switch to passive (PASV) connect mode.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 3, 2011

69459ad commented

after setting to PASV connect mode and using 4.0.2, transferring of files still stop prematurely when using SFTP transfer. Reopen the ticket. Thank for having a look again.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 12, 2011

Wstsandmore commented

I made a very interesting observation, which could help you programmers probably a lot :

After uploading a file the Cyberduck File Browser (at least in Macinsosh ) does reload.
First I thought that this is a convenient feature to show the user the updated state,
but I now realized that Cyberduck also seems to depend on the new recalculated filesize,
because if I upload a large file into a subfolder where a reload of the filemanager does not show the new filesize, and then move the entire folder straight away to another location (as I often do with large files in order to prevent people from downloading partially uploaded stuff ),
the filesize in that moved folder keeps being zero, because it was never updated by Cyberduck to be larger now.

This also creates really strange problems when uploading multiple folders including large files:
The first uploaded files are not registered as uploaded because a refresh of the filebrowser and therewith filecalculation was not made, so if the connection is reset once daily by the ISP, Cyberduck reloads the multiple task, but does not see the files already uploaded and starts them again from the beginning.
The only way to prevent this is to open the folder of the file currently uploaded so that it refreshes on completion. But this only works on single folder uploads, because multiple tasks only refresh at the very end.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 4, 2011

@dkocher commented

Replying to [comment:27 Wstsandmore]:

I made a very interesting observation, which could help you programmers probably a lot :

After uploading a file the Cyberduck File Browser (at least in Macinsosh ) does reload.
First I thought that this is a convenient feature to show the user the updated state,
but I now realized that Cyberduck also seems to depend on the new recalculated filesize,
because if I upload a large file into a subfolder where a reload of the filemanager does not show the new filesize, and then move the entire folder straight away to another location (as I often do with large files in order to prevent people from downloading partially uploaded stuff ),
the filesize in that moved folder keeps being zero, because it was never updated by Cyberduck to be larger now.

This also creates really strange problems when uploading multiple folders including large files:
The first uploaded files are not registered as uploaded because a refresh of the filebrowser and therewith filecalculation was not made, so if the connection is reset once daily by the ISP, Cyberduck reloads the multiple task, but does not see the files already uploaded and starts them again from the beginning.
The only way to prevent this is to open the folder of the file currently uploaded so that it refreshes on completion. But this only works on single folder uploads, because multiple tasks only refresh at the very end.

I do not understand the issue. The refresh in the browser window is just to show uploaded files.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jul 4, 2011

@dkocher commented

Replying to [comment:26 lee.norman@…]:

after setting to PASV connect mode and using 4.0.2, transferring of files still stop prematurely when using SFTP transfer. Reopen the ticket. Thank for having a look again.

I cannot replicate any more issues. Post the transcript with the problem to a new ticket reporting against 4.1.

@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 fixed ftp-tls
Projects
None yet
Development

No branches or pull requests

2 participants