[jira] [Commented] (ZOOKEEPER-2344) Provide more diagnostics/stack traces on SASL Auth failure
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422594#comment-15422594 ] Rakesh R commented on ZOOKEEPER-2344: - I am moving this out to 3.4.10 for now. > 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.7, 3.5.1 >Reporter: Steve Loughran > Fix For: 3.5.3, 3.6.0, 3.4.10 > > > 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)
[jira] [Commented] (ZOOKEEPER-2344) Provide more diagnostics/stack traces on SASL Auth failure
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135488#comment-15135488 ] Raul Gutierrez Segales commented on ZOOKEEPER-2344: --- [~cnauroth], [~steve_l]: lets target this for 3.4.9 - thanks! > 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.7, 3.5.1 >Reporter: Steve Loughran > Fix For: 3.4.9, 3.5.2, 3.6.0 > > > 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)
[jira] [Commented] (ZOOKEEPER-2344) Provide more diagnostics/stack traces on SASL Auth failure
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058428#comment-15058428 ] Flavio Junqueira commented on ZOOKEEPER-2344: - [~ste...@apache.org] I've just had to do this for Kafka and it was not too bad, but that might have to do with code familiarity. If you could be a bit more specific about the cases that you found we could do more, then I'd appreciate if you could list them here so that I can get a better idea of how to fix it. Thanks for reporting this issue. > 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)
[jira] [Commented] (ZOOKEEPER-2344) Provide more diagnostics/stack traces on SASL Auth failure
[ 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)
[jira] [Commented] (ZOOKEEPER-2344) Provide more diagnostics/stack traces on SASL Auth failure
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058509#comment-15058509 ] Chris Nauroth commented on ZOOKEEPER-2344: -- bq. Tell me which branch you'd like patches against and I see what I can do too Hi [~ste...@apache.org]. In general, patches are flowing into trunk and branch-3.5 right now. I expect any trunk patch is also applicable to branch-3.5. Bug fixes can also flow down to the branch-3.4 maintenance line depending on the circumstances. For small patches to improve logging and debugging like you're suggesting, I expect they'd be great candidates for inclusion in branch-3.4. You'll likely need to create a different patch file for branch-3.4. > 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.7, 3.5.1 >Reporter: Steve Loughran > Fix For: 3.4.8, 3.5.2, 3.6.0 > > > 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)
[jira] [Commented] (ZOOKEEPER-2344) Provide more diagnostics/stack traces on SASL Auth failure
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058504#comment-15058504 ] Flavio Junqueira commented on ZOOKEEPER-2344: - Thanks [~ste...@apache.org]. bq. Tell me which branch you'd like patches against and I see what I can do too I'd say 3.4 because that's what most folks are using at the moment, 3.5 and trunk > 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.7, 3.5.1 >Reporter: Steve Loughran > Fix For: 3.4.8, 3.5.2, 3.6.0 > > > 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)
