部署grails app时stacktrace.log的问题

rao*_*ski 9 deployment grails tomcat log4j stack-trace

我有部署grails应用程序的问题.

我得到以下异常:

log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: stacktrace.log (Permission denied)
    at java.io.FileOutputStream.openAppend(Native Method)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
    at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
    at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
    at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
    at org.apache.log4j.spi.OptionHandler$activateOptions.call(Unknown Source)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:40)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:120)
    at org.codehaus.groovy.grails.plugins.logging.Log4jConfig.createFullstackTraceAppender(Log4jConfig.groovy:177)
    at org.codehaus.groovy.grails.plugins.logging.Log4jConfig.this$2$createFullstackTraceAppender(Log4jConfig.groovy)
    at org.codehaus.groovy.grails.plugins.logging.Log4jConfig$this$2$createFullstackTraceAppender.callCurrent(Unknown Source)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:44)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:145)
    at org.codehaus.groovy.grails.plugins.logging.Log4jConfig.configure(Log4jConfig.groovy:145)
    at org.codehaus.groovy.grails.web.util.Log4jConfigListener.contextInitialized(Log4jConfigListener.java:62)
    at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4135)
    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4630)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
    at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
    at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
    at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:445)
    at org.apache.catalina.core.StandardService.start(StandardService.java:519)
    at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
May 25, 2011 11:16:54 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
Run Code Online (Sandbox Code Playgroud)

我在配置中对记录器的设置如下所示:

log4j = { 
    appenders {
        rollingFile name: "stacktrace", maxFileSize: 1024, file: "/var/www/logs/myapp-stacktrace.log"
     }
 }
Run Code Online (Sandbox Code Playgroud)

我还尝试使用log4j = {appenders {'null'name:"stacktrace"}}禁用记录器

为tomcat-user设置了此目录的权限

-rwxr--r-- 1 tomcat6 root 0 May 24 18:38 myapp-stacktrace.log
Run Code Online (Sandbox Code Playgroud)

根本没有成功...感谢任何反馈和帮助!!

小智 8

我遇到了与Grails 1.3.7类似的问题并发现它修复了它(通过将堆栈跟踪日志推入标准日志记录目录)

log4j = {
    appenders {
    rollingFile name: "stacktrace", maxFileSize: 1024, file: "/var/logs/piws-stacktrace.log"
    ....
Run Code Online (Sandbox Code Playgroud)

  • 我们最后写了:`file:(System.getProperty('catalina.base')?:'target')+'/ logs/itsfeature.log'` - 用于生产和dev的bot. (2认同)

And*_*ewW 6

查看有关将Grails应用程序部署到Tomcat的官方文档,网址http://www.grails.org/Deployment/#Tomcat.

引用相关部分......

"请注意,在默认设置下,Grails将尝试向tomcat目录写入某些文件,通常是stacktrace.log和h2数据库.您的Tomcat目录可能与root用户/组一起安装,而Tomcat服务器以用户身份运行tomcat6.这将导致您的应用程序无法以写权限错误启动.更改Grails生产设置,以便将这些文件写入具有正确权限的目录的其他位置或更改Tomcat目录的所有者(对于Unix:/ var/lib/tomcat6)到tomcat6(或者你使用TOMCAT6_USER设置设置的任何tomcat用户). "

您可以使用sudo chown tomcat6 /var/lib/tomcat6更改所有者(如果需要,替换运行tomcat的用户和正在编写日志的目录),这是大多数情况下最简单和最合适的解决方案.


hvg*_*des 1

检查磁盘空间(长镜头)并尝试 chmodding 到 777 只是为了验证其权限问题。如果是,您要么没有以 tomcat 用户身份运行 tomcat,要么您的目录已关闭...