Cyberduck Can't Find Local File? #16076
Replies: 31 comments 2 replies
-
I have the latest FLAC.EXE 64-bit command-line installed on my Windows 11 computer. I just used the test command line parm against the file in question on my D: drive: Below are the results: This is Cyberduck 64-bit version 8.9.0 (41543). |
Beta Was this translation helpful? Give feedback.
-
Incidentally, the reason that I am performing this upload with Cyberduck is that my Mountain Duck is foobar and will not complete correctly. My plan is to perform the entire 1.2 TiB upload using Cyberduck, completely uninstall both Cyberduck and Mountain Duck deleting all cached files, and lastly re-install both again for a fresh start. I will then use Mountain Duck to sync the complete upload done by Cyberduck. My plan is to have a locally cached sync to play content from my Windows 11 computer. |
Beta Was this translation helpful? Give feedback.
-
Regarding the "File not Found" error: Sidenote: If you want to share the log file here, make sure to attach it through the GitHub web interface, as it wouldn't be visible to us otherwise. Regarding your use case: |
Beta Was this translation helpful? Give feedback.
-
Thank you for emailing.
The issue I faced with CyberDuck upload was on an SFTP server from a
service provider a discontinued service with. I was able to reproduce
the issue quickly, but after canceling service I would not be able to.
The service provider was IONOS.
I am getting a new SFTP server that I am working to order now. It
should be available shortly, and I will attempt to reproduce the issue
on the new SFTP server once it is ready.
Regarding the Mountain Duck offline functionality note you added, my
plan was to completely upload all data via Cyberduck to the SFTP server.
Once that is done, I will use Mountain Duck to then download everything
for offline mode to be kept in sync. I would not refer to the
obfuscated data later and will have no need to. As long as the sync
works properly, I will work directly with the mapped drive only. This
should work...unless it doesn't later. I would post about future issues
if faced later.
…------ Original Message ------
From "Laura" ***@***.***>
To "iterate-ch/cyberduck" ***@***.***>
Cc "WhatImListnTo" ***@***.***>; "Author"
***@***.***>
Date 7/5/2024 7:30:03 AM
Subject Re: [iterate-ch/cyberduck] Cyberduck Can't Find Local File?
(Discussion #16076)
Regarding the "File not Found" error:
Can you please enable debug logging
<https://docs.cyberduck.io/cyberduck/support/#debug-logging-level>,
recreate the error message, and send us the log file afterward? If you
don't like to see sensitive data to be shared publicly, please send the
log file with the ticket reference GH-16076
<#16076> to
***@***.***, otherwise attach it here.
Sidenote: If you want to share the log file here, make sure to attach
it through the GitHub web interface, as it wouldn't be visible to us
otherwise.
Regarding your use case:
If you use the offline functionality
<https://docs.cyberduck.io/mountainduck/connect/sync/#keep-offline> of
Mountain Duck, you'll still need the mounted drive to access the files
as the synchronization cache is obfuscated.
—
Reply to this email directly, view it on GitHub
<#16076 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANHTSOX5ZJCFMMUK7E2X3DLZKZ7TXAVCNFSM6AAAAABJ4UNWOWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSNRXGUYTK>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I got my new SFTP server. I attempted what failed previously again, and I got a worse failure this time uploading to new server. I selected the option to send a crash log. I am not sure what went wrong. However, I successfully uploaded 16 files. After this, I successfully selected and uploaded a single selected directory containing a nested directory and several files underneath. After this completes, I will again select a large number of directories with all files under to see what happens |
Beta Was this translation helpful? Give feedback.
-
It looks like the issue is that I am uploading too much at once. The transfer gets canceled with such a large number, and Cyberduck does not recover. I have to close the application, restart it, then select a smaller number of directories. It did not get through the directory creation portion and never started uploading files. |
Beta Was this translation helpful? Give feedback.
-
My logs have been overwritten it appears, and I lost the debug log of the crash I stated earlier. My upload is continuing, and Cyberduck has no issues uploading 229.3GiB content at a time. I will continue increasing the upload size to determine what causes the failure. My current upload will be complete tomorrow. I do have the crash log output, but I am not sure how helpful this will be: `[General Info] Application: Cyberduck User Explanation: User said ""[Exception Info 1] Top-level Exception [Assembly Info] mscorlib, Version=4.0.0.0 [System Info] Operating System Machine ` |
Beta Was this translation helpful? Give feedback.
-
It looks like once you set debug that logs are only kept for five ZIP backups. After five, the new logs replace the older ZIPs after five. |
Beta Was this translation helpful? Give feedback.
-
The issue I am facing appears to be specific to Cyberduck attempting to create all directories prior to upload in both this latest case and the previous one. It seems to be doing this too fast that results in failure. I am wondering if instead you were to create directories if they do not exist just prior to upload as opposed to blast creating all at the beginning. For example, 50 nested directories exist in total with various files all within this directory hierarchy. I select all directories under a parent. Like this: directory_1 This is a small example above. What currently happens is that Cyberduck is mass creating directories: directory_1, sub_drectory_a, sub_drectory_b. Only after this is done are files ever then uploaded. Why not instead work on file_1, and if directory_1 does not exist, create it. If sub_drectory_a does not exist under directory_1, create it. With both directories existing, only then upload file_1. Repeat this same logic for file_2 in which case no directory creation would be necessary. |
Beta Was this translation helpful? Give feedback.
-
My SFTP upload of 229.3GiB just completed successfully. Next I attempted my next largest SFTP upload of 723GiB. This one failed right away after a a new logon: I will email the captured debug log for investigation. Not a single directory was created on the destination after my previous successful SFTP upload pictured above. |
Beta Was this translation helpful? Give feedback.
-
My next several attempts also failed. I am finally getting a successful upload of 77.1GiB right now. This should complete in less than ten hours. |
Beta Was this translation helpful? Give feedback.
-
Also, I had to close Cyberduck followed by re-launching it to start the upload. The job was stuck and would not stop. |
Beta Was this translation helpful? Give feedback.
-
I think the job is failing due to Cyberduck spamming directory creation. |
Beta Was this translation helpful? Give feedback.
-
I just reviewed jorunalctl in its entirety. I see nothing bad related to this activity in the logs of my server. |
Beta Was this translation helpful? Give feedback.
-
I added an option of firewall to my server, so it could be Cyberduck is being mistaken for a DDoS attack. |
Beta Was this translation helpful? Give feedback.
-
I will perform a flac test on the file after it is uploaded to ensure the resume worked correctly. |
Beta Was this translation helpful? Give feedback.
-
This 77.1GiB failure may have been my mistake. I accidentally set the upload path to /sftp instead of /sftp/Music. I noticed this yesterday and started moving complete directories already uploaded from /sftp to /sftp/Music. I moved the entire sub-directory complete with all files and nested sub-directories. I originally thought Cyberduck was working in alphabetic order, but it appears some folders I moved were empty and not yet uploaded. I canceled this upload and started a new upload job to the correct directory overwriting any existing files. It completed the directory creation and is now uploading files. This upload is 262.28GiB: This upload should finish either tomorrow or the day after. |
Beta Was this translation helpful? Give feedback.
-
I see why it is starting at the wrong directory and will correct my bookmark to prevent this from happening again. |
Beta Was this translation helpful? Give feedback.
-
My above upload completed, and I hit another immediate failure. The app is stuck now. No buttons will work: I am emailing the latest log. |
Beta Was this translation helpful? Give feedback.
-
I attempted this yesterday as well as many other things. This did not
help. The uploads continued to fail immediately.
This is a peculiar issue. It started off working with 157 total selections on the first successful upload. I repeated 157 on the next attempt. On the third attempt I got instant failures with no uploads. I had to reduce the selection count from 156 down to 36 to have a successful upload. After 36 completed, I was never able to upload again using Cyberduck.
…------ Original Message ------
From "Laura" ***@***.***>
To "iterate-ch/cyberduck" ***@***.***>
Cc "WhatImListnTo" ***@***.***>; "Author"
***@***.***>
Date 7/9/2024 6:32:26 AM
Subject Re: [iterate-ch/cyberduck] Cyberduck Can't Find Local File?
(Discussion #16076)
Please set the Transfer Files dropdown within the Cyberduck preferences
Transfers tab to Open single connection instead of Open multiple
connections to see if this improves the upload behavior.
—
Reply to this email directly, view it on GitHub
<#16076 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANHTSOSX622XDWAAD3F6SFDZLO33VAVCNFSM6AAAAABJ4UNWOWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TSOJXGA3DG>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Also, the failures are instant now. There is a delay of about one or two seconds then I immediately see failure. I am over 60% my current upload (I still need to get this done). I can try again probably tomorrow using Cyberduck with more logging. |
Beta Was this translation helpful? Give feedback.
-
I did two things -- I ran Windows Update, and I also rebooted my computer. I did not set the preference to use a single connection. However, I do currently have the Connections drop down on the Transfer screen to 1 Connection. I selected the first missing folder from local followed by selecting the absolute last folder. It is uploading now, and when this completes it will be done: Note that I normally do not reboot or power off my computer. It stays on constantly. I wonder if the reboot may have resolved this issue? I do recall seeing posts about memory leaks. |
Beta Was this translation helpful? Give feedback.
-
Bad news -- it just failed. I do not know why it would have failed this time. Everything should have worked perfectly. I will email the latest log. |
Beta Was this translation helpful? Give feedback.
-
I clicked the resume button, and it is now continuing. It appears that the default timeout and retry settings are too low. I increased both of these. Is it also possible to auto-resume a failure after a delay? |
Beta Was this translation helpful? Give feedback.
-
This failed yet again. My expectation was that this completed today, but it failed: I will email captured log again. Also, I will attempt to resume again. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, debug logs spams so much that I have no way of knowing which ZIP file to send. |
Beta Was this translation helpful? Give feedback.
-
I have turned off debug logging considering it has not been useful for any issues I am facing. |
Beta Was this translation helpful? Give feedback.
-
Cyberduck for a small number of file transfers works fine without issue. It is not ideal for large (over 1 TiB) transfers at this point in time. Lots of time gets spent clicking resume over and over, and you will have to reboot your computer when the transfers eventually all fail. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
It looks like the upload finally completed. My shell tree list shows zero files missing. Unfortunately, Cyberduck will not stop uploading. It appears to be re-uploading files that previously completed. I just forced stopped it when re-uploading a completed file. This single file is now corrupt. I will delete then upload this single one and finally be done with this. This 1.15TiB upload took seven days. It would have been shorter if not for all the issues I faced. |
Beta Was this translation helpful? Give feedback.
-
I connected to an SFTP server, navigated to an empty directory on the server then clicked the Upload button. I have over 30,000 directories and files combined that exist on my local D: drive: D:\Media\Digital Audio. I selected all content within that directory to then upload to the SFTP server. Cyberduck started creating all directories. During this directory creation and before any file uploads, I get a strange error:
This file it is claiming that it cannot find is on my local D: drive and is valid. Why would Cyberduck be complaining about a local file referring me to my web hosting service provider? This doesn't make sense.
Beta Was this translation helpful? Give feedback.
All reactions