Re: nodetool hangs and didn't print anything with firewall

2012-02-08 Thread Maxim Potekhin
That's good to hear because it does present a problem for a strictly manages and firewalled campus environment. Maxim On 2/6/2012 11:57 AM, Nick Bailey wrote: JMX is not very firewall friendly. The problem is that JMX is a two connection process. The first connection happens on port 7199 and

Re: nodetool hangs and didn't print anything with firewall

2012-02-06 Thread R. Verlangen
Do you allow both outbound as inbound traffic? You might also try allowing both TCP as UDP. 2012/2/6 Roshan codeva...@gmail.com Yes, If the firewall is disable it works. -- View this message in context:

Re: nodetool hangs and didn't print anything with firewall

2012-02-06 Thread Nick Bailey
JMX is not very firewall friendly. The problem is that JMX is a two connection process. The first connection happens on port 7199 and the second connection happens on some random port 1024. Work on changing this behavior was started in this ticket:

Re: nodetool hangs and didn't print anything with firewall

2012-02-05 Thread Mohit Anchlia
Does it work with iptables disabled? You could add log to your firewall rules to see if firewall is dropping the packets. On Sun, Feb 5, 2012 at 5:35 PM, Roshan codeva...@gmail.com wrote: Hi I have 2 node Cassandra cluster and each linux box configured with a firewall. The ports 7000, 7199