[ 
https://issues.apache.org/jira/browse/CASSANDRA-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sunjian updated CASSANDRA-4494:
-------------------------------

    Description: 
1. download cassandra 1.1.3 , then start with "{cassandra}/bin/cassandra -pf &"
2. cd to bin , call nodetool as "./nodetool -h localhost ring"
3. console returned : failed to connect to 'localhost:7199' : connection refused


BUT ,

at the same centos , all was ok before (1.1.2) .


PS: 

cassandra-cli/cqlsh works well (1.1.3)


--------------

update:

even if add the following in cassandra-env.sh , connection refused as well :
JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=10.10.30.11


  was:
1. download cassandra 1.1.3 , then start with "{cassandra}/bin/cassandra -pf &"
2. cd to bin , call nodetool as "./nodetool -h localhost ring"
3. console returned : failed to connect to 'localhost:7199' : connection refused


BUT ,

at the same centos , all was ok before (1.1.2) .


PS: 

cassandra-cli/cqlsh works well (1.1.3)

    
> nodetool can't work at all !
> ----------------------------
>
>                 Key: CASSANDRA-4494
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4494
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.1.3
>         Environment: centos 64bit
>            Reporter: sunjian
>            Priority: Critical
>             Fix For: 1.1.3
>
>
> 1. download cassandra 1.1.3 , then start with "{cassandra}/bin/cassandra -pf 
> &"
> 2. cd to bin , call nodetool as "./nodetool -h localhost ring"
> 3. console returned : failed to connect to 'localhost:7199' : connection 
> refused
> BUT ,
> at the same centos , all was ok before (1.1.2) .
> PS: 
> cassandra-cli/cqlsh works well (1.1.3)
> --------------
> update:
> even if add the following in cassandra-env.sh , connection refused as well :
> JVM_OPTS="$JVM_OPTS -Djava.rmi.server.hostname=10.10.30.11

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to