openstack/deb-heat
Code Issues Proposed changes

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.

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

Change-Id: I4dbf1a11d3737c4a8444b3a79de824acecb56d7d
This commit is contained in:
Bertrand Lallau 2015-11-04 13:38:17 +01:00
parent 1af66c5da2
commit ef5a2976b2
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/gmr.rst
View File

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