summaryrefslogtreecommitdiff
path: root/doc/cephadm/troubleshooting.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/cephadm/troubleshooting.rst')
-rw-r--r--doc/cephadm/troubleshooting.rst33
1 files changed, 33 insertions, 0 deletions
diff --git a/doc/cephadm/troubleshooting.rst b/doc/cephadm/troubleshooting.rst
index 375420ad182..93f42025f7f 100644
--- a/doc/cephadm/troubleshooting.rst
+++ b/doc/cephadm/troubleshooting.rst
@@ -8,6 +8,39 @@ a specific service no longer runs properly.
As cephadm deploys daemons as containers, troubleshooting daemons is slightly
different. Here are a few tools and commands to help investigating issues.
+Pausing or disabling cephadm
+----------------------------
+
+If something goes wrong and cephadm is doing behaving in a way you do
+not like, you can pause most background activity with::
+
+ ceph orch pause
+
+This will stop any changes, but cephadm will still periodically check hosts to
+refresh its inventory of daemons and devices. You can disable cephadm
+completely with::
+
+ ceph orch set backend ''
+ ceph mgr module disable cephadm
+
+This will disable all of the ``ceph orch ...`` CLI commands but the previously
+deployed daemon containers will still continue to exist and start as they
+did before.
+
+Checking cephadm logs
+---------------------
+
+You can monitor the cephadm log in real time with::
+
+ ceph -W cephadm
+
+You can see the last few messages with::
+
+ ceph log last cephadm
+
+If you have enabled logging to files, you can see a cephadm log file called
+``ceph.cephadm.log`` on monitor hosts (see :ref:`cephadm-logs`).
+
Gathering log files
-------------------