[
https://issues.apache.org/jira/browse/ZOOKEEPER-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058487#comment-15058487
]
Steve Loughran commented on ZOOKEEPER-2344:
-------------------------------------------
I'll add some stacks as I go along. the ones where stack traces get lost are
one-line fixes; anything for diagnostics harder -I think the thing to know
there is what information to provide in server-side and client-side reports.
At a guess
# keytabs
# user being used
# location of JAAS conf file and/or dump of the actual config
Tell me which branch you'd like patches against and I see what I can do too
> Provide more diagnostics/stack traces on SASL Auth failure
> ----------------------------------------------------------
>
> Key: ZOOKEEPER-2344
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2344
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client, server
> Affects Versions: 3.4.5
> Reporter: Steve Loughran
>
> When Kerberos decides it doesn't want to work, the JRE libraries provide some
> terse and unhelpful error messages.
> The only way to debug the problem is (a) to have complete stack traces and
> (b) as much related information as possible.
> Zookeeper could do more here. Currently too much of the code loses stack
> traces; sometimes auth errors aren't reported back to the client (the
> connection is closed) +others
> Everyone who has tried to diagnose kerberos problems will appreciate
> improvements here
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
