There is a bug with the new option in Centos 5 called setroubleshoot.

The bug spins the program over and over causing high memory and sometimes CPU use. Unfortunately there is no permanent fix yet, but if you see something like this high in your daily process log:

/usr/bin/python -E /usr/sbin/setroubleshootd

To fix for now you simply have to restart the process:

/etc/init.d/setroubleshoot restart

or set up a cron to restart the service as needed.

Was this post helpful?