Browse Source

Document workaround for AccessDenied error

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
Ben Nemec 1 year ago
parent
commit
8d0e5fcc95
1 changed files with 6 additions and 0 deletions
  1. 6
    0
      doc/source/user/usage.rst

+ 6
- 0
doc/source/user/usage.rst View File

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

Loading…
Cancel
Save