Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not start SASL: Error in sasl_client_start (-4) SASL(-4) #41

Open
kotharisonal opened this issue Mar 4, 2015 · 3 comments
Open

Comments

@kotharisonal
Copy link

I have CentOs 6.6 running Python 2.6. I installed python 2.7 in a separate localtion /usr/local/bin for being able to use the pyh2 hive client. I installed all the additional packages needed. Eg. all the SASL packages are available:

[tap@localhost test]$ rpm -qa | grep sasl
cyrus-sasl-gssapi-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-lib-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-md5-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-plain-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-devel-2.1.23-15.el6_6.1.x86_64

But I still see the following error:
/usr/local/lib/python2.7/site-packages/setuptools-12.3-py2.7.egg/pkg_resources/init.py:1224: UserWarning: /home/tap/.python-eggs is writable by group/others and vulnerable to attack when used with get_resource_filename. Consider a more secure location (set with .set_extraction_path or the PYTHON_EGG_CACHE environment variable).
Traceback (most recent call last):
File "testPktFlow2.py", line 7, in
database='default') as conn:
File "build/bdist.linux-x86_64/egg/pyhs2/init.py", line 7, in connect
File "build/bdist.linux-x86_64/egg/pyhs2/connections.py", line 45, in init
File "build/bdist.linux-x86_64/egg/pyhs2/cloudera/thrift_sasl.py", line 66, in open
thrift.transport.TTransport.TTransportException: Could not start SASL: Error in sasl_client_start (-4) SASL(-4): no mechanism available: No worthy mechs found

@zklopman
Copy link
Collaborator

zklopman commented Mar 4, 2015

Hello,

this error message:

/usr/local/lib/python2.7/site-packages/setuptools-12.3-py2.
7.egg/pkg_resources/init.py:1224: UserWarning: /home/tap/.python-eggs is
writable by group/others and vulnerable to attack when used with
get_resource_filename. Consider a more secure location (set with
.set_extraction_path or the PYTHON_EGG_CACHE environment variable).

means that the permissions on the file .python-eggs are too open. Try
running this:

chmod 007 /home/tap/.python-eggs

which will prevent others from accessing the nest and see if that solves
your problem.

bye,

Zachi

On Wed, Mar 4, 2015 at 4:11 PM, kotharisonal [email protected]
wrote:

I have CentOs 6.6 running Python 2.6. I installed python 2.7 in a separate
localtion /usr/local/bin for being able to use the pyh2 hive client. I
installed all the additional packages needed. Eg. all the SASL packages are
available:

[tap@localhost test]$ rpm -qa | grep sasl
cyrus-sasl-gssapi-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-lib-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-md5-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-plain-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-devel-2.1.23-15.el6_6.1.x86_64

But I still see the following error:

/usr/local/lib/python2.7/site-packages/setuptools-12.3-py2.7.egg/pkg_resources/
init.py:1224: UserWarning: /home/tap/.python-eggs is writable by
group/others and vulnerable to attack when used with get_resource_filename.
Consider a more secure location (set with .set_extraction_path or the
PYTHON_EGG_CACHE environment variable).
Traceback (most recent call last):
File "testPktFlow2.py", line 7, in
database='default') as conn:
File "build/bdist.linux-x86_64/egg/pyhs2/init.py", line 7, in connect
File "build/bdist.linux-x86_64/egg/pyhs2/connections.py", line 45, in
init
File "build/bdist.linux-x86_64/egg/pyhs2/cloudera/thrift_sasl.py", line
66, in open
thrift.transport.TTransport.TTransportException: Could not start SASL:
Error in sasl_client_start (-4) SASL(-4): no mechanism available: No worthy
mechs found


Reply to this email directly or view it on GitHub
#41.

@kotharisonal
Copy link
Author

Thanks but I am stalled by the Error in SASL client. How do I resolve that.

Sent from my iPhone

On 4 Mar, 2015, at 2:14 pm, Zachi Klopman [email protected] wrote:

Hello,

this error message:

/usr/local/lib/python2.7/site-packages/setuptools-12.3-py2.
7.egg/pkg_resources/init.py:1224: UserWarning: /home/tap/.python-eggs is
writable by group/others and vulnerable to attack when used with
get_resource_filename. Consider a more secure location (set with
.set_extraction_path or the PYTHON_EGG_CACHE environment variable).

means that the permissions on the file .python-eggs are too open. Try
running this:

