Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionBrian J. Murrell
2016-06-22 12:07:44 UTC
+++ This bug was initially created as a clone of Bug #1329550 +++
Cloning for RHEL7 because this appears to be happening there also.
Description of problem:
Unable to get alert details via sealert.
Version-Release number of selected component (if applicable):
Name : setroubleshoot-server
Arch : x86_64
Epoch : 0
Version : 3.3.5
Release : 3.fc24
Size : 1.6 M
Repo : @System
From repo : fedora
How reproducible:
Always
Steps to Reproduce:
1. Cause an avc denial that setroubleshoot picks up on
2. Run with id from journal, e.g. sealert -l 20b23739-fbb4-41f8-b6bc-1efe6b07a4cc
Actual results:
output: failed to connect to server: No such file or directory
Journal entry: /bin/sealert[22726]: attempt to open server connection failed: No such file or directory
Expected results:
Solution details.
Additional info:
System updated to latest fedora+updates, no testing packages
setenforce 0 doesn't affect the result/failure
--- Additional comment from Petr Lautrbach on 2016-04-25 08:01:01 EDT ---
I can't it reproduce it here. There's probably a problem with setroubleshootd.
Did you change seroubleshoot.conf? Can you see something suspicious in journal?
--- Additional comment from Dominik Perpeet on 2016-05-31 08:56 EDT ---
Sadly there is no extra helpful info in the journal.
It is still happening to me on Fedora 24:
Name : setroubleshoot-server
Arch : x86_64
Epoch : 0
Version : 3.3.8
Release : 0.3.fc24
Size : 1.6 M
Repo : @System
From repo : plautrba-setroubleshoot
Summary : SELinux troubleshoot server
URL : https://fedorahosted.org/setroubleshoot
License : GPLv2+
Description : Provides tools to help diagnose SELinux problems. When AVC messages
: are generated an alert can be generated that will give information
: about the problem and help track its resolution. Alerts can be configured
: to user preference. The same tools can be run on existing log files.
Name : setroubleshoot-plugins
Arch : noarch
Epoch : 0
Version : 3.3.4
Release : 1.fc24
Size : 3.6 M
Repo : @System
From repo : plautrba-setroubleshoot
Summary : Analysis plugins for use with setroubleshoot
URL : https://github.com/fedora-selinux/setroubleshoot
License : GPLv2+
Description : This package provides a set of analysis plugins for use with
: setroubleshoot. Each plugin has the capacity to analyze SELinux AVC
: data and system data to provide user friendly reports describing how
: to interpret SELinux AVC denials.
--- Additional comment from Dominik Perpeet on 2016-05-31 09:12:57 EDT ---
Installing the setroubleshoot package helped. Maybe there is some dependency issue, where setroubleshoot-server relies on the directory /var/run/setroubleshoot to be present.
--- Additional comment from Petr Lautrbach on 2016-05-31 13:17:48 EDT ---
strace really helped, thanks!
http://pkgs.fedoraproject.org/cgit/rpms/setroubleshoot.git/commit/?id=288066f917ebc344fb65e7ebb5ab9e198a75681f
--- Additional comment from Fedora Update System on 2016-06-02 09:35:19 EDT ---
setroubleshoot-3.3.8-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-68f69f600e
--- Additional comment from Fedora Update System on 2016-06-02 09:44:28 EDT ---
setroubleshoot-3.3.8-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-927d275831
--- Additional comment from Fedora Update System on 2016-06-03 05:26:42 EDT ---
setroubleshoot-3.3.8.1-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-68f69f600e
--- Additional comment from Fedora Update System on 2016-06-03 12:27:29 EDT ---
setroubleshoot-3.3.8.1-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-927d275831
--- Additional comment from Fedora Update System on 2016-06-07 21:24:17 EDT ---
setroubleshoot-3.3.8.1-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
--- Additional comment from Stef Walter on 2016-06-14 10:07:19 EDT ---
Glad to see this fixed. Workaround for this is:
$ sudo yum install setroubleshoot
$ reboot
The workaround installs lots of X11 stuff.
--- Additional comment from Petr Lautrbach on 2016-06-16 05:28:40 EDT ---
--- Additional comment from Fedora Update System on 2016-06-18 14:49:10 EDT ---
setroubleshoot-3.3.8.1-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2298.html