openstack/oslo.reports
Code Issues Proposed changes

Document workaround for AccessDenied error

Browse Source 
On SELinux-enabled platforms it is possible for the report process
to fail with an AccessDenied error when it tries to read information
about the process being debugged.  Per [1], the recommended solution
is to temporarily disable SELinux during debugging and then turn it
on again once the report has completed successfully.

1: https://bugzilla.redhat.com/show_bug.cgi?id=1292787

Change-Id: Ic12d5658858bb085448e1b437b548111d3c79583
Closes-Bug: 1756044
This commit is contained in:
Ben Nemec 2018-04-04 15:47:22 +00:00
parent a3ee768864
commit 8d0e5fcc95
1 changed files with 6 additions and 0 deletions

6
doc/source/user/usage.rst

@ -28,6 +28,12 @@ To trigger the report to be generated::
kill -SIGUSR2 <process_id>
.. note::
On SELinux platforms the report process may fail with an AccessDenied
exception. If this happens, temporarily disable SELinux enforcement
by running ``sudo setenforce 0``, trigger the report, then turn SELinux
back on by running ``sudo setenforce 1``.
Here is a sample report: