doc/cephadm: some troubleshooting tips

Signed-off-by: Sage Weil <sage@redhat.com>

diff --git a/doc/cephadm/operations.rst b/doc/cephadm/operations.rst
index 2e25874aabdf8d7a7cb0fe21433bb9dd4f9e964a..59e2f2965f327248f84cab81c9ab849ecea199a0 100644 (file)
--- a/doc/cephadm/operations.rst
+++ b/doc/cephadm/operations.rst
@@ -26,6 +26,8 @@ These events are also logged to the ``ceph.cephadm.log`` file on
 monitor hosts and to the monitor daemons' stderr.
 
 
+.. _cephadm-logs:
+
 Ceph daemon logs
 ================
 

diff --git a/doc/cephadm/troubleshooting.rst b/doc/cephadm/troubleshooting.rst
index 375420ad1828296d728630d6ead8dabbdfd74277..c8208cef5ffd9ba9b2e03595d0a00de54142f2f8 100644 (file)
--- 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 thigns go wrong and cephadm is doing something you don't 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 realtime 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
 -------------------