Bug 1234313 - /usr/bin/sealert: attempt to open server connection failed: No such file or directory
Summary: /usr/bin/sealert: attempt to open server connection failed: No such file or d...
Keywords:
Status: CLOSED DUPLICATE of bug 1329550
Alias: None
Product: Fedora
Classification: Fedora
Component: setroubleshoot
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Lautrbach
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-22 11:09 UTC by Juan Orti
Modified: 2016-06-16 09:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-16 09:28:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Juan Orti 2015-06-22 11:09:29 UTC
Description of problem:
I cannot use sealert to view a specific alert.

# journalct 
setroubleshoot[1324]: SELinux is preventing radvd from using the dac_override capability. For complete SELinux messages. run sealert -l aad0a6b8-475a-4788-9719-f2014c613963
[...]

# sealert -l aad0a6b8-475a-4788-9719-f2014c613963
failed to connect to server: No such file or directory

# journalctl
/usr/bin/sealert[1911]: attempt to open server connection failed: No such file or directory

Version-Release number of selected component (if applicable):
setroubleshoot-plugins-3.0.61-1.fc22.noarch
setroubleshoot-server-3.2.24-1.fc22.x86_64

Comment 1 Mike Gerber 2015-09-30 05:30:09 UTC
I have the same problem on F22. strace revealed that sealert tries to open /var/run/setroubleshoot/setroubleshoot_server, which does not exist. 

Quick fix: Create /etc/tmpfiles.d/setroubleshoot.conf with the following contents and reboot:

D /var/run/setroubleshoot 0755 setroubleshoot root -

Comment 2 Mike Gerber 2015-09-30 05:31:38 UTC
# rpm -qa | grep setrouble
setroubleshoot-server-3.2.24-2.fc22.x86_64
setroubleshoot-plugins-3.0.61-1.fc22.noarch

Comment 3 Juan Orti 2016-06-16 09:24:10 UTC
Keeps failing in Fedora 24. After creating the directory /var/run/setroubleshoot as Mike said and killing setroubleshootd, it works.

# rpm -qa|grep setrouble
setroubleshoot-plugins-3.3.4-1.fc24.noarch
setroubleshoot-server-3.3.7-1.fc24.x86_64

# LANG=C ls -la /var/run/setroubleshoot
ls: cannot access '/var/run/setroubleshoot': No such file or directory

# LANG=C strace -f sealert -l 15a5aba5-49c1-45f8-ace2-850bf58f3527
[...]
[pid  2950] set_robust_list(0x7fba3bdc49e0, 24) = 0
[pid  2950] mmap(NULL, 134217728, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = 0x7fba335c4000
[pid  2950] munmap(0x7fba335c4000, 10731520) = 0
[pid  2950] munmap(0x7fba38000000, 56377344) = 0
[pid  2950] mprotect(0x7fba34000000, 135168, PROT_READ|PROT_WRITE) = 0
[pid  2950] prctl(PR_SET_NAME, "gmain\0\0\0X+\317N\272\177\0\0") = 0
[pid  2950] poll([{fd=6, events=POLLIN}], 1, -1) = 1 ([{fd=6, revents=POLLIN}])
[pid  2950] poll([{fd=6, events=POLLIN}], 1, -1) = 1 ([{fd=6, revents=POLLIN}])
[pid  2950] read(6, "\1\0\0\0\0\0\0\0", 16) = 8
[pid  2950] poll([{fd=6, events=POLLIN}], 1, -1 <unfinished ...>
[pid  2949] <... uname resumed> {sysname="Linux", nodename="argon", ...}) = 0
[pid  2949] socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC, 0) = 7
[pid  2949] fcntl(7, F_SETFD, FD_CLOEXEC) = 0
[pid  2949] connect(7, {sa_family=AF_LOCAL, sun_path="/var/run/setroubleshoot/setroubleshoot_server"}, 47) = -1 ENOENT (No such file or directory)
[pid  2949] socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 8
[pid  2949] connect(8, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) = 0
[pid  2949] sendto(8, "<11>Jun 16 11:16:11 /usr/bin/sea"..., 105, MSG_NOSIGNAL, NULL, 0) = 105
[pid  2949] getsockname(7, {sa_family=AF_LOCAL, NULL}, [2]) = 0
[pid  2949] getpeername(7, 0x7ffc06859550, 0x7ffc0685954c) = -1 ENOTCONN (Transport endpoint is not connected)
[pid  2949] shutdown(7, SHUT_RDWR)      = 0
[pid  2949] close(7)                    = 0
[pid  2949] write(2, "failed to connect to server: No "..., 55failed to connect to server: No such file or directory
) = 55
[pid  2949] rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x7fba4f419c10}, {0x7fba46edbf60, [], SA_RESTORER|SA_RESTART|SA_NOCLDSTOP, 0x7fba4f419c10}, 8) = 0
[pid  2949] rt_sigaction(SIGHUP, {SIG_DFL, [], SA_RESTORER, 0x7fba4f419c10}, {0x7fba4f789a20, [], SA_RESTORER, 0x7fba4f419c10}, 8) = 0
[pid  2949] rt_sigaction(SIGQUIT, {SIG_DFL, [], SA_RESTORER, 0x7fba4f419c10}, {0x7fba4f789a20, [], SA_RESTORER, 0x7fba4f419c10}, 8) = 0
[pid  2949] rt_sigaction(SIGTERM, {SIG_DFL, [], SA_RESTORER, 0x7fba4f419c10}, {0x7fba4f789a20, [], SA_RESTORER, 0x7fba4f419c10}, 8) = 0
[pid  2949] write(4, "\1\0\0\0\0\0\0\0", 8) = 8
[pid  2949] close(3)                    = 0
[pid  2949] rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
[pid  2949] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
[pid  2949] exit_group(1)               = ?
[pid  2950] +++ exited with 1 +++
+++ exited with 1 +++

Comment 4 Petr Lautrbach 2016-06-16 09:28:40 UTC
It is already fixed in setroubleshoot-3.3.8.1-1.fc24 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-68f69f600e

Please update setroubleshoot-server from updates-testing repository.

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


Note You need to log in before you can comment on or make changes to this bug.