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

Hudson commented on AMBARI-15197:
---------------------------------

ABORTED: Integrated in Ambari-trunk-Commit #4561 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4561/])
AMBARI-15197. Make use of log dir properties while installing (gautam: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ac35c6dd83fc61ff0ea35a454a78f9df54b57aec])
* 
ambari-server/src/main/resources/common-services/RANGER/0.4.0/configuration/ranger-env.xml
* 
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/configuration/kms-env.xml
* 
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/setup_ranger_xml.py
* 
ambari-server/src/main/resources/common-services/RANGER/0.4.0/package/scripts/ranger_service.py
* 
ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-ugsync-site.xml
* 
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/package/scripts/kms.py


> Make use of log dir properties while installing Ranger
> ------------------------------------------------------
>
>                 Key: AMBARI-15197
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15197
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Gautam Borad
>            Assignee: Gautam Borad
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15197.patch
>
>
> *PROBLEM:*
> The ranger_admin_log_dir and ranger_usersync_log_dir settings under "Advanced 
> ranger-env" doesn't do anything.  
> It is not using the value given in above properties to create / set the log 
> directory for Ranger service. Fix it for HDP-2.3. 
> *PROPOSED SOLUTION:*
> Need to use these properties and create / set log dir and set correct 
> permissions for log dir for Ranger. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to