Topic: Tomcat Startup problem on e-smith

[Tom May]

Anyone have any problems getting tomcat to come up automatically on startup?

I have SME 5.5 installed (moved from 5.1) and all works well except that for some reason /etc/init.d/tomcat4 appears not to get run.

I've definitely reviewed my configuration and double checked my scripts and chkconfig setup but no luck!

I finally had to resort to a cron job that checks to see if it is running and starts it up if not - kludges suck!

I tested the 5.1 install and found the same problem. Since I haven't restarted that server since I installed Tomcat4 - over 5 months, I didn't realize it was a problem.

IT DOES work on another machine running RedHat 7.1 Professional... go figure!

It would be nice to have some sort of answer as to way this doesn't work.

Any of you gurus have any comments or ideas? How about Dave H.

[David Helmuth]

I am not sure, but have you tried linking the startup script into run level 7?


It may very well be that the upgrade remove the symlink.

Try:

ln -s /etc/rc.d/init.d/tomcat4 /etc/rc.d/rc7.d/S80tomcat4

-Dave

[Kevin Baker]

What is the significance of "S80" in "S80tomcat4".  I have to name another service... and don't know what all the S#{servicename} values mean.

I am working on start jboss as a service... I  think I have most of it going.. modeled after all the Tomcat stuff.

[Des Dougan]

"S" means it's a start-up script, and "80" is a sequence number, so that services are started in the correct order. Look in /etc/rc.d/rc7.d for an illustration.

Des Dougan