Re: Failed to connect to '127.0.0.1:7199'

2013-04-06 Thread Everton Lima
What is the IP setted in cassandra.yalm file? Try to use that IP. 2013/4/6 zg > Hi everyone, > I have a 3 nodes cluster, one node when I use nodetool, I met a error > "Failed to connect to '127.0.0.1:7199':Connection timed out", use CLI and > CQLsh is ok on t

Failed to connect to '127.0.0.1:7199'

2013-04-05 Thread zg
Hi everyone, I have a 3 nodes cluster, one node when I use nodetool, I met a error "Failed to connect to '127.0.0.1:7199':Connection timed out", use CLI and CQLsh is ok on this node, the other two nodes is OK when I use nodetool commend. So what's the problem with that node?

Re: Nodetool can not get to 7199 after migrating to 1.2.1

2013-01-31 Thread aaron morton
52 AM, Shahryar Sedghi wrote: > I migrated my test environment from 1.2.0 to 1.2.1 (DataStax Community) and > nodetool can not communicate to 7199, even if it is listening. in one node I > get > Failed to connect to 'cassandra4:7199': Connection refused > > in another

Nodetool can not get to 7199 after migrating to 1.2.1

2013-01-30 Thread Shahryar Sedghi
I migrated my test environment from 1.2.0 to 1.2.1 (DataStax Community) and nodetool can not communicate to 7199, even if it is listening. in one node I get Failed to connect to 'cassandra4:7199': Connection refused in another node I get timeout. Did I do anything wrong, when upgradin

Re: what other ports than 7199 need to be open for nodetool to work?

2012-03-26 Thread Edward Capriolo
s. It is still connecting to a >> random second port though. >> >> On Mon, Mar 26, 2012 at 2:42 PM, Yiming Sun wrote: >> > Hi, >> > >> > We opened port 7199 on a cassandra node, but were unable to get a >> > nodetool >> > to talk to it

Re: what other ports than 7199 need to be open for nodetool to work?

2012-03-26 Thread Yiming Sun
detool is often > used to connect to 'localhost' which generally does not have any > firewall rules at all so it usually works. It is still connecting to a > random second port though. > > On Mon, Mar 26, 2012 at 2:42 PM, Yiming Sun wrote: > > Hi, > > > >

Re: what other ports than 7199 need to be open for nodetool to work?

2012-03-26 Thread Nick Bailey
which generally does not have any firewall rules at all so it usually works. It is still connecting to a random second port though. On Mon, Mar 26, 2012 at 2:42 PM, Yiming Sun wrote: > Hi, > > We opened port 7199 on a cassandra node, but were unable to get a nodetool > to talk to it remo

what other ports than 7199 need to be open for nodetool to work?

2012-03-26 Thread Yiming Sun
Hi, We opened port 7199 on a cassandra node, but were unable to get a nodetool to talk to it remotely unless we turn off the firewall entirely. So what other ports should be opened for this -- online posts all indicate that JMX uses a random dynamic port, which would be difficult to create a

Re: 7199

2011-11-22 Thread Maxim Potekhin
khin wrote: Hello, I have this in my cassandra-env.sh JMX_PORT="7199" Does this mean that if I use nodetool from another node, it will try to connect to that particular port? Thanks, Maxim

Re: 7199

2011-11-22 Thread Jeremiah Jordan
Yes, that is the port nodetool needs to access. On Nov 22, 2011, at 8:43 PM, Maxim Potekhin wrote: > Hello, > > I have this in my cassandra-env.sh > > JMX_PORT="7199" > > Does this mean that if I use nodetool from another node, it will try to > connect to t

7199

2011-11-22 Thread Maxim Potekhin
Hello, I have this in my cassandra-env.sh JMX_PORT="7199" Does this mean that if I use nodetool from another node, it will try to connect to that particular port? Thanks, Maxim