Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 99E2D200B2B for ; Tue, 28 Jun 2016 20:02:58 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 98B62160A6C; Tue, 28 Jun 2016 18:02:58 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id EB089160A28 for ; Tue, 28 Jun 2016 20:02:57 +0200 (CEST) Received: (qmail 50564 invoked by uid 500); 28 Jun 2016 18:02:57 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 50554 invoked by uid 99); 28 Jun 2016 18:02:57 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Jun 2016 18:02:57 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 050FF2C14DC for ; Tue, 28 Jun 2016 18:02:57 +0000 (UTC) Date: Tue, 28 Jun 2016 18:02:57 +0000 (UTC) From: =?utf-8?Q?Oliv=C3=A9r_Szab=C3=B3_=28JIRA=29?= To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-17170) Logfeeder should read every logs with non-root user MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 28 Jun 2016 18:02:58 -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 updated AMBARI-17170: ---------------------------------- Description:=20 ambari logs generated with ambari-server user / ambari-server group permiss= ions. 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 amb= ari-server group (not in hadoop), so does not matter logfeeder and ambari-s= erver on the same group, if the ambari server log files are not in the comm= on hadoop group Also we can hit different permission issues also if any of the services log= s is only readable by the actual service user was: ambari logs generated with ambari-server user / ambari-server group permiss= ions. 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 amb= ari-server group (not in hadoop), so does not matter logfeeder and ambari-s= erver on the same group, if the ambari server log files are not in the comm= on hadoop group Also we can hit different permission issues also i > 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=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)