[
https://issues.apache.org/jira/browse/AMBARI-17617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376093#comment-15376093
]
Hudson commented on AMBARI-17617:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #5299 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/5299/])
AMBARI-17617. Set default log level for Ranger KMS to INFO (gborad via
(sgunturi:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1253e9be03572f27308e4c49ea65b89c2a2882d1])
*
ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/configuration/kms-log4j.xml
> Set default log level for Ranger KMS to INFO
> --------------------------------------------
>
> Key: AMBARI-17617
> URL: https://issues.apache.org/jira/browse/AMBARI-17617
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Deepak Sharma
> Assignee: Gautam Borad
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17617.patch
>
>
> Kms log file is getting bigger till 18 GB , causing No space left on device
> for inode.
> Problem is :
> 1. by default debug log is generated in the kms.log fle
> 2. there is not split in log file if there is over flow of logs in kms.log
> file like other access audit logs file and xa_portal logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
