-
Notifications
You must be signed in to change notification settings - Fork 70
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
s3sync fails with few files saying NoSuchKey: The specified key does not exist. #26
Comments
Hello. Another option is that the file was deleted after it was listed. |
Hey thanks for reaching me back, I have tried using skipmissing option but that skips the entire content in that folder, however I have checked the permission form s3 console I see read object as yes, read object permission as yes and write object permission as yes, also I have tried with straight aws s3 sync command works well and gets synced to local directory.
Tested with s4cmd works fine: with s3sync added the following options -
gets the following error:
However, under same s3 bucket, I have tested with another folder sync works:
s3sync -verison
|
Hey looks something close to this issue: s3cmd info gives the following output: However s3cmd sync works for that directory and files inside it. s3cmd ls and aws s3 ls lists all the directories and files inside it. |
Issue #24 related to another bug, that has been fixed. |
s3cmd info ouput:
s3cmd info ouput with object:
Below is the output for aws s3cmd sync for the same file that is failing with s3sync.
s3sync failed with the following error:
|
Somehow I feel s3sync is not picking up files under prefixes with "//" meaning s3://mytests3syncbucket//content, my data is under s3 bucket, under an empty folder and then under content folder so the path created was s3://mytests3syncbucket//content with '//' before content folder, I have moved the same file under the bucket s3://mytests3syncbucket and s3sync worked fine wich failed if it was under s3://mytests3syncbucket//content, so I'm assuming it is throwing NoSuckKey if it was under // folder, correct me if I'm wrong and I have tested this across |
It's known issue with double slash. It was fixed in latest commit, but build with this version was not released. I create new version with this fix, please try version |
Hey thanks a lot for that release, I have downloaded it and tried the s3sync commands still gets the same error Nosuchkey s3sync -version |
I commit bugfix to |
Hey sorry I'm late to update, it's working now, however when I try to run more than 128 processes it breaks, but this double slash bug I suppose it exists in aws cli itself? |
Hello.
|
@larrabee , Generally this issue comes , If Source and Destination Bucket User is different... |
@kannanvr, hello. I think it's not related issues. Can you create new issue and provide full cmd line (without keys). |
s3sync works with few s3 files and for few, it fails saying NoSuchKey: The specified key does not exist, anything to fix form s3 permission for am I missing any option with s3sync?
error log:
ERRO[0000] Sync error: pipeline step: 1 (LoadObjData) failed with error: object: content/directpath/health-check/abd/details/js.properties sync error: NoSuchKey: The specified key does not exist.
status code: 404, request id: xxxxxxxxxxxxxx, host id: v5dwefwefwefmkwmfkwa98y79790978ZKpjUNCAkKhE+8697fqbdqtdgbxbx0=, terminating
The text was updated successfully, but these errors were encountered: