| 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: | setroubleshoot | Assignee: | Petr Lautrbach <plautrba> |
| Status: | CLOSED DUPLICATE | QA Contact: | Milos Malik <mmalik> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | 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: | |
|
Description
Brian J. Murrell
2016-09-17 17:37:07 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' 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? (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. *** This bug has been marked as a duplicate of bug 1348955 *** |