Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Why do I have to do a setenforce 0 to cluster tomcat on Scientific Linux using mod_proxy

I am using Scientific Linux release 6.2 and trying to get mod_proxy working with httpd and tomcat.

I want to have two tomcat nodes running on the box and so I need to change the 2nd tomcat node ajp port to something diff then 8009 like 8109, But once I change the port on Scientific Linux it stops working but I have found if I do a

setenforce 0

it works then.

Can someone please tell me what I am doing and if anyone knows a better what to get tomcat nodes working on Scientific Linux without doing a setenforce 0


share|improve this question
up vote 1 down vote accepted

Your SELinux profile is blocking connections to non-standard ports. You'll need to change the ruleset to allow tomcat on the new port if you wish to continue running in enforcing mode.

share|improve this answer
can you please tell me how to do that? – techsjs2012 Dec 4 '12 at 20:20
Step one, learn SElinux. Step two, learn how to write SELinux policies (aka rulesets). I'm in the middle of step one. – John Dec 5 '12 at 13:11

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.