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.

Bug 1377027

Summary: sealert -l: failed to connect to server: No such file or directory
Product: Red Hat Enterprise Linux 7 Reporter: Brian J. Murrell <brian>
Component: setroubleshootAssignee: Petr Lautrbach <plautrba>
Status: CLOSED DUPLICATE QA Contact: Milos Malik <mmalik>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.2CC: lvrabec, mgrepl, mmalik, plautrba
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-19 07:24:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brian J. Murrell 2016-09-17 17:37:07 UTC
Description of problem:
# sealert -l b1eecb90-3c8b-4024-9334-024e301c3e3b
failed to connect to server: No such file or directory

Version-Release number of selected component (if applicable):
setroubleshoot-server-3.2.24-4.el7_2.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Locate an AVC message in the journal/messages
2. run "sealert -l $uid" as it suggests

Actual results:
failed to connect to server: No such file or directory

Expected results:
Should work without an error

Additional info:

Comment 2 Petr Lautrbach 2016-09-18 14:49:43 UTC
This issue will be fixed in the next update.

As a workaround you can either 

- install setroubleshoot package

or

- download http://pkgs.fedoraproject.org/cgit/rpms/setroubleshoot.git/tree/setroubleshoot.tmpfiles, save it as /etc/tmpfiles.d/setroubleshoot.conf and run 'systemd-tmpfiles --create'

Comment 3 Brian J. Murrell 2016-09-18 16:25:33 UTC
Installing setroubleshoot does not fix the problem.  Or is there something else I have to do after installing that.  Not that I am fan of installing it given that it pulls in lots of dependencies that shouldn't be necessary on a server

(In reply to Petr Lautrbach from comment #2)
> This issue will be fixed in the next update.

As in RHEL 7.3?  Do you have a specific RPM version number I can look forward to?

> As a workaround you can either 
> 
> - install setroubleshoot package

Installing setroubleshoot does not seem to fix the problem.  Or is there something else I have to do after installing that?  Not that I am fan of installing it given that it pulls in lots of dependencies that shouldn't be necessary on a headless machine/server.

> or
> 
> - download
> http://pkgs.fedoraproject.org/cgit/rpms/setroubleshoot.git/tree/
> setroubleshoot.tmpfiles, save it as /etc/tmpfiles.d/setroubleshoot.conf and
> run 'systemd-tmpfiles --create'

Still no joy.  Is there a service I have to reload or restart after doing that?

Comment 4 Petr Lautrbach 2016-09-18 18:33:15 UTC
(In reply to Brian J. Murrell from comment #3)
> Installing setroubleshoot does not fix the problem.  Or is there something
> else I have to do after installing that.  Not that I am fan of installing it
> given that it pulls in lots of dependencies that shouldn't be necessary on a
> server

I completely understand. 

> (In reply to Petr Lautrbach from comment #2)
> > This issue will be fixed in the next update.
> 
> As in RHEL 7.3?  Do you have a specific RPM version number I can look
> forward to?

It's fixed in setroubleshoot-3.2.26-1.el7

> 
> > As a workaround you can either 
> > 
> > - install setroubleshoot package
> 
> Installing setroubleshoot does not seem to fix the problem.  Or is there
> something else I have to do after installing that?  Not that I am fan of
> installing it given that it pulls in lots of dependencies that shouldn't be
> necessary on a headless machine/server.
> 
> > or
> > 
> > - download
> > http://pkgs.fedoraproject.org/cgit/rpms/setroubleshoot.git/tree/
> > setroubleshoot.tmpfiles, save it as /etc/tmpfiles.d/setroubleshoot.conf and
> > run 'systemd-tmpfiles --create'
> 
> Still no joy.  Is there a service I have to reload or restart after doing
> that?

The important thing is the existence of /run/setroubleshoot directory. It needs to be owned by setroubleshoot:setroubleshoot

When setroubleshootd  starts, it creates an unix socket - /run/setroubleshoot/setroubleshoot_server

So if it's not there, try to restart setroubleshootd and run sealert again.

Comment 5 Petr Lautrbach 2016-09-19 07:24:36 UTC

*** This bug has been marked as a duplicate of bug 1348955 ***