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

Transfer incomplete when change permissions checked for uploads #9488

Closed
cyberduck opened this issue Apr 26, 2016 · 7 comments
Closed

Transfer incomplete when change permissions checked for uploads #9488

cyberduck opened this issue Apr 26, 2016 · 7 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Apr 26, 2016

c4eb05c created the issue

this happens with my mac, as long as i try have checked the box to change the permissions of the uploaded files, either to that of the local file and directory, or to something explicit.

if I uncheck the permissions preference, the upload works, but I have to use the AWS console itself to change permissions to make my upload public. this means that my user account does in fact have the rights to change permissions.

unfortunately the logs do not show anything useful, with the 5.0 snapshot I see only:

2016-04-25 17:10:22.901 Cyberduck[92702]: [main] WARN  ch.cyberduck.core.threading.ThreadPoolFactory - No matching constructor for parameter class ch.cyberduck.core.threading.LoggingUncaughtExceptionHandler

it looks like the true exception is being prevented from being logged due to this


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 26, 2016

@dkocher commented

Please post 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

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 27, 2016

c4eb05c commented

Unfortunately the log drawer seems blank, even with debug logging enabled.

I notice though that a few files do succeed in being uploaded, it seems to stop on the 2nd file in the first sub directory I am uploading.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 4, 2016

@dkocher commented

Can you please open the log drawer of the Transfers window prior starting the transfer and then post the output here.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 4, 2016

c4eb05c commented

I just attached a run log. I am running the latest version for MacOS, Version 5.0 (19930)

I hope the log is helpful, I could not see anything that stood out.

My previous examination of the internal logs seemed to indicate an exception during error handling, which could be making the error not be logged properly.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 4, 2016

@dkocher commented

Your account is missing permission to read the existing ACL for the bucket.

GET /?acl HTTP/1.1
Date: Wed, 04 May 2016 17:19:28 GMT
x-amz-request-payer: requester
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Host: tribecashortlistassets.s3.amazonaws.com
x-amz-date: 20160504T171928Z
Authorization: AWS4-HMAC-SHA256 Credential=AKIAIETGPTQA5OBUYQUQ/20160504/us-east-1/s3/aws4_request,SignedHeaders=date;host;x-amz-content-sha256;x-amz-date;x-amz-request-payer,Signature=bb36abfad3f94d5ae5cf302676560d717f3a89d09dc112973613636c2705c1ce
Connection: Keep-Alive
User-Agent: Cyberduck/5.0.19930 (Mac OS X/10.11.4) (x86_64)
HTTP/1.1 403 Forbidden
x-amz-request-id: C8E9763740B6DEE0
x-amz-id-2: kyVW/6P1rzKT+TjBrNf7ik4FDVnTxjKJLh2x/82DEkeGGyUdCiL27t6oTfZmygYt
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Wed, 04 May 2016 17:19:27 GMT
Server: AmazonS3

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 4, 2016

c4eb05c commented

Ok, thanks. I will try and followup to see if my account's permissions can be improved.

It occurs to me however that since I am requesting that my transfers unilaterally set the permissions to public, shouldn't Cyberduck be fixed to tolerate this case? I.e. it doesn't need to query the ACL, only set it to public.

It turns out that I have upload permission to a subfolder only of my S3 bucket, just not the /. Since I upload only to that subfolder, maybe the ACL for / does not need to be queried in this case.

What's funny is that when I set things to inherit the permission, the ACL is not queried. You would think it would need to be then, more so than when I am setting things to be unilaterally public.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 23, 2016

@dkocher commented

Replying to [comment:8 rblaa]:

Ok, thanks. I will try and followup to see if my account's permissions can be improved.

It occurs to me however that since I am requesting that my transfers unilaterally set the permissions to public, shouldn't Cyberduck be fixed to tolerate this case? I.e. it doesn't need to query the ACL, only set it to public.

We need to query the ACL to find the account owner ID which is required in the ACL when setting.

Loading

@cyberduck cyberduck closed this May 23, 2016
@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.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants