Hello

We have a dual stack test machine running RadosGW.  It is currently configured 
for IPv4 only.  This is done in the ceph.conf with:
rgw_frontends="civetweb port=443s 
ssl_certificate=/etc/grid-security/hostcertkey.pem num_threads=2000 
access_log_file=/var/log/ceph/ceph-client.rgw.ceph-test-gw691-access.log 
error_log_file=/var/log/ceph/ceph-client.rgw.ceph-test-gw691-error.log"

According to the civetweb documentation we can specify for it to listen to both 
IPv4 and IPv6 addresses by doing: +443s or 443s,[::]:443s.  Unfortunately when 
we try either of these configurations (and a range of other things we tried in 
desperation) the service fails to start and we see this in the log:
2017-10-30 15:58:47.727956 7f7b2218fc80  0 ceph version 11.2.1 
(e0354f9d3b1eea1d75a7dd487ba8098311be38a7), process radosgw, pid 12640
2017-10-30 15:58:47.994738 7f7b2218fc80  0 WARNING: skipping unknown framework: 
443s
2017-10-30 15:58:47.994789 7f7b2218fc80  0 starting handler: civetweb
2017-10-30 15:58:47.994875 7f7b2218fc80  0 civetweb: 0x7f7b22b2cb20: Cannot add 
SSL socket (entry 1). Is -ssl_certificate option set?
2017-10-30 15:58:47.994889 7f7b2218fc80 -1 ERROR: failed run

We have tested that individually both the IPv4 and IPv6 works (the service 
starts and transfers work), so we believe the problem is with how ceph parses 
the port setting.  We did consider the possibility of running two radosgw 
instances on the same machine, but thought it more sensible to ask if anyone 
else has had the same problem and if they managed to fix it?  

Thanks

Alastair
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to