Re: cqlsh problem

CASSANDRA-10959 made the control connection timeout be the same as the connect timeout. This patch is available since 2.2.5, 3.0.3, 3.3. On Fri, Oct 14, 2016 at 11:45 AM, joseph gao wrote: > I've found the problem,

Re: cqlsh problem

I've found the problem, in cqlsh file, find all Cluster 's construct method like ' conn = Cluster(xxx,xxx). At the end, add parameter control_connection_timeout=float(_SOME_MS_VALUE_). As below: conn = Cluster(contact_points=(self.hostname,), port=self.port, cql_version=self.conn.cql_version,

Re: cqlsh problem

This appears in the system log: Caused by: java.lang.RuntimeException: org.apache.cassandra.exceptions.ReadTimeoutException: Operation timed out - received only 2 responses. at org.apache.cassandra.auth.Auth.selectUser(Auth.java:276) ~[apache-cassandra-2.1.14.jar:2.1.14] at

Re: cqlsh problem

I am also getting the same error: cqlsh -u cassandra -p cassandra Connection error: ('Unable to connect to any servers', {'': OperationTimedOut('errors=Timed out creating connection (5 seconds), last_host=None',)}) But it is not consistent. Sometimes I manage to connect. It is random. Using

Re: cqlsh problem

hi, Patric, [image: 内嵌图片 1], netstat -lepunt looks like above 2016-05-27 23:16 GMT+08:00 Patrick McFadin : > Can you do a netstat -lepunt and show the output? If Cassandra is running > you aren't trying to connect to the ip/port it's bound to. > > Patrick > > > On Monday, May

Re: cqlsh problem

Can you do a netstat -lepunt and show the output? If Cassandra is running you aren't trying to connect to the ip/port it's bound to. Patrick On Monday, May 23, 2016, joseph gao wrote: > I used to think it's firewall/network issues too. So I make ufw to be > inactive. I

Re: cqlsh problem

I used to think it's firewall/network issues too. So I make ufw to be inactive. I really don't what's the reason. 2016-05-09 19:01 GMT+08:00 kurt Greaves : > Don't be fooled, despite saying tcp6 and :::*, it still listens on IPv4. > As far as I'm aware this happens on all

Re: cqlsh problem

Don't be fooled, despite saying tcp6 and :::*, it still listens on IPv4. As far as I'm aware this happens on all 2.1 Cassandra nodes, and may just be an oddity of netstat. It would be unrelated to your connection timeout issues, that's most likely related to firewall/network issues. On 9 May 2016

Re: cqlsh problem

It doesn't work ,still using ipv6 [image: 内嵌图片 1] And I already set [image: 内嵌图片 2] Now I'm using 4.1.1 using 9160 port instead of 5.x.x。 Hopefully this could be resolved, Thanks! 2016-03-30 22:13 GMT+08:00 Alain RODRIGUEZ : > Hi Joseph, > > why cassandra using tcp6 for

Re: cqlsh problem

Hi Joseph, why cassandra using tcp6 for 9042 port like : > tcp6 0 0 0.0.0.0:9042:::*LISTEN > if I remember correctly, in 2.1 and higher, cqlsh uses native transport, port 9042 (instead of thrift port 9160) and your clients (if any) are also probably

Re: cqlsh problem

why cassandra using tcp6 for 9042 port like : tcp6 0 0 0.0.0.0:9042:::*LISTEN would this be the problem 2016-03-30 11:34 GMT+08:00 joseph gao : > still have not fixed it . cqlsh: error: no such option: --connect-timeout > cqlsh

Re: cqlsh problem

still have not fixed it . cqlsh: error: no such option: --connect-timeout cqlsh version 5.0.1 2016-03-25 16:46 GMT+08:00 Alain RODRIGUEZ : > Hi Joseph. > > As I can't reproduce here, I believe you are having network issue of some > kind. > > MacBook-Pro:~ alain$ cqlsh

Re: cqlsh problem

Hi Joseph. As I can't reproduce here, I believe you are having network issue of some kind. MacBook-Pro:~ alain$ cqlsh --version cqlsh 5.0.1 MacBook-Pro:~ alain$ echo 'DESCRIBE KEYSPACES;' | cqlsh --connect-timeout=5 --request-timeout=10 system_traces system MacBook-Pro:~ alain$ It's been a few

Re: cqlsh problem

cqlsh version 5.0.1. nodetool tpstats looks good, log looks good. And I used specified port 9042. And it immediately returns fail (less than 3 seconds). By the way where should I use '--connect-timeout', cqlsh seems don't have such parameters. 2016-03-18 17:29 GMT+08:00 Alain RODRIGUEZ

Re: cqlsh problem

protocols are all active, like this: Gossip active : true Thrift active : true Native Transport active: true I used all kinds of address: hostname, localhost, 0.0.0.0, 127.0.0.1, localip, publicip, doesn't work most times. But some time it just work fine 2016-03-17 22:28

cqlsh problem

hi, all cassandra version 2.1.7 When I use cqlsh to connect cassandra, something is wrong Connection error: ( Unable to connect to any servers', {'127.0.0.1': OperationTimedOut('errors=None, last_host=None,)}) This happens lots of times, but sometime it works just fine. Anybody knows why? --

Re: cqlsh problem

Hi, did you try with the address of the node rather than 127.0.0.1 Is the transport protocol used by cqlsh (not sure if it is thrift or binary - native in 2.1) active ? What is the "nodetool info" output ? C*heers, --- Alain Rodriguez - al...@thelastpickle.com France The

Re: cqlsh problem

Is the node fully healthy or rejecting some requests ? What are the outputs for "grep -i "ERROR" /var/log/cassandra/system.log" and "nodetool tpstats"? Any error? Any pending / blocked or dropped messages? Also did you try using distinct ports (9160 for thrift, 9042 for native) - out of

Re: cqlsh problem

Have you started the Cassandra service? sh cassandra On 17-Mar-2016 7:59 pm, "Alain RODRIGUEZ" wrote: > Hi, did you try with the address of the node rather than 127.0.0.1 > > Is the transport protocol used by cqlsh (not sure if it is thrift or > binary - native in 2.1)

Re: cqlsh problem

Of course yes. 2016-03-17 22:35 GMT+08:00 Vishwas Gupta : > Have you started the Cassandra service? > > sh cassandra > On 17-Mar-2016 7:59 pm, "Alain RODRIGUEZ" wrote: > >> Hi, did you try with the address of the node rather than 127.0.0.1 >> >>

Client SSL - cassandra-cli -OK, cqlsh -Problem

I am having a problem connecting via SSL using cqlsh. If I try with the cassandra-cli command: cassandra-cli -ts /etc/cassandra/conf/.truststore -tspw password -h host -p 9160 -tf org.apache.cassandra.cli.transport.SSLTransportFactory it connects fine. If I try with cqlshrc [root@ccluster1 ~]#