Cyberduck Mountain Duck CLI

Opened on Sep 11, 2018 at 9:05:57 PM

Closed on Sep 14, 2018 at 9:19:53 PM

Last modified on Sep 20, 2018 at 8:57:36 PM

#10458 closed defect (fixed)

Interoperability with AWS Snowball

Reported by: greendm Owned by: dkocher
Priority: normal Milestone: 6.8.0
Component: s3 Version: 6.7.1
Severity: normal Keywords:
Cc: greendm@… Architecture: Intel
Platform: macOS 10.13

Description

Hello,

I am hoping to use Cyberduck to provide users access to AWS Snowball devices. I have begun testing using the "generic S3 profile" available here: ​https://trac.cyberduck.io/wiki/help/en/howto/s3#GenericS3profiles

Cyberduck is able to connect to S3 endpoint on the Snowball device, but there are errors when attempting to write data. I have attached a screenshot.

Reads from Snowball to local directories works fine, so it feels we are close!

I am able to put a single file to Snowball via Cyberduck, but writing multiple files or a directory fails with the attached screenshot.

Please let me know if any additional information is needed. I would like to be able to suggest Cyberduck to our customers using Snowball.

I have attached the debug log from system.log. Any help is appreciated.

Thanks!

David Green AWS greendm@…

Attachments (1)

cyberduck.log​ (1.1 MB) - added by greendm on Sep 11, 2018 at 9:06:26 PM.
debug log

Download all attachments as: .zip

Change History (9)

Changed on Sep 11, 2018 at 9:06:26 PM by greendm

debug log

comment:1 Changed on Sep 12, 2018 at 9:11:43 AM by dkocher

  • Component changed from core to s3
  • Milestone set to 7.0
  • Owner set to dkocher
  • Priority changed from high to normal
  • Status changed from new to assigned 
Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> PUT /mpp-goodbyestranger-sync/cyberduck/snowball2/ HTTP/1.1
5821	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> Date: Tue, 11 Sep 2018 21:00:15 GMT
5822	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> Expect: 100-continue
5823	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> Content-Type: application/x-directory
5824	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
5825	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> Host: 10.34.16.1
5826	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> x-amz-date: 20180911T210015Z
5827	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> Authorization: AWS4-HMAC-SHA256 Credential=65DY3OLJ0NQLG327O1OK/20180911/us-east-1/s3/aws4_request,SignedHeaders=content-type;date;host;x-amz-content-sha256;x-amz-date,Signature=0129b6b6a4925f60005397b3fcda9be7adf62f729b18f8231ca2ed1b25c3761a
5828	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> Content-Length: 0
5829	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> Connection: Keep-Alive
5830	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 >> User-Agent: Cyberduck/6.7.1.28683 (Mac OS X/10.13.3) (x86_64)
5831	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 << HTTP/1.1 100 Continue
5832	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 << Server: AmazonSnowball
5833	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 << Keep-Alive: timeout=89
5834	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 << HTTP/1.1 201 Created
5835	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 << Content-Type: text/plain; charset=utf-8
5836	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 << Content-Length: 0
5837	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 << ETag: "d41d8cd98f00b204e9800998ecf8427e"
5838	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 << Server: AmazonSnowball
5839	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.apache.http.headers - http-outgoing-9 << Keep-Alive: timeout=89
5840	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] INFO  ch.cyberduck.transcript.response - HTTP/1.1 201 Created
5841	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] INFO  ch.cyberduck.transcript.response - Content-Type: text/plain; charset=utf-8
5842	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] INFO  ch.cyberduck.transcript.response - Content-Length: 0
5843	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] INFO  ch.cyberduck.transcript.response - ETag: "d41d8cd98f00b204e9800998ecf8427e"
5844	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] INFO  ch.cyberduck.transcript.response - Server: AmazonSnowball
5845	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] INFO  ch.cyberduck.transcript.response - Keep-Alive: timeout=89


Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.jets3t.service.impl.rest.httpclient.RestStorageService - Response '/mpp-goodbyestranger-sync/cyberduck/snowball2/' - Received error response without XML content
5858	Sep 11 14:00:15 ProdTechs-Mac-Pro Cyberduck[1401]: [http-snowball2-1] DEBUG org.jets3t.service.impl.rest.httpclient.RestStorageService - Rethrowing as a ServiceException error in performRequest: org.jets3t.service.ServiceException: Request Error. -- ResponseCode: 201, ResponseStatus: null, with cause: org.jets3t.service.impl.rest.HttpException: 201 Created
Last edited on Sep 14, 2018 at 9:07:59 PM by dkocher (previous) (diff)

comment:2 Changed on Sep 12, 2018 at 9:11:55 AM by dkocher

  • Summary changed from S3 endpoint - AWS Snowball to Interoperability with AWS Snowball

comment:3 Changed on Sep 14, 2018 at 9:12:07 PM by dkocher

​https://docs.aws.amazon.com/AmazonS3/latest/API/RESTObjectPUT.html#RESTObjectPUT-responses

We expect a response code of 200 or 204 for a PUT operation but get 201.

comment:4 Changed on Sep 14, 2018 at 9:19:05 PM by dkocher

Upstream fix in ​2a76aa5.

comment:5 Changed on Sep 14, 2018 at 9:19:53 PM by dkocher

  • Resolution set to fixed
  • Status changed from assigned to closed

In r45070.

comment:6 Changed on Sep 20, 2018 at 6:47:20 AM by dkocher

Please update to the latest ​snapshot build available.

comment:7 Changed on Sep 20, 2018 at 6:52:01 AM by dkocher

  • Milestone changed from 7.0 to 6.7.2

comment:8 Changed on Sep 20, 2018 at 8:57:36 PM by dkocher

  • Milestone changed from 6.7.2 to 6.8.0

Milestone renamed

Note: See TracTickets for help on using tickets.