From user-return-51414-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org Thu May 26 09:06:24 2016 Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 659A7198F1 for ; Thu, 26 May 2016 09:06:24 +0000 (UTC) Received: (qmail 37431 invoked by uid 500); 26 May 2016 09:06:22 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 37362 invoked by uid 500); 26 May 2016 09:06:22 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 37350 invoked by uid 99); 26 May 2016 09:06:21 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2016 09:06:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 3EB1DC7477 for ; Thu, 26 May 2016 09:06:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.429 X-Spam-Level: * X-Spam-Status: No, score=1.429 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id PtgXu9n5790b for ; Thu, 26 May 2016 09:06:19 +0000 (UTC) Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 214EF5F235 for ; Thu, 26 May 2016 09:06:18 +0000 (UTC) Received: by mail-oi0-f49.google.com with SMTP id k23so114812207oih.0 for ; Thu, 26 May 2016 02:06:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=bNj9efYb/JeBjIQ9FCdw7AkI+XPpO1mqyFqz08EGBYA=; b=E0DJoOfv9+DLLBa/t2s2IAdRlfbe4R1IueXHhKPT2S1TjQm4ELKLZx257cs6TiNi7L Uq5OpoLLJNRVlavvWqvOYTzits0M66g2F5JW/MKqpAyyQrQnfwc9xy8ojk5f+QCjfsD7 rYoRPufZslEg569lxp7d/PW4GqKqOOvNsMp3UfYnldCv4/XIX3N6Sqe39+0SZ8Q5HUOU WxiSXx1v6Q6q4ejhKnR+jAL+uf6sWGfDJGxkyprGdRDmyOSKG7rIUNyK3vLsRihFYzJO umEcD0qvq4gV7Cp371nuJzDLkeKtR+TBPhLxvjPBd1EjVPBokuAmYYmgs0F+G3rwudsH 1shw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=bNj9efYb/JeBjIQ9FCdw7AkI+XPpO1mqyFqz08EGBYA=; b=GX37tCpG5Bvrs14al3j1N6wcNd+jCRKfOKYZtfvFTbUH6LY2ZNAHEI96PmqhYuDBhX 4zXFbWvOebRCIg25jFWG7nmPxU97Y4BPTfbUVJdzWcjlkqpUNG/IeHH77Kh2sdvqks3N qh5DxuNvtBisucfYgAIzhXP4crz6OKp8H25G16piJtS5RI27r0nceBlCj+PzUG/pHFtU sXLi6K3p15x3AYK6Mz0Eg+PWQ6bG+TGrN09vVRtQIy4tIZbNWfeavy904owkkxkTwl7Y H3M6c/ixqfQxafuoiz/jQhLn/1iyGjmOdc6tv4lujS4FtQ9OgLuk6peY632C9Uw8dcnC RJ3g== X-Gm-Message-State: ALyK8tKyvZ+E5TvM1gVpu8dS+u5fkSU94EJ/6cpu9ab3fO9SEtMxy3ii024kwPwuo7B9BSZ3V/+FC8so8DWG+w== MIME-Version: 1.0 X-Received: by 10.157.6.164 with SMTP id 33mr5168472otx.164.1464253576949; Thu, 26 May 2016 02:06:16 -0700 (PDT) Received: by 10.157.37.83 with HTTP; Thu, 26 May 2016 02:06:16 -0700 (PDT) In-Reply-To: <8E858C3A39F0D046B420FBA6F75448C086D3264A@blreml501-mbx.china.huawei.com> References: <8E858C3A39F0D046B420FBA6F75448C086D31F11@blreml501-mbx.china.huawei.com> <8E858C3A39F0D046B420FBA6F75448C086D31F27@blreml501-mbx.china.huawei.com> <8E858C3A39F0D046B420FBA6F75448C086D3264A@blreml501-mbx.china.huawei.com> Date: Thu, 26 May 2016 14:36:16 +0530 Message-ID: Subject: Re: How to enable log4j properties in hbase From: Mahesh Sankaran To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=94eb2c04f74e50b9700533bb1a2d --94eb2c04f74e50b9700533bb1a2d Content-Type: text/plain; charset=UTF-8 yes i have added above properties. On Thu, May 26, 2016 at 1:10 PM, ashish singhi wrote: > Forgot to say before, I hope you have added > "org.apache.hadoop.hbase.security.access.AccessController" class in the > master, rs and region coprocessor configuration in hbase-site.xml. > > Regards, > Ashish > > -----Original Message----- > From: Mahesh Sankaran [mailto:sankarmahesh37@gmail.com] > Sent: 26 May 2016 12:33 > To: user@hbase.apache.org > Subject: Re: How to enable log4j properties in hbase > > Hi Ashish, > > Yes i have restarted and tried hbase authorization operation. Still facing > same issue. > > Thanks, > > Mahesh > > On Wed, May 25, 2016 at 2:04 PM, ashish singhi > wrote: > > > Hi, > > Did you restart the HBase service ? > > Did you try any HBase operation ? > > > > Regards, > > Ashish > > > > -----Original Message----- > > From: Mahesh Sankaran [mailto:sankarmahesh37@gmail.com] > > Sent: 25 May 2016 13:32 > > To: user@hbase.apache.org > > Subject: Re: How to enable log4j properties in hbase > > > > Hi Ashish, > > > > Thanks for your quick reply. > > I uncommented mentioned property. But it is not working. > > > > Thanks, > > Mahesh > > > > On Wed, May 25, 2016 at 1:10 PM, ashish singhi > > > > wrote: > > > > > Uncomment > > > > > > "log4j.logger.SecurityLogger.org.apache.hadoop.hbase.security.access.AccessController=TRACE" > > > this line in log4j.properties file. > > > > > > Regards, > > > Ashish > > > > > > -----Original Message----- > > > From: Mahesh Sankaran [mailto:sankarmahesh37@gmail.com] > > > Sent: 25 May 2016 13:01 > > > To: user@hbase.apache.org > > > Subject: Re: How to enable log4j properties in hbase > > > > > > Hi, > > > > > > And also am using hbase-1.2.0 from cdh 5.7 > > > > > > Thanks, > > > Mahesh > > > > > > On Wed, May 25, 2016 at 12:56 PM, Mahesh Sankaran < > > > sankarmahesh37@gmail.com> > > > wrote: > > > > > > > Hi All, > > > > > > > > I have configured hbase authorization in my hbase cluster. Now i > > > > want to enable audit logs for hbase authorization to monitor users. > > > > For that i did following changes. > > > > > > > > 1.vim /etc/hbase/conf/log4j.properties > > > > > > > > log4j.rootLogger=${hbase.root.logger} > > > > hbase.root.logger=INFO,console > > > > log4j.appender.console=org.apache.log4j.ConsoleAppender > > > > log4j.appender.console.target=System.err > > > > log4j.appender.console.layout=org.apache.log4j.PatternLayout > > > > log4j.appender.console.layout.ConversionPattern=%d{yy/MM/dd > > > > HH:mm:ss} %p > > > > %c{2}: %m%n > > > > > > > > log4j.logger.SecurityLogger=TRACE, RFAS > > > > log4j.additivity.SecurityLogger=false > > > > log4j.appender.RFAS=org.apache.log4j.RollingFileAppender > > > > log4j.appender.RFAS.File=${log.dir}/audit/SecurityAuth-hbase.audit > > > > log4j.appender.RFAS.layout=org.apache.log4j.PatternLayout > > > > log4j.appender.RFAS.layout.ConversionPattern=%d{ISO8601} %p %c: > > > > %m%n log4j.appender.RFAS.MaxFileSize=${max.log.file.size} > > > > log4j.appender.RFAS.MaxBackupIndex=${max.log.file.backup.index} > > > > > > > > > > > > 2.Restarted my hbase cluster. SecurityAuth-hbase.audit file is > > > > created but there is no content inside that file. > > > > > > > > Kindly help me to enable audit logs for hbase authorization. > > > > > > > > Note: I am using cloudera > > > > > > > > Thanks, > > > > > > > > Mahesh > > > > > > > > > > --94eb2c04f74e50b9700533bb1a2d--