Cyberduck Mountain Duck CLI

#6117 closed defect (thirdparty)

MD5 checksum mismatch error

Reported by: gaurav Owned by: dkocher
Priority: normal Milestone: 4.1
Component: openstack Version: 4.0.2
Severity: normal Keywords:
Cc: Architecture:
Platform:

Description

I am using Cyberduck on Mac, it works fine with swift, but with S3(swift3) when i try to create some object it gives MD5 checksum mismatch error, even though object creation is successfull.

I tried to trace the checksum swift generating at server side, its matching with what cyberduck is complaining mismatch. I think there is some issue with cyberduck on Mac for S3, with windows it works fine with both swift and S3.

I am not sure about cyberduck version, how to check for the version?

Attachments (2)

mac_s3_md5.png (198.6 KB) - added by gaurav on Aug 1, 2011 at 8:26:40 AM.
Transfer window.
cyberduck.png (13.7 KB) - added by aivaras.sukackas on Jun 4, 2015 at 6:49:01 AM.
openstack swift error

Download all attachments as: .zip

Change History (18)

comment:1 follow-up: Changed on Jul 29, 2011 at 5:13:31 PM by dkocher

Use the menu Cyberduck → Check for Update….

comment:2 Changed on Jul 30, 2011 at 3:00:41 PM by dkocher

  • Summary changed from Cyberduck not working on MAC with S3. to MD5 checksum mismatch error

comment:3 follow-up: Changed on Jul 31, 2011 at 2:31:49 PM by dkocher

I have never tested against a swift3 endpoint. Can you post the transcript from the log drawer (Transfer window).

comment:5 in reply to: ↑ 1 Changed on Aug 1, 2011 at 5:48:53 AM by gaurav

Replying to dkocher:

Use the menu Cyberduck → Check for Update….

Cyberduck version is 4.0.1

Changed on Aug 1, 2011 at 8:26:40 AM by gaurav

Transfer window.

comment:6 in reply to: ↑ 3 Changed on Aug 1, 2011 at 8:30:46 AM by gaurav

Replying to dkocher:

I have never tested against a swift3 endpoint. Can you post the transcript from the log drawer (Transfer window).

I have attached the screenshot of transfer window. As you can see file is uploaded but it still gives md5 error.

comment:7 Changed on Aug 1, 2011 at 8:39:15 AM by dkocher

  • Resolution set to thirdparty
  • Status changed from new to closed

The response is missing a ETag header.

comment:8 follow-up: Changed on Aug 1, 2011 at 8:43:19 AM by dkocher

Actually as of r8710 we already check if the ETag header is missing and don't compare if so. Therefore I suppose there is actually an ETag header included in the response that has the value null.

comment:9 in reply to: ↑ 8 ; follow-up: Changed on Aug 1, 2011 at 9:52:23 AM by gaurav

Replying to dkocher:

Actually as of r8710 we already check if the ETag header is missing and don't compare if so. Therefore I suppose there is actually an ETag header included in the response that has the value null.

I wonder how its working on windows then?

comment:10 in reply to: ↑ 9 Changed on Aug 1, 2011 at 10:01:42 AM by dkocher

Replying to gaurav:

Replying to dkocher:

Actually as of r8710 we already check if the ETag header is missing and don't compare if so. Therefore I suppose there is actually an ETag header included in the response that has the value null.

I wonder how its working on windows then?

I can't explain any difference. We use the very same core library on both platforms and it should behave the same.

comment:11 follow-up: Changed on Aug 1, 2011 at 10:02:01 AM by dkocher

To compare we would need the transcript from the log drawer of the Transfers window.

comment:12 in reply to: ↑ 11 ; follow-up: Changed on Aug 1, 2011 at 10:42:43 AM by gaurav

Replying to dkocher:

To compare we would need the transcript from the log drawer of the Transfers window.

Ok on windows i am using 4.1. Its working with 4.1. When i upgraded to 4.1 on Mac, its also working their. Its failing with earlier versions on both Mac and Windows, with the same error as i mentioned earlier. Is their any fix regarding this gone in 4.1.

comment:13 in reply to: ↑ 12 Changed on Aug 1, 2011 at 11:42:11 AM by dkocher

Replying to gaurav:

Replying to dkocher:

To compare we would need the transcript from the log drawer of the Transfers window.

Ok on windows i am using 4.1. Its working with 4.1. When i upgraded to 4.1 on Mac, its also working their. Its failing with earlier versions on both Mac and Windows, with the same error as i mentioned earlier. Is their any fix regarding this gone in 4.1.

That explains it, yes. Version 4.1 was the first release to include the patch in r8710.

comment:14 Changed on Aug 1, 2011 at 11:42:28 AM by dkocher

  • Milestone set to 4.1
  • Version changed from 4.1 to 4.0.2

Changed on Jun 4, 2015 at 6:49:01 AM by aivaras.sukackas

openstack swift error

comment:15 follow-up: Changed on Jun 4, 2015 at 6:49:36 AM by aivaras.sukackas

problems with native openstack swift just in windows

Last edited on Jun 4, 2015 at 7:01:03 AM by aivaras.sukackas (previous) (diff)

comment:16 in reply to: ↑ 15 Changed on Jun 4, 2015 at 7:53:17 AM by dkocher

Replying to aivaras.sukackas:

problems with native openstack swift just in windows

Please open a new issue with the transcript from the log drawer of the Transfers window. Choose ⌘-L on Mac or right-click the toolbar from the Transfers window and choose Log on Windows.

Note: See TracTickets for help on using tickets.