Ok so, I have looked at this some more. When you are running /var/www/s3gw.fcgi by hand you are getting an error because the client name used in that script is inconsistent with the one configured in /etc/ceph/ceph.conf. When apache runs that script it does:
So it is providing a socket (incidentally the same as the one in /etc/ceph/ceph.conf). So, i think this is a real bug but it is not likely the soure of your original problem since because apache provide a --socket the command does not error out.
I think we should still fix /var/www/s3gw.fcgi to use the correct ceph client (client.radosgw.gateway) as opposed to your patch which modifes ceph.conf.
Ok so, I have looked at this some more. When you are running /var/www/s3gw.fcgi by hand you are getting an error because the client name used in that script is inconsistent with the one configured in /etc/ceph/ ceph.conf. When apache runs that script it does:
FastCgiExternal Server /var/www/s3gw.fcgi -socket /tmp/radosgw.sock
So it is providing a socket (incidentally the same as the one in /etc/ceph/ ceph.conf) . So, i think this is a real bug but it is not likely the soure of your original problem since because apache provide a --socket the command does not error out.
I think we should still fix /var/www/s3gw.fcgi to use the correct ceph client (client. radosgw. gateway) as opposed to your patch which modifes ceph.conf.