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

Upload is not working #7543

Closed
cyberduck opened this issue Nov 3, 2013 · 16 comments
Closed

Upload is not working #7543

cyberduck opened this issue Nov 3, 2013 · 16 comments
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Nov 3, 2013

54a7c85 created the issue

After the last update to CyberDuck I am unable to upload any files to my server by any means, including drop and drag, copy and paste, and using the upload feature in the program. This must be fixed ASAP. In addition, following the latest update I must constantly refresh to find the files again as they don't show up without refreshing. I've made no changes to my settings or my computer - the problem is in your latest update.


Attachments

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 4, 2013

@dkocher commented

Please attach the logging information found in the cyberduck.log file in the AppData directory.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 4, 2013

54a7c85 commented

Here is what i think you are asking for:

2013-10-24 09:31:28,653 [background-3] FATAL ch.cyberduck.core.ProtocolFactory - Unknown protocol with identifier gd
2013-10-24 10:44:49,032 [background-3] FATAL ch.cyberduck.core.ProtocolFactory - Unknown protocol with identifier gd
2013-10-24 14:00:59,018 [background-3] FATAL ch.cyberduck.core.ProtocolFactory - Unknown protocol with identifier gd
2013-10-24 20:09:25,365 [background-3] FATAL ch.cyberduck.core.ProtocolFactory - Unknown protocol with identifier gd
2013-10-25 17:56:15,833 [background-3] FATAL ch.cyberduck.core.ProtocolFactory - Unknown protocol with identifier gd
2013-10-31 12:26:44,460 [background-3] FATAL ch.cyberduck.core.ProtocolFactory - Unknown protocol with identifier gd
2013-10-31 12:29:16,736 [background-8] ERROR ch.cyberduck.core.ftp.FTPSession - Error closing connection: FTP response 421 received.  Server closed connection.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 5, 2013

@ylangisc commented

Is there any error message displayed or does it just fails silently? Can you please test with the latest snapshot build available and report back?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 5, 2013

54a7c85 commented

I updated with the latest snapshot build and the problem is not resolved. I can delete files from the server, but not upload. There is no error message. The upload screen shows the upload is complete, but 0 B of 0 B is shown as being uploaded (meaning nothing got uploaded). This problem started on Nov. 2. I was able to upload successfully on Oct. 19th.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 7, 2013

@dkocher commented

Upgrade to the latest snapshot build and post the transcript from the log drawer (⌘-L) if still an issue.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 7, 2013

54a7c85 commented

