Red Hat Bugzilla – Bug 281621
Setroubleshoot seems to be broken with latest audit
Last modified: 2007-11-30 17:12:15 EST
Description of problem:
/var/run/audit_events does not exist on my system (assuming no longer), but
/var/run/audispd_events exists, so I changed the path.
Version-Release number of selected component (if applicable):
Working setroubleshoot like in the past. Because nevertheless setroubleshoot
2007-09-07 00:43:06,055 [avc.ERROR] exception MemoryError:
Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/setroubleshoot/avc_audit.py", line
578, in run
if not record.read_from_fd(self.audit_socket.fileno()):
File "/usr/lib/python2.5/site-packages/setroubleshoot/avc_audit.py", line 80,
new_data = os.read(fd, self.length - len(self.body))
Can somebody please fix setroubleshoot soon?
Created attachment 189311 [details]
Changes the path of the socket
yes, we are aware the audit package and setroubleshoot is out of sync.
Unfortunately it's more than just the path of the socket. The protocol on the
socket changed too. We're working to update setroubleshoot to work with the new
protcol and an update should be available shortly. Thank you for reporting this.
Current versions of audit and setroubleshoot should resolve this issue.
the above two versions are known to work together, although I believe the issue
was resolved as early as setroubleshoot-1.10.3-1.fc8