You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Yongjun Zhang (JIRA)" <ji...@apache.org> on 2015/03/09 20:51:38 UTC
[jira] [Updated] (HADOOP-11692) Improve authentication failure WARN
message to avoid user confusion
[ https://issues.apache.org/jira/browse/HADOOP-11692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yongjun Zhang updated HADOOP-11692:
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.8.0
Status: Resolved (was: Patch Available)
> 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)