Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 29 Jun 2016 10:20:37 +0000 (UTC)
From: =?utf-8?Q?Oliv=C3=A9r_Szab=C3=B3_=28JIRA=29?= <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12977633.1465570458000.50.1467195637539@Atlassian.JIRA>
In-Reply-To: <JIRA.12977633.1465570458000@Atlassian.JIRA>
References: <JIRA.12977633.1465570458000@Atlassian.JIRA> <JIRA.12977633.1465570458337@arcas>
Subject: [jira] [Resolved] (AMBARI-17170) Logfeeder should read every
 service/ambari logs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 29 Jun 2016 10:20:39 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-17170?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oliv=C3=A9r Szab=C3=B3 resolved AMBARI-17170.
-----------------------------------
    Resolution: Fixed

committed to trunk:
{code:java}
commit 259279cd67ba2626d68d3565982729769b9f5ea9
Author: oleewere <oleewere@gmail.com>
Date:   Tue Jun 28 20:04:11 2016 +0200

    AMBARI-17170. Logfeeder should read every service/ambari logs (oleewere=
)
{code}
comitted to branch-2.4:
{code:java}
commit 64613ae9b7bb76e5d248a0d353f5fcde0941f301
Author: oleewere <oleewere@gmail.com>
Date:   Tue Jun 28 20:04:11 2016 +0200

    AMBARI-17170. Logfeeder should read every service/ambari logs (oleewere=
)
{code}

> Logfeeder should read every service/ambari logs
> -----------------------------------------------
>
>                 Key: AMBARI-17170
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17170
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch, ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Oliv=C3=A9r Szab=C3=B3
>            Assignee: Oliv=C3=A9r Szab=C3=B3
>             Fix For: 2.4.0
>
>
> ambari logs generated with ambari-server user / ambari-server group permi=
ssions.
> In case of non-root ambari server installs, ambari-server user should be =
in Hadoop service group, although that happens, most of the logs still in a=
mbari-server group (not in hadoop), so does not matter logfeeder and ambari=
-server on the same group, if the ambari server log files are not in the co=
mmon hadoop group
> Also we can hit different permission issues also if any of the services l=
ogs is only readable by the actual service user


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