- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
CA Certificates Error when trying to connect with Impala Driver LINUX
- Labels:
-
Apache Impala
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I followed the instructions here for setting up and configuring the Impala driver on Linux. When I test the connection using the isql command line utility I get the following error:
[S1000][unixODBC][Cloudera][DriverSupport] (1140) Unable to load CA certificates from certs file location. Please ensure the file exists, has read permission, and has the correct PEM format.
[ISQL]ERROR: Could not SQLConnect
My odbc.ini looks like this:
[ODBC Data Sources]
[hadoop]
Driver=Cloudera ODBC Driver for Impala 64-bit
AllowHostNameCNMismatch=1
AllowSelfSignedServerCert=1
AuthMec=3
CheckCertRevocation=1
DelegateKrbCreds=0
Host={myhost}
KrbFQDN=_HOST
KrbRealm={myrealm}
KrbServiceName=impala
Min_TLS=1.2
Port=21050
ServicePrincipalCanonicalization=1
SSL=1
TrustedCerts=/opt/cloudera/impalaodbc/lib/64/cacerts.pem
UseKeytab=0
UseOnlySSPI=1
UseSASL=1
UseSystemTrustStore=1
And the permission on /opt/cloudera/imapalaodbc/lib/64/cacerts.pem is set to 777:
-rwxrwxrwx 1 userXXX groupXXX 246K Dec 31 2018 /opt/cloudera/impalaodbc/lib/64/cac erts.pem
Can anyone help resolve this error? The cacerts.pem file has the right permission and the file certainly exists.
Created ‎03-31-2020 10:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oops. Reading the docs it mentions "UseSystemTrustStore" is only valid for windows. Removing this value from by odbc.ini fixes this issue.
Created ‎03-31-2020 10:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oops. Reading the docs it mentions "UseSystemTrustStore" is only valid for windows. Removing this value from by odbc.ini fixes this issue.
