Re: Can not connect with cqlsh to something different than localhost

2014-12-08 Thread Richard Snowden
Ah! That did the trick! Thanks Sam! On Mon, Dec 8, 2014 at 8:49 PM, Sam Tunnicliffe wrote: > rpc_address (or rpc_interface) is used for client connections, > listen_address is for inter-node communication. > > > > On 8 December 2014 at 19:21, Richard Snowden > wrote: > >> $ netstat -ntl | gr

Re: Can not connect with cqlsh to something different than localhost

2014-12-08 Thread Sam Tunnicliffe
rpc_address (or rpc_interface) is used for client connections, listen_address is for inter-node communication. On 8 December 2014 at 19:21, Richard Snowden wrote: > $ netstat -ntl | grep 9042 > tcp6 0 0 127.0.0.1:9042 :::* > LISTEN > > ("listen_address" not set in cassand

Re: Can not connect with cqlsh to something different than localhost

2014-12-08 Thread Richard Snowden
$ netstat -ntl | grep 9042 tcp6 0 0 127.0.0.1:9042 :::*LISTEN ("listen_address" not set in cassandra.yaml) Even with "listen_address: 192.168.111.136" I get: $ netstat -ntl | grep 9042 tcp6 0 0 127.0.0.1:9042 :::*

Re: Can not connect with cqlsh to something different than localhost

2014-12-08 Thread Michael Dykman
The difference is what interface your service is listening on. What is the output of $ netstat -ntl | grep 9042 On Mon, 8 Dec 2014 07:21 Richard Snowden wrote: > I left listen_address blank - still I can't connect (connection refused). > > "cqlsh" -> OK > "cqlsh ubuntu" -> fail ("ubuntu" is my

Re: Can not connect with cqlsh to something different than localhost

2014-12-08 Thread Richard Snowden
I left listen_address blank - still I can't connect (connection refused). "cqlsh" -> OK "cqlsh ubuntu" -> fail ("ubuntu" is my hostname) "cqlsh 192.168.111.136" -> fail "telnet 192.168.111.136 9042" from outside the VM gives me a "connection refused". I just started a Tomcat in my VM and did a "

Re: Can not connect with cqlsh to something different than localhost

2014-12-08 Thread Jonathan Haddad
Listen address needs the actual address, not the interface. This is best accomplished by setting up proper hostnames for each machine (through DNS or hosts file) and leaving listen_address blank, as it will pick the external ip. Otherwise, you'll need to set the listen address to the IP of the ma

Re: Can not connect with cqlsh to something different than localhost

2014-12-08 Thread Vivek Mishra
Two things: 1. Try telnet 192.168.111.136 9042 and see if it connects? 2. check for hostname in /etc/hosts, if it is mapped correctly. -Vivek On Mon, Dec 8, 2014 at 4:19 PM, Richard Snowden wrote: > This did not work either. I changed /etc/cassandra.yaml and restarted > Cassandra (I even resta

Re: Can not connect with cqlsh to something different than localhost

2014-12-08 Thread Richard Snowden
This did not work either. I changed /etc/cassandra.yaml and restarted Cassandra (I even restarted the machine to make 100% sure). What I tried: 1) "listen_address: localhost" -> connection OK (but of course I can't connect from outside the VM to "localhost") 2) Set "listen_interface: eth0"

Re: Can not connect with cqlsh to something different than localhost

2014-12-07 Thread Michael Dykman
Try: $ netstat -lnt and see which interface port 9042 is listening on. You will likely need to update cassandra.yaml to change the interface. By default, Cassandra is listening on localhost so your local cqlsh session works. On Sun, 7 Dec 2014 23:44 Richard Snowden wrote: > I am running Cassandr