I'm pretty sure we won't fix the curl stuff, since RHEL 6 is unlikely to backport  curl_multi_wait().

The problem seems to be with the missing keyring... Yehuda?

These are just warnings, they are not fatal.

static void check_curl()
{
  derr << "WARNING: libcurl doesn't support curl_multi_wait()" << dendl;
  derr << "WARNING: cross zone / region transfer performance may be affected" << dendl;
}

The real problem is here I believe...

340 int MonClient::init()
341 {
...
365   if (auth_supported->is_supported_auth(CEPH_AUTH_CEPHX)) {
366     r = keyring->from_ceph_context(cct);
367     if (r == -ENOENT) {
368       auth_supported->remove_supported_auth(CEPH_AUTH_CEPHX);
369       if (auth_supported->get_supported_set().size() > 0) {
370 »·······r = 0;
371 »·······no_keyring_disabled_cephx = true;
372       } else {
373 »·······lderr(cct) << "ERROR: missing keyring, cannot use cephx for authentication" << dendl;

Leading to...

204 int librados::RadosClient::connect()
205 {
...
255   err = monclient.init();
256   if (err) {
257     ldout(cct, 0) << conf->name << " initialization error " << cpp_strerror(-err) << dendl;
258     shutdown();
259     goto out;
260   }

Could you check
https://access.redhat.com/documentation/en/red-hat-ceph-storage/version-1.2.3/red-hat-ceph-storage-123-ceph-object-gateway-for-rhel-x86-64/#configure_ceph_object_gateway
especially section 2.5, and make sure your keys are set up correctly?

If we look at /etc/init.d/ceph-radosgw we see the following.

# bash -x /etc/init.d/ceph-radosgw start 2>&1|grep client.radosgw
+ PREFIX=client.radosgw.
++ ceph-conf --list-sections client.radosgw.
++ ceph-conf -n client.radosgw.magna117 'auto start'
++ ceph-conf -n client.radosgw.magna117 host
++ ceph-conf -n client.radosgw.magna117 user
++ /usr/bin/radosgw -n client.radosgw.magna117 --show-config-value log_file
+ log_file=/var/log/radosgw/client.radosgw.gateway.log
+ '[' -n /var/log/radosgw/client.radosgw.gateway.log ']'
+ '[' '!' -e /var/log/radosgw/client.radosgw.gateway.log ']'
+ daemon --user=apache '/usr/bin/radosgw -n client.radosgw.magna117'
+ '[' '/usr/bin/radosgw -n client.radosgw.magna117' '!=' '/usr/bin/radosgw -n client.radosgw.magna117' ']'
+ base='radosgw -n client.radosgw.magna117'
+ __pids_var_run 'radosgw -n client.radosgw.magna117' ''
+ local 'base=radosgw -n client.radosgw.magna117'
+ local 'pid_file=/var/run/radosgw -n client.radosgw.magna117.pid'
++ /usr/bin/dirname /var/run/radosgw -n client.radosgw.magna117.pid
+ '[' -f '/var/run/radosgw -n client.radosgw.magna117.pid' ']'
+ runuser -s /bin/bash apache -c 'ulimit -S -c 0 >/dev/null 2>&1 ; /usr/bin/radosgw -n client.radosgw.magna117'
+ success 'radosgw -n client.radosgw.magna117 startup'
+ echo 'Starting client.radosgw.magna117...'
Starting client.radosgw.magna117...

So it calculates some of the name from "hostname -s" so when starting we need to specify the name and we also need to add a key for the *actual* name, client.radosgw.magna117, not client.radosgw.gateway.

So I added a key per the docs and can now start the gateway fine.

# radosgw -d -n client.radosgw.magna117 startup
2016-02-09 22:25:19.911201 7f8af7e07820  0 ceph version 0.80.8 (69eaad7f8308f21573c604f121956e64679a52a7), process radosgw, pid 26602
2016-02-09 22:25:19.911207 7f8af7e07820 -1 WARNING: libcurl doesn't support curl_multi_wait()
2016-02-09 22:25:19.911209 7f8af7e07820 -1 WARNING: cross zone / region transfer performance may be affected
2016-02-09 22:25:20.109311 7f8ac28fa700  0 ERROR: can't get key: ret=-2
2016-02-09 22:25:20.109330 7f8ac28fa700  0 ERROR: sync_all_users() returned ret=-2
2016-02-09 22:25:20.109582 7f8af7e07820  0 framework: fastcgi
2016-02-09 22:25:20.109605 7f8af7e07820  0 framework conf key: socket_port, val: 9000
2016-02-09 22:25:20.109611 7f8af7e07820  0 framework conf key: socket_host, val: 0.0.0.0
2016-02-09 22:25:20.109616 7f8af7e07820  0 starting handler: fastcgi

Rachana, Have another go at setting this up, only this time when following the docs instead of "client.radosgw.gateway" use "client.radosgw.magna117" and use "-n client.radosgw.magna117" when starting the gateway. If that works we can see whether a doc bug is needed or where we go from there.

tried solution suggested in Comment#3 but it didn't solve problem

(In reply to Rachana Patel from comment #5)
> tried solution suggested in Comment#3 but it didn't solve problem

Do you mean comment#4 ?

The rados gateway was starting up and running fine on magna117 when I logged out?

Are you still having trouble with this? If so, I may need to set up a rhel6 cluster and document the steps, if any, that differ from the docs to get this going.

(In reply to Brad Hubbard from comment #6)
> (In reply to Rachana Patel from comment #5)
> > tried solution suggested in Comment#3 but it didn't solve problem
> 
> Do you mean comment#4 ?
> 
> The rados gateway was starting up and running fine on magna117 when I logged
> out?
> 
> Are you still having trouble with this? If so, I may need to set up a rhel6
> cluster and document the steps, if any, that differ from the docs to get
> this going.

Sorry, for typo, I meant Comment#4.

Yes, it was working on that node(magna117), But when I set up new cluster  and followed Doc it didn't work in that. So looks like something is different than Doc and better to document steps again.

(In reply to Rachana Patel from comment #7)
> Sorry, for typo, I meant Comment#4.

No problem.

> 
> Yes, it was working on that node(magna117), But when I set up new cluster 
> and followed Doc it didn't work in that. So looks like something is
> different than Doc and better to document steps again.

I see. I'll get onto this on Monday, thanks for your patience.

1.2 is going EOL very soon; closing