Linux

Ask something
Discussion Locked

Tomcat not starting

0 helpful
3 replies

by cp409sd

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Solaris 9 machine that has apache and tomcat installed. (actually both apache and tomcat came bundled in the Solaris 9 installation). Both apache and tomcat were working just fine. I just used JASS (Solaris Security Toolkit) from Sun to harden my system which will be directly exposed to the internet. It seems to have broken tomcat though. I know that I can back out of the changes that JASS made to my system, but want to keep them, and just fix the problem with tomcat.

JASS originally renamed both the /etc/apache/httpd.conf and /etc/apache/tomcat.conf, to disable them. I renamed them back to what they should be, but it seems that only apache starts.

Doing a ps -ef before I used JASS and after shows that a certain java process is not running. This process is:

/usr/java/bin/java -classpath /usr/apache/tomcat/bin/bootstrap.jar:/usr/java/li

After the '.../java/li' I can't see any more of the line. It seems like this is probably the problem, but I am not sure where to begin in fixing it. Any help would be greatly appreciated.

3 replies

by marco milo

I've Solaris 9 too, but i've not used JASS, and my Apache/Tomcat works fine.

i've just a couple of hints:

1) chech that in your /etc/apache/httpd.conf one of those 2 lines at the end of the file are uncommented:

include /etc/apache/jserv.conf (to enable servlets and jsp in Apache)

and

include /etc/apache/tomcat.conf (to enable the Tomcat standalone server)

2)check if the network port used by tomcat is still available, maybe JASS modified the network access from outside whilesecuring your system

3) maybe that JASS has modified your JAVA_HOME directory?

at the moment i've no other ideas...

bye.

by cp409sd

Sorry...I forgot about this question. I actually ended up figuring out the problem.

The problem was that when JASS disabled the nobody user, by putting /bin/noshell in the /etc/passwd, it broke tomcat. For whatever reason, the nobody user is used in the tomcat startup process. I simply removed this info from the /etc/passwd, and it works properly now.

Thanks for the help though.

This discussion is closed to new replies.