From 6beee188fb7272ec7983d1c202bbbd982b2010e8 Mon Sep 17 00:00:00 2001 From: Zac Dover Date: Sat, 2 Dec 2023 06:32:26 +0100 Subject: [PATCH] doc/radosgw: add gateway starting command Add a command that properly starts (or restarts) the RADOS gateway after RGW settings have been changed. This commit has been added in response to an issue reported anonymously on https://pad.ceph.com/p/Report_Documentation_Bugs. Co-authored-by: Anthony D'Atri Signed-off-by: Zac Dover (cherry picked from commit ec7c515490c2ade44d886e423a6601c7ef0cf5e8) --- doc/radosgw/multisite.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/radosgw/multisite.rst b/doc/radosgw/multisite.rst index 8f6111ffbec38..3cbeb3b886940 100644 --- a/doc/radosgw/multisite.rst +++ b/doc/radosgw/multisite.rst @@ -528,6 +528,17 @@ running the following commands on the object gateway host: systemctl start ceph-radosgw@rgw.`hostname -s` systemctl enable ceph-radosgw@rgw.`hostname -s` +If the ``cephadm`` command was used to deploy the cluster, you will not be able +to use ``systemctl`` to start the gateway because no services will exist on +which ``systemctl`` could operate. This is due to the containerized nature of +the ``cephadm``-deployed Ceph cluster. If you have used the ``cephadm`` command +and you have a containerized cluster, you must run a command of the following +form to start the gateway: + +.. prompt:: bash # + + ceph orch apply rgw --realm= --zone= --placement --port + Checking Synchronization Status ------------------------------- -- 2.39.5