[
https://issues.apache.org/jira/browse/AMBARI-17170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-17170:
----------------------------------
Description:
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 i
was:
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
> Logfeeder should read every logs with non-root user
> ---------------------------------------------------
>
> 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.1
>
>
> 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 i
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
