You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2016/10/04 13:49:20 UTC
[jira] [Updated] (ZOOKEEPER-2606)
SaslServerCallbackHandler#handleAuthorizeCallback() should log the
exception
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Yu updated ZOOKEEPER-2606:
------------------------------
Priority: Minor (was: Major)
> SaslServerCallbackHandler#handleAuthorizeCallback() should log the exception
> ----------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2606
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2606
> Project: ZooKeeper
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Minor
>
> {code}
> LOG.info("Setting authorizedID: " + userNameBuilder);
> ac.setAuthorizedID(userNameBuilder.toString());
> } catch (IOException e) {
> LOG.error("Failed to set name based on Kerberos authentication rules.");
> }
> {code}
> On one cluster, we saw the following:
> {code}
> 2016-10-04 02:18:16,484 - ERROR [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:SaslServerCallbackHandler@137] - Failed to set name based on Kerberos authentication rules.
> {code}
> It would be helpful if the log contains information about the IOException.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)