Return-Path: 
 <hdfs-issues-return-110919-apmail-hadoop-hdfs-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-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 BE59417EC9
	for <apmail-hadoop-hdfs-issues-archive@minotaur.apache.org>;
 Fri, 27 Feb 2015 18:43:06 +0000 (UTC)
Received: (qmail 22249 invoked by uid 500); 27 Feb 2015 18:43:05 -0000
Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org
Received: (qmail 22151 invoked by uid 500); 27 Feb 2015 18:43:05 -0000
Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-issues@hadoop.apache.org>
List-Id: <hdfs-issues.hadoop.apache.org>
Reply-To: hdfs-issues@hadoop.apache.org
Delivered-To: mailing list hdfs-issues@hadoop.apache.org
Received: (qmail 21858 invoked by uid 99); 27 Feb 2015 18:43:05 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2015 18:43:05 +0000
Date: Fri, 27 Feb 2015 18:43:05 +0000 (UTC)
From: "Yongjun Zhang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12778280.1425062538000.36201.1425062585472@Atlassian.JIRA>
In-Reply-To: <JIRA.12778280.1425062538000@Atlassian.JIRA>
References: <JIRA.12778280.1425062538000@Atlassian.JIRA>
 <JIRA.12778280.1425062538699@arcas>
Subject: [jira] [Created] (HDFS-7857) Incomplete information in WARN message
 caused user confusion
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

Yongjun Zhang created HDFS-7857:
-----------------------------------

             Summary: Incomplete information in WARN message caused user confusion
                 Key: HDFS-7857
                 URL: https://issues.apache.org/jira/browse/HDFS-7857
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: namenode
            Reporter: Yongjun Zhang
            Assignee: Yongjun Zhang


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)