From a168c1240f95fc0146bb0cf461ac9e9f519bb168 Mon Sep 17 00:00:00 2001 From: Ihar Hrachyshka Date: Thu, 3 Mar 2016 16:16:10 +0100 Subject: [PATCH] Change signal used to generate Guru Meditation Reports for Nova Recently [1], the signal used to trigger oslo.reports feature changed from USR1 to USR2. Update the docs to reflect that. [1] https://github.com/openstack/oslo.reports/commit/45b1c02d113051d147e54ef921ce8e94135542d8 Change-Id: I11679d1f5c96103b1650cb9e4189dae23d573553 --- doc/admin-guide-cloud/source/support-compute.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/admin-guide-cloud/source/support-compute.rst b/doc/admin-guide-cloud/source/support-compute.rst index e3d3d84a9c..6f3b3ee81f 100644 --- a/doc/admin-guide-cloud/source/support-compute.rst +++ b/doc/admin-guide-cloud/source/support-compute.rst @@ -47,9 +47,9 @@ Guru Meditation reports ----------------------- A Guru Meditation report is sent by the Compute service upon receipt of the -``SIGUSR1`` signal. This report is a general-purpose error report, -including a complete report of the service's current state, and is sent to -``stderr``. +``SIGUSR2`` signal (``SIGUSR1`` before Mitaka). This report is a +general-purpose error report that includes details about the current state +of the service. The error report is sent to ``stderr``. For example, if you redirect error output to ``nova-api-err.log`` using :command:`nova-api 2>/var/log/nova/nova-api-err.log`, @@ -57,7 +57,7 @@ resulting in the process ID 8675, you can then run: .. code-block:: console - # kill -USR1 8675 + # kill -USR2 8675 This command triggers the Guru Meditation report to be printed to ``/var/log/nova/nova-api-err.log``.