You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Shwetha G S (JIRA)" <ji...@apache.org> on 2013/09/19 11:34:04 UTC

[jira] [Commented] (OOZIE-905) Clarify and improve Oozie logging configuration and streaming

    [ https://issues.apache.org/jira/browse/OOZIE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771736#comment-13771736 ] 

Shwetha G S commented on OOZIE-905:
-----------------------------------

Oozie 3.3.2 has the following error in catalina.out and then logs are not written to oozie.log. Is this fixed?
log4j:WARN Failed to set property [rollingPolicy] to value "org.apache.oozie.util.OozieRollingPolicy".
log4j:WARN Please set a rolling policy for the RollingFileAppender named 'oozie'
log4j:ERROR No output stream or file set for the appender named [oozie].
log4j:WARN No appenders could be found for logger (org.apache.jasper.compiler.JspRuntimeContext).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
                
> Clarify and improve Oozie logging configuration and streaming
> -------------------------------------------------------------
>
>                 Key: OOZIE-905
>                 URL: https://issues.apache.org/jira/browse/OOZIE-905
>             Project: Oozie
>          Issue Type: Improvement
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>            Priority: Minor
>             Fix For: 3.3.0
>
>         Attachments: OOZIE-905.patch
>
>
> Oozie's logging configuration has a number of "restrictions" which are not listed anywhere and aren't all obvious.  There are also some improvements to the streaming log code that can be made to simplify it and make it more robust.  Additionally, having the ability to automatically delete old log files can help prevent problems from having too many files in the same directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira