Cyberduck Mountain Duck CLI

#11253 closed defect (thirdparty)

Mountainduck Copy from FSx to S3 seems broken?

Reported by: jordibares Owned by:
Priority: normal Milestone:
Component: core Version: 7.7.0
Severity: critical Keywords: AWS, S3
Cc: Architecture: Intel
Platform: Windows 10

Description

I am copying a tar file from my FSx server on AWS to my S3 bucket and although the system reports the copy successful and the data seems there, if I look from a different workstation (a local mac in this case), there are zero bytes copied.

Only when I disconnect from mountainduck is the data released and appears on the S3 bucket.

I don't know if has to do with any particular setting but this is highly disturbing as you can imagine.

My configuration is

Windows instance on AWS, FSX server and regular S3 bucket. I do have permissions and all that obviously.

In terms of mountainduck settings..

Smart Sync is off (I am on Online mode) No proxies Enable cache is ON

AWS S3 settings region EU london (eu-west-2)

Using Windows10 Pro

Change History (1)

comment:1 Changed on Nov 22, 2020 at 4:25:59 PM by dkocher

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

Please write to support@mountainduck.io. The issue might have been fixed in version 4.3.1.

Note: See TracTickets for help on using tickets.