chmod 007 /home/tap/.python-eggs

which will prevent others from accessing the nest and see if that solves
your problem.

bye,

Zachi

On Wed, Mar 4, 2015 at 4:11 PM, kotharisonal [email protected]
wrote:

I have CentOs 6.6 running Python 2.6. I installed python 2.7 in a separate
localtion /usr/local/bin for being able to use the pyh2 hive client. I
installed all the additional packages needed. Eg. all the SASL packages are
available:

[tap@localhost test]$ rpm -qa | grep sasl
cyrus-sasl-gssapi-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-lib-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-md5-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-plain-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-devel-2.1.23-15.el6_6.1.x86_64

But I still see the following error:

/usr/local/lib/python2.7/site-packages/setuptools-12.3-py2.7.egg/pkg_resources/
init.py:1224: UserWarning: /home/tap/.python-eggs is writable by
group/others and vulnerable to attack when used with get_resource_filename.
Consider a more secure location (set with .set_extraction_path or the
PYTHON_EGG_CACHE environment variable).
Traceback (most recent call last):
File "testPktFlow2.py", line 7, in
database='default') as conn:
File "build/bdist.linux-x86_64/egg/pyhs2/init.py", line 7, in connect
File "build/bdist.linux-x86_64/egg/pyhs2/connections.py", line 45, in
init
File "build/bdist.linux-x86_64/egg/pyhs2/cloudera/thrift_sasl.py", line
66, in open
thrift.transport.TTransport.TTransportException: Could not start SASL:
Error in sasl_client_start (-4) SASL(-4): no mechanism available: No worthy
mechs found


Reply to this email directly or view it on GitHub
#41.


Reply to this email directly or view it on GitHub.

@zklopman
Copy link
Collaborator

zklopman commented Mar 5, 2015

Hi,

If you have fixed the permissions issue and it is still a problem, you
might check the resolution of a similar problem at
#19 .

bye,

Zachi

On Wed, Mar 4, 2015 at 6:38 PM, kotharisonal [email protected]
wrote:

Thanks but I am stalled by the Error in SASL client. How do I resolve that.

Sent from my iPhone

On 4 Mar, 2015, at 2:14 pm, Zachi Klopman [email protected]
wrote:

Hello,

this error message:

/usr/local/lib/python2.7/site-packages/setuptools-12.3-py2.
7.egg/pkg_resources/init.py:1224: UserWarning: /home/tap/.python-eggs
is
writable by group/others and vulnerable to attack when used with
get_resource_filename. Consider a more secure location (set with
.set_extraction_path or the PYTHON_EGG_CACHE environment variable).

means that the permissions on the file .python-eggs are too open. Try
running this:

chmod 007 /home/tap/.python-eggs

which will prevent others from accessing the nest and see if that solves
your problem.

bye,

Zachi

On Wed, Mar 4, 2015 at 4:11 PM, kotharisonal [email protected]
wrote:

I have CentOs 6.6 running Python 2.6. I installed python 2.7 in a
separate
localtion /usr/local/bin for being able to use the pyh2 hive client. I
installed all the additional packages needed. Eg. all the SASL
packages are
available:

[tap@localhost test]$ rpm -qa | grep sasl
cyrus-sasl-gssapi-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-lib-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-md5-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-plain-2.1.23-15.el6_6.1.x86_64
cyrus-sasl-devel-2.1.23-15.el6_6.1.x86_64

But I still see the following error:

/usr/local/lib/python2.7/site-packages/setuptools-12.3-py2.7.egg/pkg_resources/
init.py:1224: UserWarning: /home/tap/.python-eggs is writable by
group/others and vulnerable to attack when used with
get_resource_filename.
Consider a more secure location (set with .set_extraction_path or the
PYTHON_EGG_CACHE environment variable).
Traceback (most recent call last):
File "testPktFlow2.py", line 7, in
database='default') as conn:
File "build/bdist.linux-x86_64/egg/pyhs2/init.py", line 7, in connect
File "build/bdist.linux-x86_64/egg/pyhs2/connections.py", line 45, in
init
File "build/bdist.linux-x86_64/egg/pyhs2/cloudera/thrift_sasl.py", line
66, in open
thrift.transport.TTransport.TTransportException: Could not start SASL:
Error in sasl_client_start (-4) SASL(-4): no mechanism available: No
worthy
mechs found


Reply to this email directly or view it on GitHub
#41.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub
#41 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants