File Created by Node.js Client is not accessible Gives error 404 Not Found Although Data on Storage Node

[rr-paras-patel]

Environment : O.S. CentOS_6.3.64bit LeoFS system version : 1.0.0-pre1 total replicas : 2

[Node(s) state] S storage_0@127.0.0.1 running 60a1e4ea 60a1e4ea 2014-02-06 11:32:40 +0900 S storage_1@127.0.0.1 running 60a1e4ea 60a1e4ea 2014-02-06 11:32:40 +0900 S storage_2@127.0.0.1 running 60a1e4ea 60a1e4ea 2014-02-06 11:32:40 +0900 S storage_3@127.0.0.1 running 60a1e4ea 60a1e4ea 2014-02-06 11:32:40 +0900 G gateway_0@127.0.0.1 running 60a1e4ea 60a1e4ea 2014-02-06 11:32:41 +0900

Results to be check : 1) Node.js Client Test Script : https://github.com/awslabs/aws-nodejs-sample/blob/master/sample.js

2) Bucket status $s3cmd ls s3://test 2014-02-06 05:17 6 s3://test/myKey $s3cmd get s3://test/mykey s3://test/mykey -> ./mykey [1 of 1] ERROR: S3 error: 404 (Not Found):

3) checked file location via telnet window and leofs command (no ring address assigned and file was on storage_2@127.0.0.1 node so i suspended storage_1@127.0.0.1 but no result.)

4) Another strange thing is i can upload the file with same name and diffrent content and size. $ s3cmd put mykey s3://test mykey -> s3://test/mykey [1 of 1] 4 of 4 100% in 0s 917.64 B/s done $ s3cmd ls s3://test 2014-02-06 05:17 6 s3://test/myKey //older file with 6 byte created by node.js client 2014-02-06 05:37 4 s3://test/mykey //new file with 4 byte uploaded by s3cmd client

5) After upload file location check

[yosukehara]

Thank you for your report. We'll check this issue.

[mocchira]

@Paras2009 The key you are using at your node.js client is not 'mykey' but 'myKey'.('K' is uppercase!) That's why s3cmd ls listed 2files. please check it out again!

[mocchira]

and I recommend you enabling the output access.log at leo_gateway for debug purpose.

[rr-paras-patel]

O.K. I accept this is very silly mistake but we should change output of this command. (e.g. Object not exist or available)