Re: unable to nodetool to remote EC2

2012-05-22 Thread ramesh
On 05/22/2012 12:45 AM, Tamar Fraenkel wrote: Thanks for the response. But it still does not work. I am running the script from a git bash on my windows 7. adding some debug prints, this is what I am running

Re: unable to nodetool to remote EC2

2012-05-21 Thread Tamar Fraenkel
Thanks for the response. But it still does not work. I am running the script from a git bash on my windows 7. adding some debug prints, this is what I am running ssh -i key.pem -N -f -D8123 ubuntu@ec2-*.amazonaws.com ssh pid = 11616 /c/PROGRA~2/Java/jdk1.7.0_02/bin/jconsole.exe -J-DsocksProxyHost=l

Re: unable to nodetool to remote EC2

2012-05-21 Thread ramesh
On 05/21/2012 03:55 AM, Tamar Fraenkel wrote: Hi! I am trying the tunnel and it fails. Will be gratefull for some hints: I defined proxy_host = ubuntu@my_ec2_cassandra_node_public

Re: unable to nodetool to remote EC2

2012-05-21 Thread Tamar Fraenkel
Hi! I am trying the tunnel and it fails. Will be gratefull for some hints: I defined - proxy_host = ubuntu@my_ec2_cassandra_node_public_ip - proxy_port = 22 I do: *ssh -N -f -i /c/Users/tamar/.ssh/Amazon/tokey.openssh -D22 ubuntu@my_ec2_cassandra_node_public_ip* I put some debug prints an

Re: unable to nodetool to remote EC2

2012-05-18 Thread ramesh
On 05/18/2012 01:35 PM, Tyler Hobbs wrote: Your firewall rules need to allow TCP traffic on any port >= 1024 for JMX to work. It initially connects on port 7199, but then the client is asked to reconnect on a randomly chosen port. You can open the firewall, SSH to the node first, or set up so

Re: unable to nodetool to remote EC2

2012-05-18 Thread ramesh
On 05/18/2012 01:35 PM, Tyler Hobbs wrote: Your firewall rules need to allow TCP traffic on any port >= 1024 for JMX to work. It initially connects on port 7199, but then the client is asked to reconnect on a randomly chosen port. You can open the firewall, SSH to the node first, or set up so

Re: unable to nodetool to remote EC2

2012-05-18 Thread Tyler Hobbs
Your firewall rules need to allow TCP traffic on any port >= 1024 for JMX to work. It initially connects on port 7199, but then the client is asked to reconnect on a randomly chosen port. You can open the firewall, SSH to the node first, or set up something like this: http://simplygenius.com/2010

unable to nodetool to remote EC2

2012-05-18 Thread ramesh
I updated the cassandra-env.sh $JMX_HOST="10.20.30.40" JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=$JMX_HOST" netstat -ltn shows port 7199 is listening. I tried both public and private IP for connecting but neither helps. However, I am able to connect locally from within server. I get this