Apache Tomcat Splash Screen Not Coming Up

AussieAndrew · 07-23-2013, 02:38 AM

Hi guys,

I've set up my CentOS server with Java 1.6.0_24 and Apache Tomcat 7.0.42. I then successfully (I thought) started Tomcat, and went to a browser to see if I could access it. I've tried putting the IP Address directly into the browser and the same but with :8080 after it, but it always times out.

Has anyone got any ideas what I've missed?

Regards,
Andrew

druuna · 07-23-2013, 02:59 AM

Is iptables running?

Run

Code:

iptables -L -n

to see if iptables is running. You can do a quick test by stopping iptables and trying to connect:

Code:

service iptables stop
# to start again
service iptables start

If you haven't added rules to allow this traffic you will not be able to connect.

You don't provide any info on how you have set up tomcat, so your mileage mat vary, but have a look here: Install Tomcat 7 on CentOS / RHEL (especially step 6).

SAbhi · 07-23-2013, 03:05 AM

Two things I would like to confirm :
1.did you tried running http://tomcat/ ?
2.did you check if the tomcat process running after you started it ?

AussieAndrew · 07-23-2013, 03:14 AM

Thanks for your quick responses. Here is what I have found:

iptables is running
I believe tomcat is running after I run the startup.sh file. I used ps -ef | grep java as I read elsewhere online, and the result looks correct to my untrained eye.
I wasn't sure what you meant by /tomcat/ so I tried http://<ip>/tomcat/ which didn't work.

I am now looking at step 6 of the tutorial you suggested. I'll be surprised if Tomcat isn't setup right, as I followed a step-by-step guide as part of setting up a program called OpenGTS which I'm trying to use this server for.

Any further suggestions?

Regards,
Andrew

druuna · 07-23-2013, 03:20 AM

Quote:

Originally Posted by AussieAndrew

iptables is running

I am now looking at step 6 of the tutorial you suggested.

Did you try stopping iptables first and checked if you can connect without a time-out? Would be nice to know iptables is actually the culprit.

AussieAndrew · 07-23-2013, 03:23 AM

Hi Druuna,

Sorry I misunderstood your first instructions. When I stop iptables I do indeed get the correct splash screen. I take it this means that something in the iptables configuration needs changing so that this connection gets let through?

Regards,
Andrew

druuna · 07-23-2013, 03:38 AM

Quote:

Originally Posted by AussieAndrew

Hi Druuna,

Sorry I misunderstood your first instructions. When I stop iptables I do indeed get the correct splash screen. I take it this means that something in the iptables configuration needs changing so that this connection gets let through?

Regards,
Andrew

Correct! You now established that iptables is blocking the connection.

You can now try step 6 from the previous posted link.

AussieAndrew · 07-23-2013, 03:46 AM

Thanks for your help! I'll be back if I can't figure it out