setroubleshootd socket directory is missing so sealert does not work

Bug #354196 reported by pacificnw
6
Affects Status Importance Assigned to Milestone
setroubleshoot (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: setroubleshoot

Ubuntu 9.04 Jaunty server x86 beta

sapere@seubuntu9:~$ sudo apt-cache policy setroubleshoot
setroubleshoot:
  Installed: 2.0.12-2
  Candidate: 2.0.12-2
  Version table:
 *** 2.0.12-2 0
        500 http://us.archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

Expected:
-------------
sudo sealert -l da87160b-4c6f-42f8-8c3a-56e11470e8e2 (to work, removed correct output)

Observed defect:
----------------------
sapere@seubuntu9:~$ sealert -l da87160b-4c6f-42f8-8c3a-56e11470e8e2
failed to connect to server: No such file or directory

/var/run/setroubleshoot directory is missing so socket is not created for sealert
and has to be created manually and setroubleshootd restarted.

pacificnw (ssmyth)
description: updated
summary: - setroubleshoot socket directory is missing so sealert does not work
+ setroubleshootd socket directory is missing so sealert does not work
Revision history for this message
Scott Kitterman (kitterman) wrote :

I've put a potential fix into my PPA: https://launchpad.net/~kitterman/+archive/ppa - I just uploaded it, so it will be awhile before it's there.

Please let me know if this solves the problem (I don't use SELinux, so I can't test this myself).

Changed in setroubleshoot (Ubuntu):
assignee: nobody → Scott Kitterman (kitterman)
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Scott Kitterman (kitterman) wrote :

Bug 354197 blocks progress on this, so it's not possible to fix it for Karmic. In the mean time, if it's otherwise working.

Changed in setroubleshoot (Ubuntu):
assignee: Scott Kitterman (kitterman) → nobody
status: In Progress → Triaged
Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 354196] Re: setroubleshootd socket directory is missing so sealert does not work

this, so it's not possible to fix it for
>Karmic. In the mean time, if it's otherwise working.
.... manually recreating /var/run/setroubleshoot should work around the
problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.