The update did not change anything. It still shows the upload screen and says the upload was successful but 0 of 0 files were transferred. For some reason, it is not logging this latest attempt. Here's the last entry from the log-in file from 11-5:
2013-11-05 10:13:18,120 [Thread-0] ERROR ch.cyberduck.ui.AbstractController - Exception running cleanup task null
java.lang.NullPointerException
at cli.Ch.Cyberduck.Core.Utils.ConvertFromJavaMap(Unknown Source)
at cli.Ch.Cyberduck.Ui.Controller.TransferPromptModel$FilterAction$InnerTransferPromptFilterWorker.cleanup(Unknown Source)
at ch.cyberduck.ui.threading.WorkerBackgroundAction.cleanup(WorkerBackgroundAction.java:51)
at ch.cyberduck.ui.AbstractController$BackgroundCallable$1.run(AbstractController.java:181)
at cli.System.Delegate.DynamicInvokeImpl(Unknown Source)
at cli.System.Windows.Forms.Control.InvokeMarshaledCallbackDo(Unknown Source)
at cli.System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Unknown Source)
at cli.System.Threading.ExecutionContext.runTryCode(Unknown Source)
at cli.System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(Unknown Source)
at cli.System.Threading.ExecutionContext.RunInternal(Unknown Source)
at cli.System.Threading.ExecutionContext.Run(Unknown Source)
at cli.System.Threading.ExecutionContext.Run(Unknown Source)
at cli.System.Windows.Forms.Control.InvokeMarshaledCallback(Unknown Source)
at cli.System.Windows.Forms.Control.InvokeMarshaledCallbacks(Unknown Source)
at cli.System.Windows.Forms.Control.WndProc(Unknown Source)
at cli.System.Windows.Forms.ScrollableControl.WndProc(Unknown Source)
at cli.System.Windows.Forms.Form.WndProc(Unknown Source)
at cli.System.Windows.Forms.Control$ControlNativeWindow.OnMessage(Unknown Source)
at cli.System.Windows.Forms.Control$ControlNativeWindow.WndProc(Unknown Source)
at cli.System.Windows.Forms.NativeWindow.Callback(Unknown Source)
at cli.System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(Unknown Source)
at cli.System.Windows.Forms.Application$ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Unknown Source)
at cli.System.Windows.Forms.Application$ThreadContext.RunMessageLoopInner(Unknown Source)
at cli.System.Windows.Forms.Application$ThreadContext.RunMessageLoop(Unknown Source)
at cli.System.Windows.Forms.Application.RunDialog(Unknown Source)
at cli.System.Windows.Forms.Form.ShowDialog(Unknown Source)
at cli.Ch.Cyberduck.Ui.Winforms.BaseForm.ShowDialog(Unknown Source)
at cli.Ch.Cyberduck.Ui.Controller.TransferPromptController.b__3(Unknown Source)
at cli.Ch.Cyberduck.Ui.Controller.Threading.SimpleDefaultMainAction.run(Unknown Source)
at cli.System.Delegate.DynamicInvokeImpl(Unknown Source)
at cli.System.Windows.Forms.Control.InvokeMarshaledCallbackDo(Unknown Source)
at cli.System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Unknown Source)
at cli.System.Threading.ExecutionContext.runTryCode(Unknown Source)
at cli.System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(Unknown Source)
at cli.System.Threading.ExecutionContext.RunInternal(Unknown Source)
at cli.System.Threading.ExecutionContext.Run(Unknown Source)
at cli.System.Threading.ExecutionContext.Run(Unknown Source)
at cli.System.Windows.Forms.Control.InvokeMarshaledCallback(Unknown Source)
at cli.System.Windows.Forms.Control.InvokeMarshaledCallbacks(Unknown Source)
at cli.System.Windows.Forms.Control.WndProc(Unknown Source)
at cli.System.Windows.Forms.ScrollableControl.WndProc(Unknown Source)
at cli.System.Windows.Forms.Form.WndProc(Unknown Source)
at cli.System.Windows.Forms.Control$ControlNativeWindow.OnMessage(Unknown Source)
at cli.System.Windows.Forms.Control$ControlNativeWindow.WndProc(Unknown Source)
at cli.System.Windows.Forms.NativeWindow.Callback(Unknown Source)
at cli.System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(Unknown Source)
at cli.System.Windows.Forms.Application$ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Unknown Source)
at cli.System.Windows.Forms.Application$ThreadContext.RunMessageLoopInner(Unknown Source)
at cli.System.Windows.Forms.Application$ThreadContext.RunMessageLoop(Unknown Source)
at cli.Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun(Unknown Source)
at cli.Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel(Unknown Source)
at cli.Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(Unknown Source)
at cli.Ch.Cyberduck.Ui.Controller.MainController.Run(Unknown Source)
at cli.Ch.Cyberduck.Ui.Controller.MainController.Run(Unknown Source)
at cli.Ch.Cyberduck.Ui.Controller.MainController.Main(Unknown Source)

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2013

0fc9061 commented

As a reference, I am also seeing this behavior. I opened Ticket #7522 re: WinSSHD, so I downloaded the latest snapshot to test the fix.

When I upload a file, it appears to complete successfully after uploading 0 bytes. I enabled debugging and have attached the log.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2013

@dkocher commented

Can you please try snapshot build 13924 and attach the debug log again.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2013

0fc9061 commented

Attached. I also attempted to download a file, and it seems like I get the same behavior. Completed with 0 bytes.

The log should show me opening cyberduck, attempting to upload 2 files, then attempting to download 1 file, then closing cyberduck.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2013

@dkocher commented

The bug was introduced in d383d88.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2013

@dkocher commented

#7578 closed as duplicate.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2013

@dkocher commented

In 901fee3.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2013

@ylangisc commented

And in f532310.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2013

@dkocher commented

Please update to the latest snapshot build available.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2013

0fc9061 commented

Looks like uploads and downloads are working properly in Snapshot build 13933. Thanks!

@cyberduck
Copy link
Collaborator Author

cyberduck commented Nov 8, 2013

54a7c85 commented

I updated to f532310 and there is no change. I still cannot upload. The upload screen comes up and shows a successful upload, but still 0 of 0 files (none are actually uploaded).

@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.
Projects
None yet
Development

No branches or pull requests

2 participants