[
https://issues.apache.org/jira/browse/ZOOKEEPER-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated ZOOKEEPER-2040:
-------------------------------------
Attachment: ZOOKEEPER-2040.002.patch
[~rgs], would you please consider including Steve's patch in the upcoming 3.4.7
release? It's a one-line change to a log message, and it can be very useful
while troubleshooting.
I'm uploading a patch v002 file. This just takes Steve's earlier patch and
regenerates it with the {{--no-prefix}} option to satisfy the ZooKeeper
test-patch.sh script. This patch file can apply to both trunk and branch-3.4.
> 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,
> ZOOKEEPER-2040.002.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)
