CentOS

I have recently added support to fcgi with httpd and after that I'm full of those messages in the

/var/log/messages file:

[quote]Apr 7 14:19:47 secure setroubleshoot: SELinux is preventing /bin/ps from search access on the directory 2(r). For complete SELinux messages. run sealert -l 54675ba6-bca8-414f-85ad-d6557d55023f[/quote][Moderator edit: Changed [i]code[/i] to [i]quote[/i] tags to wrap long line.]

[code]$ sealert -l 54675ba6-bca8-414f-85ad-d6557d55023f
Entity: line 53: parser error : Input is not proper UTF-8, indicate encoding !
Bytes: 0x85 0x3C 0x2F 0x74
<tpath>2(r)</tpath>
^
failed to connect to server: xmlParseDoc() failed
[/code]

Can someone give an idea?

Thank you Very Much.

[quote]
woow wrote:
I have recently added support to fcgi with httpd and after that I'm full of those messages in the
[/quote]

How did you go about doing that? Seems you have broken something. A google on the [url=https://www.google.com/search?q=sealert+Entity+line++parser+error++Input+is+not+proper+UTF-8%2C+indicate+encoding+!&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a&safe=active#q=sealert+Entity+line++parser+error++Input+is+not+proper+UTF-8,+indicate+encoding+!&hl=en&safe=active&client=firefox-a&hs=gYW&tbo=1&rls=org.mozilla:en-US:unofficial&prmd=imvns&tbas=0&source=lnt&sa=X&ei=1jyAT5izK8jIgQfPwMTdBw&ved=0CBkQpwUoAA&bav=on.2,or.r_gc.r_pw.r_qf.,cf.osb&fp=d5b0fb9cd82eac&biw=1293&bih=762]error[/url] turns up some obsolete bug reports, but if the search is limited to the last year, nothing recent except this thread.

yes, actually after some reboots the problem solved automatic!
still get some messages of ps which I managed to restrict via modifing the policy.. :-)

ty