openstack/nova
Code Issues Proposed changes

doc: gmr: Update instructions to generate GMR error reports

Browse Source 
Guru Meditation Reports (GMR) code in oslo.reports was recently updated
to expect SIGUSR2 as opposed to SIGUSR1, because it is reserved by
Apache 'mod_wsgi' for its own use.

So, update the Nova doc, gmr.rst, to reflect this new reality.

[1] https://review.openstack.org/#/c/223133/ -- guru_meditation_report:
    Use SIGUSR2 instead of SIGUSR1

Change-Id: Iac2d606103189b965581e0c6c20b55360a04e3a6
This commit is contained in:
Kashyap Chamarthy
2015-09-25 12:46:44 +02:00
parent 1635086529
commit bd3911c4e8
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/gmr.rst
View File

@@ -21,9 +21,9 @@ Nova contains a mechanism whereby developers and system administrators can gener
Generating a GMR
----------------
A *GMR* can be generated by sending the *USR1* signal to any Nova process with support (see below). The *GMR* will then be outputted standard error for that particular process.
A *GMR* can be generated by sending the *USR2* signal to any Nova process with support (see below). The *GMR* will then be outputted standard error for that particular process.
For example, suppose that ``nova-api`` has process id ``8675``, and was run with ``2>/var/log/nova/nova-api-err.log``. Then, ``kill -USR1 8675`` will trigger the Guru Meditation report to be printed to ``/var/log/nova/nova-api-err.log``.
For example, suppose that ``nova-api`` has process id ``8675``, and was run with ``2>/var/log/nova/nova-api-err.log``. Then, ``kill -USR2 8675`` will trigger the Guru Meditation report to be printed to ``/var/log/nova/nova-api-err.log``.
Structure of a GMR
------------------