SASL Error: no mechanism available: No worthy mechs found
See original GitHub issueWhen trying to connect to an Impala Server, the following error happens:
>>> from impala.dbapi import connect
>>> conn = connect(host='xxxxxxxxxx', port=21050, user='xxxxxx', password='xxxxxx', auth_mechanism='LDAP')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/local/lib/python2.6/site-packages/impala/dbapi.py", line 82, in connect
auth_mechanism=auth_mechanism)
File "/usr/local/lib/python2.6/site-packages/impala/hiveserver2.py", line 586, in connect
transport.open()
File "/usr/local/lib/python2.6/site-packages/thrift_sasl/__init__.py", line 72, in open
message=("Could not start SASL: %s" % self.sasl.getError()))
thrift.transport.TTransport.TTransportException: Could not start SASL: Error in sasl_client_start (-4) SASL(-4): no mechanism available: No worthy mechs found
Even with all LDAP dependencies installed.
Issue Analytics
- State:
- Created 8 years ago
- Comments:46 (14 by maintainers)
Top Results From Across the Web
SASL(-4): no mechanism available: No worthy mechs found ...
The following error is encountered when trying to connect to the CDH cluster using the MicroStrategy DB query tool or the command line...
Read more >SASL authentication failure: No worthy mechs found
I'm running it in a Hyper-V VM if that's a factor (likely not). ... failure: No worthy mechs found," or "SASL authentication failed; ......
Read more >"No worthy mechs found" when trying to relay email to Gmail ...
Just installing postfix doesn't pull in the cyrus-sasl-plain package ... (this changed from Fedora 26). – maxschlepzig. Apr 3, 2018 at 8:51.
Read more >python cannot connect hiveserver2 - Stack Overflow
You are missing some dependencies, make sure you install cyrus-sasl-devel and cyrus-sasl-gssapi : On an RHEL-based distro: sudo yum install cyrus-sasl-devel ...
Read more >Error in sasl_client_start (-4) SASL(-4): no mechanism available
pyhs2.connect(host='localhost',port=10000,authMechanism="PLAIN" ... Error in sasl_client_start (-4) SASL(-4): no mechanism available: No worthy mechs found
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
for what it’s worth, this solved it for me
running python in Docker
I have this working now on a CentOS install of Anaconda. I think that the critical aspect in getting this functioning was installing several sasl related packages on CentOS itself.
I was unable to compile SASL on Windows (or any of the CentOS) packages, so leveraged the CentOS VM to connect to the Kerberos cluster.
After successfully running a kinit, I am able to connect with the following string:
LDAP conection works as well: