Bug 121940

Summary:	tomcat start failes - no write access to /var/run/tomcat5.pid
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Markus Meisters <mmeisters>
Component:	Java	Assignee:	Daniel Bornkessel <dbornkessel>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	RC 4
Target Milestone:	---
Hardware:	i586
OS:	SUSE Other
Whiteboard:
Found By:	IS&T	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Markus Meisters 2005-10-10 11:43:48 UTC

Hello,

old problem again :)

Please create a var/run/tomcat/ directory which is owned by tomcat and create
the pidfile tomcat5.pid in this directory, because /var/run/tomcat5.pid ->
permission denied.

Comment 1 Dale Ogilvie 2005-10-19 08:06:46 UTC

Also JAVA_HOME is not set, so even if the change to the tomcat5.pid directory is made, the start still fails. The tomcat user has no JAVA_HOME environment set, and the default /usr/lib/java doesn't point to a jdk.

I created a $CATALINA_HOME/conf/tomcat5.conf containing

JAVA_HOME=/usr/lib/jvm/java
export JAVA_HOME

And modified the @@@TCCONF@@@ line in catalina.sh to point to this file.

Comment 2 Thomas Schmidt 2005-11-22 14:42:48 UTC

similar to bug #134572.

Comment 3 Daniel Bornkessel 2005-11-23 15:43:30 UTC

Fixed the tomcat5.pid issue.
For the JAVA_HOME part, please follow Bug #134572


Cheers,
Daniel

Comment 4 Bryce Nesbitt 2006-08-07 03:12:26 UTC

As of August 6th, 2006, I'm not seeing a fix for this.  Was this relased as a patch to SUSE 10.0, or scheduled for a future release?

linux:/var/log/tomcat5/base # cat start.log
Using CATALINA_BASE:   /usr/share/tomcat5
Using CATALINA_HOME:   /usr/share/tomcat5
Using CATALINA_TMPDIR: /usr/share/tomcat5/temp
Using JAVA_HOME:       /usr/lib/jvm/java
/usr/share/tomcat5/bin/catalina.sh: line 284: /var/run/tomcat5.pid: Permission denied

Comment 5 Bryce Nesbitt 2006-08-07 03:13:15 UTC

Not fixed here.

Comment 6 Daniel Bornkessel 2006-08-07 12:49:47 UTC

Hi Bryce.
For SL, there are only security patches -- for the rest you can use the 10.1 package. We do not provide patches for SL packages if it is not a security update ... sorry.

Regards,
Daniel