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 "Aaron T. Myers (JIRA)" <ji...@apache.org> on 2013/03/04 23:45:13 UTC
[jira] [Commented] (HADOOP-9358) "Auth failed" log should include
exception string
[ https://issues.apache.org/jira/browse/HADOOP-9358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592761#comment-13592761 ]
Aaron T. Myers commented on HADOOP-9358:
----------------------------------------
+1 pending Jenkins.
> "Auth failed" log should include exception string
> -------------------------------------------------
>
> Key: HADOOP-9358
> URL: https://issues.apache.org/jira/browse/HADOOP-9358
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc, security
> Affects Versions: 3.0.0, 2.0.4-beta
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hadoop-9385.txt
>
>
> Currently, when authentication fails, we see a WARN message like:
> {code}
> 2013-02-28 22:49:03,152 WARN ipc.Server (Server.java:saslReadAndProcess(1056)) - Auth failed for 1.2.3.4:12345:null
> {code}
> This is not useful to understand the underlying cause. The WARN entry should additionally include the exception text, eg:
> {code}
> 2013-02-28 22:49:03,152 WARN ipc.Server (Server.java:saslReadAndProcess(1056)) - Auth failed for 1.2.3.4:12345:null (GSS initiate failed [Caused by GSSException: Failure unspecified at GSS-API level (Mechanism level: Request is a replay (34))])
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira