[
https://issues.apache.org/jira/browse/RANGER-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956261#comment-14956261
]
Don Bosco Durai commented on RANGER-692:
----------------------------------------
The solution should have been simple. Just moving the log4j.xml to
/etc/ranger/admin/conf should have solved the problem, because
/etc/ranger/admin/conf is in the class path.
But for some reason, it didn't work for me. I think it is because we are using
embedded tomcat. The log4j might be using the classpath from the initial
classloader.
Anyway, if someone is able to do basic experiment and make it work, then it
would be good. The same issue might happen Ranger KMS also
> RangerAdmin should use log4j.xml from the conf folder.
> ------------------------------------------------------
>
> Key: RANGER-692
> URL: https://issues.apache.org/jira/browse/RANGER-692
> Project: Ranger
> Issue Type: Improvement
> Components: admin
> Affects Versions: 0.5.1
> Reporter: Don Bosco Durai
> Fix For: 0.6.0
>
>
> Currently log4j.xml for RangerAdmin is in ews/webapp/WEB-INF/log4j.xml. We
> should come with a design where it is in the conf folder and can be
> customized by the user. If customized, then we should not overwrite on
> upgrade or reinstall.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
