You should try to create a new user without —system option so basically create a normal user , then create some bucket and object and finally try to resync cluster.
**************************************************************** Karan Singh Systems Specialist , Storage Platforms CSC - IT Center for Science, Keilaranta 14, P. O. Box 405, FIN-02101 Espoo, Finland mobile: +358 503 812758 tel. +358 9 4572001 fax +358 9 4572302 http://www.csc.fi/ **************************************************************** > On 28 Apr 2015, at 21:22, Karan Singh <[email protected]> wrote: > > You should try to create a new user without —system option so basically > create a normal user , then create some bucket and object and finally try to > resync cluster. > > -Karan- > >> On 28 Apr 2015, at 10:32, TERRY <[email protected] <mailto:[email protected]>> >> wrote: >> >> Hi： >> >> karan， singh. First of all thank you so much for replying and giving >> your precious time to this problem! >> >> I tried repeat steps 2, 4 and 5 in by executing them with >> --nameclient.radosgw-us-west-1. and the case has progressed a lot。(below are >> some the logs) >> >> >> I am now getting >> >> sudo radosgw-agent -c ceph-data-sync2.conf >> region map is: {u'us': [u'us-west', u'us-east']} >> INFO:radosgw_agent.sync:Starting sync >> INFO:radosgw_agent.worker:20585 is processing shard number 0 >> INFO:radosgw_agent.worker:finished processing shard 0 >> INFO:radosgw_agent.worker:20585 is processing shard number 1 >> INFO:radosgw_agent.sync:1/64 items processed >> INFO:radosgw_agent.sync:2/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 1 >> INFO:radosgw_agent.worker:20585 is processing shard number 2 >> INFO:radosgw_agent.sync:3/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 2 >> INFO:radosgw_agent.worker:20585 is processing shard number 3 >> INFO:radosgw_agent.sync:4/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 3 >> INFO:radosgw_agent.worker:20585 is processing shard number 4 >> INFO:radosgw_agent.sync:5/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 4 >> INFO:radosgw_agent.worker:20585 is processing shard number 5 >> INFO:radosgw_agent.sync:6/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 5 >> INFO:radosgw_agent.worker:20585 is processing shard number 6 >> INFO:radosgw_agent.sync:7/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 6 >> INFO:radosgw_agent.worker:20585 is processing shard number 7 >> INFO:radosgw_agent.sync:8/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 7 >> INFO:radosgw_agent.worker:20585 is processing shard number 8 >> INFO:radosgw_agent.sync:9/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 8 >> INFO:radosgw_agent.worker:20585 is processing shard number 9 >> INFO:radosgw_agent.sync:10/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 9 >> INFO:radosgw_agent.worker:20585 is processing shard number 10 >> INFO:radosgw_agent.sync:11/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 10 >> INFO:radosgw_agent.worker:20585 is processing shard number 11 >> INFO:radosgw_agent.sync:12/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 11 >> INFO:radosgw_agent.worker:20585 is processing shard number 12 >> INFO:radosgw_agent.sync:13/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 12 >> INFO:radosgw_agent.worker:20585 is processing shard number 13 >> INFO:radosgw_agent.sync:14/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 13 >> INFO:radosgw_agent.worker:20585 is processing shard number 14 >> INFO:radosgw_agent.sync:15/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 14 >> INFO:radosgw_agent.worker:20585 is processing shard number 15 >> INFO:radosgw_agent.sync:16/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 15 >> INFO:radosgw_agent.worker:20585 is processing shard number 16 >> INFO:radosgw_agent.sync:17/64 items processed >> INFO:radosgw_agent.worker:finished processing shard 16 >> INFO:radosgw_agent.worker:20585 is processing shard number 17 >> >> ...... >> >> ...... >> >> ...... >> >> INFO:radosgw_agent.worker:syncing bucket "my_container" >> ERROR:radosgw_agent.worker:failed to sync object my_container/us.json: state >> is error >> >> >> fyi: my_container is created by me in master zone, us.json is a object in >> my_container. >> >> i want to sync the object us.json to zone us-west zone. >> >> >> >> >> >> ------------------ 原始邮件 ------------------ >> 发件人: "Karan Singh";<[email protected] <mailto:[email protected]>>; >> 发送时间: 2015年4月28日(星期二) 下午3:02 >> 收件人: "TERRY"<[email protected] <mailto:[email protected]>>; >> 抄送: "ceph-users"<[email protected] >> <mailto:[email protected]>>; >> 主题: Re: [ceph-users] about rgw region and zone >> >> Hi >> >> >> >>> On 28 Apr 2015, at 07:12, TERRY <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi: all >>> >>> when I Configuring Federated Gateways， I got the error as below: >>> >>> sudo radosgw-agent -c /etc/ceph/ceph-data-sync.conf >>> ERROR:root:Could not retrieve region map from destination >> You should check that the region map is correct , especially the endpoints. >> Make sure firewall is not blocking the way between RGW instances. >> >>> Traceback (most recent call last): >>> File "/usr/lib/python2.6/site-packages/radosgw_agent/cli.py", line 269, >>> in main >>> region_map = client.get_region_map(dest_conn) >>> File "/usr/lib/python2.6/site-packages/radosgw_agent/client.py", line >>> 391, in get_region_map >>> region_map = request(connection, 'get', 'admin/config') >>> File "/usr/lib/python2.6/site-packages/radosgw_agent/client.py", line >>> 155, in request >>> check_result_status(result) >>> File "/usr/lib/python2.6/site-packages/radosgw_agent/client.py", line >>> 116, in check_result_status >>> HttpError)(result.status_code, result.content) >>> NotFound: Http error code 404 content {"Code":"NoSuchKey”} >> >> Cross verify the key >> >>> I have some quesions when I execute the command >>> 1、radosgw-admin zone set --rgw-zone=us-west --infile us-west.json --name >>> client.radosgw.us <http://client.radosgw.us/>-west-1 >>> i have no idea about the option --name , what's the difference if i >>> do it without --name config; >> >> —name us used to supply ceph user name that should be used to run >> radosgw-admin command against. Default is client.admin , if client.admin >> keyring are not present you need to supply another user with —name option to >> run Ceph commands. >> >>> >>> 2、Create a Region >>> there is a conversation near the end of doc : >>> If you use different Ceph Storage Cluster instances for regions, you >>> should repeat steps 2, 4 and 5 in by executing them with >>> --nameclient.radosgw-us-west-1. You may also export the region map from the >>> initial gateway instance and import it followed by updating the region map. >>> >>> I has one cluster named ceph, one region named us, and two zones: us-east、 >>> us-west， us-east is the master zone. I has two gateway >>> instances：client.radosgw.us-east-1、client.radosgw.us >>> <http://client.radosgw.us/>-west-1. Do i need repeat steps 2,4,and 5? do >>> i need export the region map from the initial gateway instance and import >>> it >> >> If you have 2 Different Ceph Cluster then only you should do this. I assume >> you have only 1 Ceph cluster with 1 region and 2 zones and 2 gateway >> instances , then you need not to repeat those steps. >> >>> >>> >>> _______________________________________________ >>> ceph-users mailing list >>> [email protected] <mailto:[email protected]> >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >>> <http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com> >> >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
