Bugzilla – Bug 134572
Tomcat won't start
Last modified: 2005-11-25 16:34:56 UTC
On SUSE 10.0 Retail Tomcat won't start due to 2 issues. 1) On line 117 in /etc/rc.d/tomcat5 -L needs to be added to chown command. Original line test -d "$dir" && chown -R --dereference tomcat:tomcat "$dir" 2>/dev/null || true needs to be changed to test -d "$dir" && chown -L -R --dereference tomcat:tomcat "$dir" 2>/dev/null || true 2) Tomcat is su-ed to tomcat thus unable to create pid file in /var/run Following will remedy the situation: # touch /var/run/tomcat5.pid # chown tomcat:tomcat /var/run/tomcat5.pid The two above commands shoud be best added to /etc/rc.d/tomcat5
Thanks! Reassigning to current maintainer...
Thanks for the bug report and the included tips. The problems you described are errors and will be fixed. However, on my system (and on systems of others I asked) the tomcat still starts -- regardless of this problems. Does tomcat start with only those changes you described above? If so I can not re-create the bug ... Is it possible to attach /usr/share/tomcat5/logs/catalina.out of the broken configuration? That could help me narrow down the problem. Thanks, Daniel
I was actually installing the open-xchange rpm when I came across the Tomcat issue. I was following the steps in /usr/share/doc/packages/open-xchange/README.SUSE There are several lines related to Tomcat changes. My system is operational now and I'm unfortunately not able to provide you with the required logs nor I have other system to install from scratch. Please look at the open-xchage readme in Tomcat section for some possible causes.
I did the changes proposed in the first comment -- thanks. Ralf, do you know anything about the problem regarding tomcat does not start when the instructions in the open-xchange README.SUSE are followed?
No, I have not heard of any such problems. For me the instructions in the Readme worked (I had to make smaller adjustments to the file recently, but IIRC they were unrelated to tomcat).
Right now I have to assume that the tomcat problems were connected to a wrong JAVA_HOME variable as described in Bug #129641 , which was indeed a problem.\ As this problem is fixed now, I will close this bug. If somebody still encounters the same problem, please feel free to re-open the bug. Best regards, Daniel