Gentlemen, I have resolved my issue, it was resolved using ,[client.rgw.gateway]
Towards helping others I have the following comments for the documentation people, unless somehow I am missing a nuance in using [client.rgw.gateway] and [client.rgw.<hostname>] and [client.radosgw.gateway] and [client.radosgw.<hostname>] Starting at the top: http://docs.ceph.com/docs/jewel/radosgw/ Then to… MANUAL INSTALL (http://docs.ceph.com/docs/jewel/install/install-ceph-gateway/) ======================= Could be consistent with ceph.conf specifiers: CHANGE THE DEFAULT PORT Mentions: [client.rgw.gateway-node1] -and then in another section- MIGRATING FROM APACHE TO CIVETWEB Mentions:[client.radosgw.gateway-node1] Mentions:[client.radosgw.gateway-node] Note the difference in “rgw” and “radosgw” SIMPLE CONFIGURATION (http://docs.ceph.com/docs/jewel/radosgw/config/) ======================= Talk about using name for “gateway” instance in first paragraph, which is not consistent with “Manual Install”, which uses <gateway-node> (i.e., hostname -s). ADD A GATEWAY CONFIGURATION TO CEPH Mentions: [client.radosgw.gateway] Not consistent with “rgw” vs “radosgw” Talks about Apache and civetweb, these could be more distinct and presented as either this civetweb or apache config, not intermingled… -----Original Message----- From: Karol Mroz [mailto:[email protected]] Sent: Tuesday, June 07, 2016 1:59 PM To: Sylvain, Eric <[email protected]> Cc: LOPEZ Jean-Charles <[email protected]>; [email protected] Subject: Re: [ceph-users] New user questions with radosgw with Jewel 10.2.1 Hi Eric, Please see inline... On Tue, Jun 07, 2016 at 05:14:25PM +0000, Sylvain, Eric wrote: > > Yes, my system is set to run as “ceph”: > > /etc/systemd/system/ceph-radosgw.target.wants/[email protected]<mailto:/etc/systemd/system/ceph-radosgw.target.wants/[email protected]> > ExecStart=/usr/bin/radosgw -f --cluster ${CLUSTER} --name > client.%i -conf --setuser ceph --setgroup ceph The first thing to check is the heading line of the RGW section in your ceph.conf file. Systemd passes --name as "client.%i" where "%i" expands to (in your case): rgw.p6-os1-mon7. Thus, your ceph.conf RGW heading should be: [client.rgw.p6-os1-mon7] If these entires do not match, RGW will not parse the necessary configuration section and will simply use defaults (ie. port 7480, etc). > > Yet changing these to “root” has no effect. > ExecStart=/usr/bin/radosgw -f --cluster ${CLUSTER} --name client.%i > -conf --setuser root --setgroup root Using user root is not needed for binding to privileged ports. When configured to use civetweb, RGW delegates the permission drop to civetweb. Civetweb does this _after_ binding to a port, reading certificates, etc. So, using the default "--user ceph" and "--group ceph" is best. > > Also doing: chown root.root /usr/bin/radosgw; chmod 4755 > /usr/bin/radosgw Had no effect. This is not needed. > > I feel the issue is in reading /etc/ceph/ceph.conf, because even if I change > rgw frontends = “bogus bogus bogus” > Expecting some failure, it still started up fine (on port 7480). > The config still says: > # ceph --admin-daemon /var/run/ceph/ceph-client.rgw.p6-os1-mon7.asok > config show > … > "rgw_frontends": "fastcgi, civetweb port=7480", > … Which points to RGW not parsing it's config section. > > Again suspecting keyring I created “client.radosgw.gateway” and > changed ceph.conf for it, to see if that would help, no luck… > > Could this be tied to having admin, mon and radosgw on same host? RGW should reside happily alongside any of the ceph daemons. > > Does keyring restrict what parts of ceph.conf are available? > > Thanks in advance for anything you can provide > Hope this helps. -- Regards, Karol _______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
