You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Olivér Szabó (JIRA)" <ji...@apache.org> on 2016/06/29 10:20:37 UTC
[jira] [Resolved] (AMBARI-17170) Logfeeder should read every
service/ambari logs
[ https://issues.apache.org/jira/browse/AMBARI-17170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olivér Szabó resolved AMBARI-17170.
-----------------------------------
Resolution: Fixed
committed to trunk:
{code:java}
commit 259279cd67ba2626d68d3565982729769b9f5ea9
Author: oleewere <ol...@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 <ol...@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ér Szabó
> Assignee: Olivér Szabó
> Fix For: 2.4.0
>
>
> ambari logs generated with ambari-server user / ambari-server group permissions.
> 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 ambari-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 common hadoop group
> Also we can hit different permission issues also if any of the services logs is only readable by the actual service user
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)