How to resolve the "GSS Initiate Failed" error when trying to connect to Cloudera Impala Datasource in TDV?
Article ID: KB0070721
Updated On:
| Products | Versions |
|---|---|
| TIBCO Data Virtualization | All Supported versions |
Description
When trying to connect to the Cloudera Impala data source using Kerberos authentication, the error
"com.cloudera.impala.jdbc42.internal.apache.thrift.transport.TTransportException: GSS initiate failed" may be encountered.
This article describes the steps that can be used to resolve this issue.
"com.cloudera.impala.jdbc42.internal.apache.thrift.transport.TTransportException: GSS initiate failed" may be encountered.
This article describes the steps that can be used to resolve this issue.
Issue/Introduction
How to resolve the "GSS Initiate Failed" error when trying to connect to Cloudera Impala Data source in TIBCO Data Virtualization (TDV)?
Environment
Linux
Resolution
If debugging for Kerberos is enabled (Launch Studio and navigate to Administration-> Configuration->Server->Configuration->Security->Authentication->Kerberos), the following entry can be observed in the logs for the GSS Initiate error:
GSS initiate failed :
Entered Krb5Context.initSecContext with state=STATE_NEW
Service ticket not found in the subject
If SPN is generated with a fully qualified hostname and the Cloudera manager is using the entry without fully qualified name, it results in the DNS being a mess and your machine not knowing its own name.
In order to resolve this issue, remove the fully qualified hostname entry from /etc/host file on the Linux environment.
GSS initiate failed :
Entered Krb5Context.initSecContext with state=STATE_NEW
Service ticket not found in the subject
If SPN is generated with a fully qualified hostname and the Cloudera manager is using the entry without fully qualified name, it results in the DNS being a mess and your machine not knowing its own name.
In order to resolve this issue, remove the fully qualified hostname entry from /etc/host file on the Linux environment.
Feedback
Yes
No
Powered by
