sealert (from setroubleshoot-server) in RHEL 7 fails with error: failed to connect to server: No such file or directory
Issue
-
Executing
sealert -l SOME_UUIDalways fails , e.g.:~]# yum install setroubleshoot-server ... ~]# service auditd restart ... ~]# passwd --help >junk.txt ~]# journalctl | grep junk.txt.*sealert Aug 15 12:47:18 a72.example.com setroubleshoot[1731]: SELinux is preventing /usr/bin/passwd from write access on the file /root/junk.txt. For complete SELinux messages. run sealert -l f1d43e5a-5251-4ff3-8fc7-a4f477f52f97 ~]# sealert -l f1d43e5a-5251-4ff3-8fc7-a4f477f52f97 failed to connect to server: No such file or directory ~]# journalctl | grep /usr/bin/sealert Aug 15 12:48:59 a72.example.com /usr/bin/sealert[1782]: attempt to open server connection failed: No such file or directory
Environment
- Red Hat Enterprise Linux 7
- setroubleshoot packages older than version
3.2.27.2-3.el7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
