I have Fedora 6 and apache-tomcat-5.5.25 installed in /usr/local. and jdk1.5.0_09 in same /usr/local. I have set jdk path in etc/profile and is showing correctly. I have set JAVA_HOME as /usr/local/jdk1.5.0_09.
but when I am starting tomcat by command- su - tomcat -c /usr/local/apache-tomcat-5.5.25/bin/startup.sh
it is showing following error- Using CATALINA_BASE: /usr/local/apache-tomcat-5.5.25 Using CATALINA_HOME: /usr/local/apache-tomcat-5.5.25 Using CATALINA_TMPDIR: /usr/local/apache-tomcat-5.5.25/temp Using JRE_HOME: /usr/local/jdk1.5.0_09 touch: cannot touch `/usr/local/apache-tomcat-5.5.25/logs/catalina.out': Permission denied /usr/local/apache-tomcat-5.5.25/bin/catalina.sh: line 273: /usr/local/apache-tomcat-5.5.25/logs/catalina.out: Permission denied
Check the permission and ownership of /usr/local/apache-tomcat-5.5.25/logs. Did you use root to install it? If the ownership is root, then you may need to change your CATALINA_BASE to e.g. /home/tomcat/logs.
SCJP 5.0, SCWCD 1.4, SCBCD 1.3, SCDJWS 1.4
My Blog
It's not a bad idea to create a tomcat user and group ID and chown the tomcat logs, work, temp and webapp directories. That way you can launch Tomcat in a secure environnment without things being so secure that Tomcat itself can't get anything done.
There are some installable packages that do all that and more, but there's not a definitive standard architecture that they all adhere to.
One of the most odious afflictions that Business has inflicted on the modern English language is "pro-active". Most of the time it's simply redundantly used in place of the simple old word "active". And a good deal of the rest of the time it means "You're not overworked enough yet, so go out and find more!"
"Aish Sk", please see you private messages regarding an important administrative matter.
Regarding your question, I have a few for you:
1) What account are you logged in under?
2) What account are you running Tomcat under?
3) What is the ownership of the directory in question? Run "ls -al /usr/local/tomcat/logs/" and post the results.
Essentially, the account used to run Tomcat doesn't have write access to /usr/local/tomcat/logs/.
1
