Hi,
I solved my problem.
I had: log4j.appender.*.file=${applicationRoot}/logs/*.log
but when I made:
log4j.appender.*.file=/usr/share/tomcat/webapps/firstsyst/logs/*.log
then it works.
Why is the variable ${applicationRoot}not set ?
with best regards,
Rafal
----- Original Message -----
From: "Shane Beasley" <[EMAIL PROTECTED]>
To: "Turbine Users List" <[email protected]>
Sent: Thursday, April 27, 2006 10:55 PM
Subject: Re: Log4j doesn't create log files
Rafal Markut wrote:
I use Turbine 2.3.2 with Torque 3.1.1. In that turbine there is
log4j-1.2.12.jar.
It doesn't create on my linux server the log files (e.g.
turbine.log).
First, check your Tomcat log files (e.g. $CATALINA_HOME/logs). It might
have some useful information about the cause.
This particular problem has happened to me before, for two unrelated
reasons.
I. UNIX FILE PERMISSIONS
Likely, Tomcat runs under a particular user account. Make sure that the
operating system will allow that account to create the logs by doing
EITHER of the following:
- grant +rwx access on $CATALINA_HOME/webapps/MyWebApp
- create and grant +rwx access on $CATALINA_HOME/webapps/MyWebApp/logs
The latter is better because it restricts access to the "logs" directory
only. However, on a development machine, the former might be acceptable.
II. JAVA SECURITY MANAGER
It may be that the Java Security Manager is stopping you. At the
minimum, you'll need the following in your policy file (e.g.
$CATALINA_HOME/conf/catalina.policy):
grant codeBase "file:${catalina.home}/webapps/MyWebApp/-" {
permission java.io.FilePermission
"${catalina.home}/webapps/industryinforespdb/logs", "write";
permission java.io.FilePermission
"${catalina.home}/webapps/industryinforespdb/logs/-", "write";
};
I've found that if it forbids you from creating the log files, it might
forbid you from doing other things as well. There are numerous ways to
fix those. You might find this to be helpful in that endeavor:
http://www.oreilly.com/catalog/javasec2/chapter/ch01.html
Note: Adding "-Djava.security.debug=all" to the Tomcat startup command
will add tons of useful diagnostics to your logs, which you can use to
hunt down permissions problems on a case-by-case basis.
Shane
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
