On Thursday 23 Apr 2009 10:29:39 Ritesh Raj Sarraf wrote: > And this is what is loggeed into syslog: > > > Apr 23 10:27:46 champaran setroubleshoot: [rpc.ERROR] attempt to open > server connection failed: No such file or directory
I've tried purge and re-install but still, no luck. I'm attaching a screenshot
of the error, probably that'll explain more.
Manually firing sealert -l with the violation id also fails with the same
message that "cannot connect to the server".
dpkg -l shows that the /var/run folder is created.
/var
/var/lib
/var/lib/setroubleshoot
/var/log
/var/log/setroubleshoot
/var/run
/usr/share/icons/hicolor/96x96/apps/setroubleshoot_red_icon.png
/usr/share/icons/hicolor/96x96/apps/setroubleshoot_icon.png
I'm assuming that setroubleshootd will create its pid file when a violation is
raised and it is automatically started. I verified with ps, setroubleshootd is
running, but there's no pid file in /var/run. That's the problem.
Ritesh
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part.
