Hello, Issuing /etc/init.d/ceph-radosgw reload fails. We have successfully tested the following patch: if [ $DEBIAN -eq 1 ]; then start-stop-daemon --stop --signal HUP -x $RADOSGW --oknodo else - killproc $RADOSGW -SIGHUP + killproc $RADOSGW -HUP fi ;; restart|force-reload) https://github.com/herver/ceph/commit/1b000abac3a02d1e788bf25eead4b6873133f5d2 Best regards, Sebastien.
We do not ship rgw in RHEL, the radosgw package is part of the RHCEPH product -> re-targetting.
Also, we should target this at 1.3.z, ceph 2 will use systemd unit files.
*** Bug 1320117 has been marked as a duplicate of this bug. ***
Verified on ceph-osd-0.94.5-12.el7cp.x86_64 ceph-common-0.94.5-12.el7cp.x86_64 ceph-selinux-0.94.5-12.el7cp.x86_64 ceph-radosgw-0.94.5-12.el7cp.x86_64 mod_fastcgi-2.4.7-1.ceph.el7.x86_64 iozone-3.424-2_ceph.el7.x86_64 ceph-0.94.5-12.el7cp.x86_64 [ubuntu@magna116 ~]$ sudo /etc/init.d/ceph-radosgw reload Reloading ceph-radosgw configuration (via systemctl): [ OK ] [ubuntu@magna116 ~]$ ps aux | grep rados root 6619 0.1 0.0 7411772 25240 ? Ssl 05:25 0:17 /bin/radosgw -n client.rgw.magna116 ubuntu 24246 0.0 0.0 112648 960 pts/0 S+ 09:15 0:00 grep --color=auto rados [ubuntu@magna116 ~]$ sudo /etc/init.d/ceph-radosgw restart Restarting ceph-radosgw (via systemctl): [ OK ] [ubuntu@magna116 ~]$ ps aux | grep rados root 24367 1.0 0.0 7410744 13856 ? Ssl 09:16 0:00 /bin/radosgw -n client.rgw.magna116 ubuntu 24515 0.0 0.0 112644 960 pts/0 S+ 09:16 0:00 grep --color=auto rados [ubuntu@magna116 ~]$ sudo /etc/init.d/ceph-radosgw stop Stopping ceph-radosgw (via systemctl): [ OK ] [ubuntu@magna116 ~]$ sudo /etc/init.d/ceph-radosgw start Starting ceph-radosgw (via systemctl): [ OK ] [ubuntu@magna116 ~]$ ps aux | grep rados root 24710 1.7 0.0 7410704 19992 ? Ssl 09:16 0:00 /bin/radosgw -n client.rgw.magna116 ubuntu 24858 0.0 0.0 112644 960 pts/0 S+ 09:17 0:00 grep --color=auto rados [ubuntu@magna116 ~]$ sudo /etc/init.d/ceph-radosgw status /bin/radosgw is running.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0721.html