 |
backtrace (646 bytes) environ (92 bytes) machineid (135 bytes) |
|
|
Another user experienced a similar problem: Not sure - all was in appropriate order yesterday, but when I logged in this morning, the bug tracker notification was present. reporter: libreport-2.1.11.1 cmdline: /usr/bin/python -Es /usr/sbin/setroubleshootd -f '' executable: /usr/sbin/setroubleshootd kernel: 3.10.0-514.16.1.el7.x86_64 package: setroubleshoot-server-3.2.27.2-3.el7 pkg_fingerprint: 24C6 A8A7 F4A8 0EB5 pkg_vendor: CentOS reason: analyze.py:294:prune:ValueError: list modified during sort reproducible: Not sure how to reproduce the problem runlevel: N 5 type: Python uid: 990 |
|
|
Another user experienced a similar problem: dani reporter: libreport-2.1.11.1 cmdline: /usr/bin/python -Es /usr/sbin/setroubleshootd -f '' executable: /usr/sbin/setroubleshootd kernel: 3.10.0-957.1.3.el7.x86_64 package: setroubleshoot-server-3.2.30-3.el7 pkg_fingerprint: 24C6 A8A7 F4A8 0EB5 pkg_vendor: CentOS reason: analyze.py:294:prune:ValueError: list modified during sort reproducible: The problem occurs regularly runlevel: N 5 type: Python uid: 992 |
|
|
the problem is derived from the installation of an antivirus as in my case eset nod 32 and the deactivation of the selinux |
|
|
Another user experienced a similar problem: I accepted updated to my CentOS system and since then I've had issues with the setroubleshoot memory usage growing taking all available memory. Upon a system restart it's ok for a few hours or a day then it starts to missbehave. The number of account lock+unlocks may contribute to the issue. The system /var/log/messages contains a lot of the following: Jan 22 08:20:02 <system_name> setroubleshoot: SELinux is preventing /usr/bin/dbus-daemon from associate access on the shared memory labeled unconfined_service_t. For complete SELinux messages run: sealert -l d8be4013-90b5-4328-b5f3-8f68fa33b8af Jan 22 08:20:02 <system_name> python: SELinux is preventing /usr/bin/dbus-daemon from associate access on the shared memory labeled unconfined_service_t.#012#012***** Plugin associate (99.5 confidence) suggests *************************#012#012If you want to change the label of Unknown to system_dbusd_t, you are not allowed to since it is not a valid file type.#012Then you must pick a valid file label.#012Do#012select a valid file type. List valid file labels by executing: #012# seinfo -afile_type -x#012#012***** Plugin catchall (1.49 confidence) suggests **************************#012#012If you believe that dbus-daemon should be allowed associate access on shm labeled unconfined_service_t by default.#012Then you should report this as a bug.#012You can generate a local policy module to allow this access.#012Do#012allow this access for now by executing:#012# ausearch -c 'dbus-daemon' --raw | audit2allow -M my-dbusdaemon#012# semodule -i my-dbusdaemon.pp#012 Jan 22 08:20:02 <system_name> sedispatch: AVC Message for setroubleshoot, dropping message Jan 22 08:20:02 <system_name> sedispatch: AVC Message for setroubleshoot, dropping message Jan 22 08:20:02 <system_name> sedispatch: AVC Message for setroubleshoot, dropping message reporter: libreport-2.1.11.1 cmdline: /usr/bin/python -Es /usr/sbin/setroubleshootd -f '' executable: /usr/sbin/setroubleshootd kernel: 3.10.0-693.21.1.el7.x86_64 package: setroubleshoot-server-3.2.29-3.el7 pkg_fingerprint: 24C6 A8A7 F4A8 0EB5 pkg_vendor: CentOS reason: analyze.py:294:prune:ValueError: list modified during sort reproducible: The problem is reproducible runlevel: N 5 type: Python uid: 995 |
|
|
This issue occurs when the machine has been up for 24 hours. At or a few seconds after an uptime of 24 hours I see the CPU usage start behaving erratically and the RAM usage increase. |
|
|
Another user experienced a similar problem: reason: analyze.py:294:prune:ValueError: list modified during sort cmdline: /usr/bin/python -Es /usr/sbin/setroubleshootd -f '' package: setroubleshoot-server-3.2.30-8.el7 uid: 989 (setroubleshoot) count: 1 Directory: /var/spool/abrt/Python-2022-09-01-06:33:24-13249 |
- Anonymous
