On Tue, December 20, 2011 09:49, Daniel J Walsh wrote:
This means somebody is executing a chcon with a context that the kernel does not understand. I would look for a chcon in an init script.
I tried this and did not find any in the init scripts:
find /etc/rc.d -print | xargs grep chcon