You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2015/11/17 23:58:10 UTC

[jira] [Updated] (AMBARI-13926) AMS log file not getting updated or created on fresh deploy

     [ https://issues.apache.org/jira/browse/AMBARI-13926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Siddharth Wagle updated AMBARI-13926:
-------------------------------------
    Summary: AMS log file not getting updated or created on fresh deploy  (was: AMS log file not getting created)

> AMS log file not getting updated or created on fresh deploy
> -----------------------------------------------------------
>
>                 Key: AMBARI-13926
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13926
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.1.2
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13926.patch
>
>
> The AMS logs were not getting created because the wrong log4j.properties were getting picked up. 
> Fix
> Moved the code that had a dependency on the jar that supplied the wrong log4j.properties to src/test. Hence, the jar will not be packaged during AMS jar assembly.



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