Log / Error messages when failing to upload files

[peter....@gmail.com]

Hi,

I've started using Cyberduck to upload files to Backblaze B2 (generally in batches of ~4/5 GB, of files ~27 MB each), and occasionally, transfers will fail, with "Transfer incomplete" in the status of the transfer item of the transfers window. However, I can't find anything else about what went wrong: OS X Console doesn't show anything, Cyberduck Menu -> View -> Toggle Log Drawer is empty, so is there a way to know exactly what went wrong (even if it's just a error code or something)?

In this situation, the files do seem to be getting uploaded to Backblaze B2 (all the files are there, of the correct size, and with the correct SHA1 checksums matching what's on disk), so it's somewhat of a mystery to me why Cyberduck is saying the transfer was incomplete. The only miss-match I can find between when uploads succeed and fail (according to Cyberduck's transfer window item status anyway), is that when it says "Transfer incomplete", it seems to have uploaded more data than there was to upload, I'm assuming due to re-trying some files again.

Am I missing some error console or logging somewhere, as I'd like to have some confidence in what Cyberduck is doing upload-wise...

Many thanks,

Peter Pearson

[David Kocher]

We are tracking this issue in https://trac.cyberduck.io/ticket/9552

– David

[Enrique Londaits]

Same thing happening to me while uploading to Google Drive. But the file is there, size is ok.

[peter....@gmail.com]

I've actually now seen situations where when this fails for large file uploads (i.e. > 1 GB), the file *was* actually corrupt in its uploaded state, so I assume (but have no proof) that the SHA1 that Cyberduck calculates before it starts uploading and that it sends to B2 (or maybe of the individual chunk parts?) doesn't match what gets received, and B2 returns an error.

But again, with no information as to what did fail, no return codes or anything, it's very difficult to say, and makes me seriously question the robustness of what Cyberduck is doing - admittedly it is saying it failed, but it could be more helpful, given B2's web API at least seems to provide pretty fine-grained error codes.

Peter

[peter....@gmail.com]

Just to say, that with the latest snapshot build with the fixes from David for the issue (see trak ticket above), it does seem this is fixed for the situation of uploading around 4 GB of ~25 MB files in directories. I've done four of these uploads and they all finish and say "Upload complete", whereas looking through the Transfer window history before the fix, I'd generally get 1 in 10 being successful, the others being "Transform incomplete".

I'm not sure what was happening with the situation I found with large single files not working correctly, possibly that was another issue or something else went wrong, so I'll ignore it for the moment unless I see it happening again.

Many thanks for the fix!

Peter

[David Kocher]

Version 6.4 is now available with the fix included.

– David

> --
> --
> You received this message because you are subscribed to the Google Groups "Cyberduck" group. To post to this group, send email to cybe...@googlegroups.com
> To unsubscribe from this group, send email to cyberduck+...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/cyberduck
> --
> Post bug reports and feature requests
> http://trac.cyberduck.ch/newticket
> --
> Support development
> http://cyberduck.ch/donate/
>
> ---
> You received this message because you are subscribed to the Google Groups "Cyberduck" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cyberduck+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.