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

duck CLI problem #10588

cyberduck opened this issue Jan 25, 2019 · 0 comments

duck CLI problem #10588

cyberduck opened this issue Jan 25, 2019 · 0 comments


Copy link

@cyberduck cyberduck commented Jan 25, 2019

ef2996d created the issue


Something odd happened this morning using the following duck CLI, [Cyberduck v6.9.0 (29768)].

duck -q -P -e rename --upload wasabisys://T5ZHIOV9VGMNBAKU1HQ4@Blaise-Backup/Magni/ Z:/Backup-Staging/Magni/20190121-Magni-Daily_20190125014500.nbd

After the command was complete CyberDuck lists the directory as shown in CyberduckListing,jpg

The file copied is seen both in the specified destination folder (Blaise-Backup/Magni) and that folder’s parent folder (Blaise-Backup) – and both are grayed out. Note that the grayed file entries do not show a size.

While the copy was proceeding (5 GiB, took about 13 minutes), the file appeared grayed out in the parent folder. I assumed that it was grayed because the file was in the process of copying. I expected that when the copy was complete, the entry in the parent folder would be gone, and the entry in the target folder (Magni) would be present but not grayed out.

Apparently, this file successfully copied to the cloud. If I try to download either entry, I get the message shown in CantDownload.jpg

Refreshing Cyberduck doesn’t help, nor does closing and reopening Cyberduck.

After closing and reopening Cyberduck a second time, I can’t connect to Wasabi (CantConnect.jpg)

-OK, just saw that Wasabi servers are down!* Well that explains at least some of the above …

I guess the duel grayed files could be caused by a service interruption during the copy. I guess we’ll see.

One other thing … CyberDuck was recently udpated. I did not think to also update the duck CLI. Could that be a problem? (installing duck update now…)


Mark Bax


@cyberduck cyberduck closed this Feb 14, 2019
@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.
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant