View Issue Details

IDProjectCategoryView StatusLast Update
0014220CentOS-7setroubleshootpublic2018-08-19 02:12
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
PlatformOSOS Version7
Product Version 
Target VersionFixed in Version 
Summary0014220: [abrt] setroubleshoot-server: unable to open /sys/fs/selinux/policy: Device or ...
DescriptionDescription of problem:
Running - Gtk package

Version-Release number of selected component:

Truncated backtrace: unable to open /sys/fs/selinux/policy: Device or resource busy

Traceback (most recent call last):
  File "/usr/sbin/setroubleshootd", line 102, in <module>
  File "/usr/lib64/python2.7/site-packages/setroubleshoot/", line 699, in RunFaultServer
ValueError: unable to open /sys/fs/selinux/policy: Device or resource busy

Local variables in innermost frame:
timeout: 10
Additional Informationreporter: libreport-
cmdline: /usr/bin/python -Es /usr/sbin/setroubleshootd -f ''
executable: /usr/sbin/setroubleshootd
kernel: 4.14.3-1.el7.elrepo.x86_64
pkg_fingerprint: 24C6 A8A7 F4A8 0EB5
pkg_vendor: CentOS
reproducible: Not sure how to reproduce the problem
runlevel: N 5
type: Python
uid: 964
TagsNo tags attached.




2017-12-02 08:54


backtrace (473 bytes) unable to open /sys/fs/selinux/policy:  Device or resource busy

Traceback (most recent call last):
  File "/usr/sbin/setroubleshootd", line 102, in <module>
  File "/usr/lib64/python2.7/site-packages/setroubleshoot/", line 699, in RunFaultServer
ValueError: unable to open /sys/fs/selinux/policy:  Device or resource busy

Local variables in innermost frame:
timeout: 10
backtrace (473 bytes)
environ (92 bytes)
environ (92 bytes)
machineid (135 bytes)
machineid (135 bytes)


2018-03-22 01:07

reporter   ~0031487

There seems to be an issue with concurrent access to the sysfs mount on /sys/fs/selinux/policy. Simply running seinfo concurrently will cause an error.

# seinfo & seinfo
[1] 96493
ERROR: Unable to open policy /sys/fs/selinux/policy.
ERROR: Device or resource busy

# cat /etc/redhat-release
CentOS Linux release 7.4.1708 (Core)

# uname -a
Linux 3.10.0-693.17.1.el7.x86_64 #1 SMP Thu Jan 25 20:13:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


2018-05-23 00:55

reporter   ~0031894

Another user experienced a similar problem:

Warning message appeared when connecting using VNC viewer

reporter: libreport-
executable: /usr/sbin/setroubleshootd
kernel: 3.10.0-693.5.2.el7.x86_64
package: setroubleshoot-server-3.2.28-3.el7
pkg_fingerprint: 24C6 A8A7 F4A8 0EB5
pkg_vendor: CentOS
reason: unable to open /sys/fs/selinux/policy: Device or resource busy
reproducible: The problem occurs regularly
runlevel: N 3
type: Python
uid: 989


2018-08-19 02:12

reporter   ~0032530

I am getting same or very similar issue. I'm running CentOS Linux release 7.4.1708 (core) (as reported by the centos-release file in /etc). System appears stable, and is running correctly, as near as I can tell. Except about every hour or so, I get this "ABRT" indicating that there is an issue with SELinux Troubleshoot program, where the file /usr/selinux/targeted/policy/policy.31 file cannot be accessed. I have a policy.30 file from several months back, and the policy.31 file, which is current as of today. I updated several packages related to glibc and x11 today. Perhaps this created a new policy file? The file "policy.31" is read-available to all. The error seems to be similar to what amtradm reports (in that the type is Python). I have run: (as the ABRT notification suggested...)

   abrt-cli list --since 1534625010

and got this information:<module>:ValueError:Failed to read //etc/selinux/targeted/policy/policy.31 file
  time: Sat. Aug 18, 2018 ...
  cmdline: /usr/bin/python -Es /usr/bin/setroubleshootd -f ' '
  package: setroubleshoot -server-3.2.28_3.el7

Machine details: The GUI [System Tools/Settings/System Details] menu reports:
     Memory: 3.7 GiB
     Processor: Intel Core i3-2120 CPU @ 3.30Ghz x 4 (4 cores)
     Graphics: Intel Sandybridge Desktop
     Gnome: Version 3.22.2
     Disk: 1.2 TB

Could someone suggest if there is any specific action I can take to correct or workaround this issue? Thanx.

Issue History

Date Modified Username Field Change
2017-12-02 08:54 splang New Issue
2017-12-02 08:54 splang File Added: backtrace
2017-12-02 08:55 splang File Added: environ
2017-12-02 08:55 splang File Added: machineid
2018-03-22 01:07 hknief Note Added: 0031487
2018-05-23 00:55 amtradm Note Added: 0031894
2018-08-19 02:12 gemesyscanada Note Added: 0032530