You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/09/16 18:12:34 UTC
[jira] [Commented] (ZOOKEEPER-2040) Server to log underlying cause
of SASL connection problems
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135651#comment-14135651 ]
Hadoop QA commented on ZOOKEEPER-2040:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12669084/ZOOKEEPER-2040-log-SASL-errors-001.patch
against trunk revision 1623916.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2338//console
This message is automatically generated.
> Server to log underlying cause of SASL connection problems
> ----------------------------------------------------------
>
> Key: ZOOKEEPER-2040
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2040
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.4.6
> Reporter: Steve Loughran
> Attachments: ZOOKEEPER-2040-log-SASL-errors-001.patch
>
>
> When you have SASL connectivity problems, you spend time staring at logs —ideally logs with stack traces.
> ZK server can help here by including the stack traces when there is a SASL auth problem, rather than just giving the text of the exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)