search

scality / cloudserver

Zenko CloudServer, an open-source Node.js implementation of the Amazon S3 protocol on the front-end and backend storage capabilities to multiple clouds, including Azure and Google.
https://www.zenko.io/cloudserver
Apache License 2.0
1.71k stars 241 forks source link

Location Constraint Info is invalid. #669

Closed amarcionek closed 7 years ago

amarcionek commented 7 years ago

Anyone seeing this error when trying to upload an object? Getting it with CloudBerry and S3Browser and latest build (7 days ago.)

{"name":"S3","clientIP":"::ffff:192.168.20.1","clientPort":19601,"httpMethod":"PUT","httpURL":"/kscott1/A79F758FD4.DIF","time":1490722748203,"req_id":"7d4208edd8b87f01cd8c","level":"info","message":"received request","hostname":"22370bf410a8","pid":49} {"name":"S3","bucketName":"kscott1","objectKey":"A79F758FD4.DIF","bytesReceived":2052592,"bodyLength":2052592,"accessKey":"accessKey1","bytesSent":200,"clientIP":"::ffff:192.168.20.1","clientPort":19601,"httpMethod":"PUT","httpURL":"/kscott1/A79F758FD4.DIF","contentLength":2052592,"httpCode":400,"time":1490722748206,"req_id":"7d4208edd8b87f01cd8c","elapsed_ms":3.303361,"level":"info","message":"responded with error XML","hostname":"22370bf410a8","pid":49}

nicolas2bert commented 7 years ago

Hey @amarcionek - Has 192.168.20.1 been listed in the restEndpoints section in your config.json?

Exemple: in S3/config.json

"restEndpoints": {
     "192.168.20.1": "us-east-1"
},

Note: Please make sure that "us-east-1" is listed in your S3/locationConfig.json

More info: https://github.com/scality/S3#location-configuration

amarcionek commented 7 years ago

I should have been a bit more specific. This is from the latest docker image built 7 days ago: https://hub.docker.com/r/scality/s3server/tags/

I could probably find a way to edit the locationConfig.json file inside of it after running the image (although neither nano nor vi is in the container), but shouldn't the container really be immutable? IOW, you would want people to run it out of the box without any configuration? The prior image (e2a2574) doesn't exhibit this issue.

nicolas2bert commented 7 years ago

@amarcionek - Ok - we are going to update it so you won't need to change the config.

amarcionek commented 7 years ago

Thanks for the help!

nicolas2bert commented 7 years ago

@amarcionek The Docker image has been updated with a fix - please pull the latest (1fcb189) S3 server Docker image. Keep us updated - thanks.

amarcionek commented 7 years ago

I can confirm this now works. THANKS!