hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yongjun Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-7857) Incomplete information in WARN message caused user confusion
Date Fri, 27 Feb 2015 18:43:05 GMT
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)

Mime
View raw message