[jira] [Commented] (CASSANDRA-10781) Connection Timed Out When PasswordAuthenticator Enabled on Cubieboard

["Sam Tunnicliffe (JIRA)" <ji...@apache.org>]

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

Sam Tunnicliffe commented on CASSANDRA-10781:
---------------------------------------------

Are you unable to connect at all, or is the problem intermittent? When using the default superuser credentials (i.e. the {{cassandra}} user), reads from the internal auth tables are performed with {{LOCAL_QUORUM}} consistency level. For any other credentials, reads are performed at cl {{ONE}}. Check the {{system.log}} on the node you're connecting to verify that it is this read which is timing out. 

If you are able to connect sometimes, you should follow the guidance [here|http://docs.datastax.com/en/cassandra/2.2/cassandra/configuration/secureConfigNativeAuth.html] and create an alternative superuser role to use for login.

> Connection Timed Out When PasswordAuthenticator Enabled on Cubieboard
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-10781
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10781
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Working Environment: Cubie-board A80, running Ubuntu Linaro 14.04 (which is download from http://dl.cubieboard.org/model/cc-a80/Image/ubuntu-linaro)
> Cassandra version: Version 2.1.7 (from http://downloads.datastax.com/community/dsc-cassandra-2.1.7-bin.tar.gz)
> Also tested with 2.2.3 version
>            Reporter: Xiangyu Zhang
>
> Connect using default username and password ./cqlsh 192.168.10.26 -u cassandra -p cassandra), it will timed out:Connection error: ('Unable to connect to any servers', {'192.168.10.26': OperationTimedOut('errors=Timed out creating connection, last_host=None',)}). This happens when PasswordAuthenticator is enabled. When it is disabled, database can be connected. Might be some dependency issue that causing the authentication timed out, checked that openssl properly installed. Is there a possible way to track down why the authentication timed out?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)