You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Davy Xu (Jira)" <ji...@apache.org> on 2022/07/02 08:07:00 UTC

[jira] [Commented] (IMPALA-11404) When impalad enables kerberos service , impala-shell failed to access it

    [ https://issues.apache.org/jira/browse/IMPALA-11404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561725#comment-17561725 ] 

Davy Xu commented on IMPALA-11404:
----------------------------------

Thanks for your advice. [~wzhou]
[~tarmstrong@cloudera.com]Please take a look at this question, thanks.

> When impalad enables kerberos service , impala-shell failed to access it
> ------------------------------------------------------------------------
>
>                 Key: IMPALA-11404
>                 URL: https://issues.apache.org/jira/browse/IMPALA-11404
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Clients
>    Affects Versions: Impala 4.0.0
>            Reporter: Davy Xu
>            Priority: Major
>
> When running the impala service with kerberos enabled on SUSE12 system, impala-shell fails to access impalad, and the error message is as follows:
> Error connecting: TTransportException, Could not start SASL: Error in sasl_client_start (-1) SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure.  Minor code may provide more information (No Kerberos credentials available)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org