I have gigs of logs, and I have them pouring out into my tty. They all look like this:
audit(1156908691.156:14): avc: granted { execmem } for pid=2508 comm="java" scontext=user_u:system_r:unconfined_t:s0 tcontext=user_u:system_r:unconfined_t:s0 tclass=process

When I stop that java process, the logs stop, but I need that process running. I configured SELinux to allow Java execstack but nothing changed. I disabled SELinux and it still does it.

What can I do to stop this? How can I tell if SELinux is still running?

if you're getting those errors, selinux is definitely still running. try adding selinux=disabled to the grub / lilo boot options and see how it performs after the next boot.

I hadn't rebooted, so it was definately still running. My next question is, how do I stop these messages while SELinux is still running?

I have allow_java_execstack checked, which it is allowing but it logs every single one of them, and there are hundreds of these a minute.


Mar 6 11:04:48 localhost kernel: audit(1173197088.765:11245): avc: granted { execmem } for pid=2996 comm="java" scontext=root:system_r:initrc_t:s0 tcontext=root:system_r:initrc_t:s0 tclass=process

I have gigs of logs, and I have them pouring out into my tty.
To console is a system setting (as in "dmesg -n int"): see "man dmesg".


I configured SELinux to allow Java execstack but nothing changed. I disabled SELinux and it still does it. (..) I have allow_java_execstack checked, which it is allowing but it logs every single one of them, and there are hundreds of these a minute.
I would advise against stopping SELinux because you then fall back to "old school" methods. That itself isn't bad provided your box is properly hardened but SELinux is a security *enhancement* so in this case "more ismore". If you can't run SELinux in enforcing mode during testing, at least run it in permissive mode. It will still be loaded to spit out AVC (access vector cache) messages so you can keep tabs on what *should* be adjusted RSN.

So the console thing being covered with "dmesg", the source of the logging can hopefully be uncovered running "audit2why" on the AVC messages. Since it's granted I suspect there is a boolean or audit2allow rule somewhere which makes messages of type "granted" get logged.

I figured it out. I updated some of the SELinux stuff with yum. I noticed there was some Java changes in the change log, and my version was a year old, so I updated it. It solved the problem.