Return-Path: 
 <common-issues-return-80618-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id EB1E617E6F
	for <apmail-hadoop-common-issues-archive@minotaur.apache.org>;
 Tue, 10 Mar 2015 14:43:44 +0000 (UTC)
Received: (qmail 85302 invoked by uid 500); 10 Mar 2015 14:43:44 -0000
Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org
Received: (qmail 85223 invoked by uid 500); 10 Mar 2015 14:43:44 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Reply-To: common-issues@hadoop.apache.org
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 85072 invoked by uid 99); 10 Mar 2015 14:43:44 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Mar 2015 14:43:44 +0000
Date: Tue, 10 Mar 2015 14:43:44 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12778280.1425062538000.51444.1425998624179@Atlassian.JIRA>
In-Reply-To: <JIRA.12778280.1425062538000@Atlassian.JIRA>
References: <JIRA.12778280.1425062538000@Atlassian.JIRA>
 <JIRA.12778280.1425062538699@arcas>
Subject: [jira] [Commented] (HADOOP-11692) Improve authentication failure
 WARN message to avoid user confusion
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/HADOOP-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354988#comment-14354988 ] 

Hudson commented on HADOOP-11692:
---------------------------------

FAILURE: Integrated in Hadoop-Hdfs-trunk #2060 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/2060/])
HADOOP-11692. Improve authentication failure WARN message to avoid user confusion. Contributed by Yongjun Zhang. (yzhang: rev de1101cb5be2d8efd0ef4945f64ccfe7cbd01049)
* hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/ipc/Server.java
* hadoop-common-project/hadoop-common/CHANGES.txt


> Improve authentication failure WARN message to avoid user confusion
> -------------------------------------------------------------------
>
>                 Key: HADOOP-11692
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11692
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: ipc
>            Reporter: Yongjun Zhang
>            Assignee: Yongjun Zhang
>              Labels: supportability
>             Fix For: 2.8.0
>
>         Attachments: HDFS-7857.001.patch
>
>
> Lots of the following messages appeared in NN log:
> {quote}
> 2014-12-10 12:18:15,728 WARN SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for <ipAddress>:39838:null (DIGEST-MD5: IO error acquiring password)
> 2014-12-10 12:18:15,728 INFO org.apache.hadoop.ipc.Server: Socket Reader #1 for port 8020: readAndProcess from client <ipAddress> threw exception [org.apache.hadoop.ipc.StandbyException: Operation category READ is not supported in state standby]
> ......
> SecurityLogger.org.apache.hadoop.ipc.Server: Auth failed for <ipAddress>:39843:null (DIGEST-MD5: IO error acquiring password)
> 2014-12-10 12:18:15,790 INFO org.apache.hadoop.ipc.Server: Socket Reader #1 for port 8020: readAndProcess from client <ipAddress> threw exception [org.apache.hadoop.ipc.StandbyException: Operation category READ is not supported in state standby]
> {quote}
> The real reason of failure is the second message about StandbyException,
> However, the first message is confusing because it talks about "DIGEST-MD5: IO error acquiring password".
> Filing this jira to modify the first message to have more comprehensive information that can be obtained from {{getCauseForInvalidToken(e)}}.
> {code}
>        try {
>           saslResponse = processSaslMessage(saslMessage);
>         } catch (IOException e) {
>           rpcMetrics.incrAuthenticationFailures();
>           // attempting user could be null
>           AUDITLOG.warn(AUTH_FAILED_FOR + this.toString() + ":"
>               + attemptingUser + " (" + e.getLocalizedMessage() + ")");
>           throw (IOException) getCauseForInvalidToken(e);
>         }
> {code}



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