Thanks! That helped.
It turns out the other issue was that I was running the admin command on the gateway node when I should have been running on the monitor node.
On Wed, Jun 1, 2016 at 5:06 PM, LOPEZ Jean-Charles <jelopez@xxxxxxxxxx> wrote:
Looks like I missed the paste: http://docs.ceph.com/docs/master/man/8/ceph/#optionsThere you have the options available from the command line.In your case the user id is radosgw-rgw0 so the command line should be radosgw-admin --id radosgw.rgw0 usage show or radosgw-admin --name client.radosgw.rgw0 usage showIf you do this it will cause the library to apply the parameters located in the [client.radosgw.rgw0] section of your config file which includes the location of the keyring.Assuming the keyring file pointed to by the config file is valid. You can still share its content via gist so we can check if it’s validJCOn Jun 1, 2016, at 14:37, RJ Nowling <rnowling@xxxxxxxxxx> wrote:I did use ceph-ansible to deploy the gateway -- using the default settings. It should work out of the box but does not.So... can the radosgw-admin CLI utility take a keyring path in the conf file or does the path need to be manually specified?And secondly, after copying the keyring to one of the default locations, I tried using the client.admin and radosgw.rgw ids you mentioned but neither worked:[vagrant@ceph-rgw0 ~]$ sudo radosgw-admin --id radosgw.rgw usage show2016-06-01 21:34:20.884525 7f2e5e01aa40 0 librados: client.radosgw.rgw authentication error (22) Invalid argumentcouldn't init storage provider[vagrant@ceph-rgw0 ~]$ sudo radosgw-admin --id client.admin usage show2016-06-01 21:34:31.699323 7fe774f96a40 0 librados: client.client.admin authentication error (22) Invalid argumentcouldn't init storage providerAnd what page were you referring to? I didn't see a link in the email.On Wed, Jun 1, 2016 at 4:30 PM, LOPEZ Jean-Charles <jelopez@xxxxxxxxxx> wrote:Hi,radosgw-admin is not radosgw. It’s the RADDOS Gateway cli admin utility.All ceph components by default use the client.admin user name to connect to the Ceph cluster. If you deployed the radosgw, the gateway itself was properly configured by Ansible and the files were placed where they have to be.To override, look at the following page and use the appropriate command line option to specify the proper user name or user id (--id or --name): e.g. radosgw-admin --id radosgw.rgw usage showRegardsJCOn Jun 1, 2016, at 14:07, RJ Nowling <rnowling@xxxxxxxxxx> wrote:_______________________________________________Hi all,I'm trying to set up a Ceph cluster with an S3 gateway using the ceph-ansible playbooks. I'm running into an issue where the radosgw-admin client can't find the keyring. The path to the keyring is listed in the ceph.conf file. I confirmed with strace that the client opens the conf file but doesn't open the path given in the conf file -- only the default keyring paths.Here's the output:[vagrant@ceph-rgw0 ~]$ sudo radosgw-admin usage show2016-06-01 13:36:17.294935 7fe45ac80a40 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory2016-06-01 13:36:17.300732 7fe45ac80a40 -1 monclient(hunting): authenticate NOTE: no keyring found; disabled cephx authentication2016-06-01 13:36:17.300737 7fe45ac80a40 0 librados: client.admin authentication error (95) Operation not supportedcouldn't init storage providerHere's the relevant part of the config file:[client.radosgw.rgw0]host = ceph-rgw0keyring = /var/lib/ceph/radosgw/ceph-rgw.ceph-rgw0/keyringrgw socket path = /tmp/radosgw-ceph-rgw0.socklog file = /var/log/ceph/ceph-rgw-ceph-rgw0.logrgw data = "">rgw frontends = civetweb port=10.0.2.15:8080 num_threads=50When I copy the keyring to /etc/ceph/keyring, the keyring is found but I get a different error:[vagrant@ceph-rgw0 ~]$ sudo radosgw-admin usage show2016-06-01 21:07:22.677525 7f62f2e38a40 0 librados: client.admin authentication error (22) Invalid argumentcouldn't init storage providerAny insights would be greatly appreciated!Thanks!RJ
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
- References:
- Client not finding keyring
- From: RJ Nowling
- Re: Client not finding keyring
- From: LOPEZ Jean-Charles
- Re: Client not finding keyring
- From: RJ Nowling
- Re: Client not finding keyring
- From: LOPEZ Jean-Charles
- Client not finding keyring
- Prev by Date: Encryption for data at rest support
- Next by Date: Re: Encryption for data at rest support
- Previous by thread: Re: Client not finding keyring
- Next by thread: Ceph API Announcement
- Index(es):