yeah, you can confirm in the log such as the one below.
WARN  [main] 2015-05-22 11:23:25,584 CassandraDaemon.java:81 - JMX is not
enabled to receive remote connections. Please see cassandra-env.sh for more
info.

we are running c* with ipv6, cqlsh works superb but not on local link.
$ nodetool -h fe80::224:1ff:fed7:82ea cfstats system.hints;
nodetool: Failed to connect to 'fe80::224:1ff:fed7:82ea:7199' -
ConnectException: 'Connection refused'.



On Fri, May 22, 2015 at 12:39 AM, Yuki Morishita <[email protected]> wrote:

> For security reason, Cassandra changes JMX to listen localhost only
> since version 2.0.14/2.1.4.
> From NEWS.txt:
>
> "The default JMX config now listens to localhost only. You must enable
> the other JMX flags in cassandra-env.sh manually. "
>
> On Thu, May 21, 2015 at 11:05 AM, Walsh, Stephen
> <[email protected]> wrote:
> > Just wondering if anyone else is seeing this issue on the nodetool after
> > installing 2.1.5
> >
> >
> >
> >
> >
> > This works
> >
> > nodetool -h 127.0.0.1 cfstats keyspace.table
> >
> >
> >
> > This works
> >
> > nodetool -h localhost cfstats keyspace.table
> >
> >
> >
> > This works
> >
> > nodetool cfstats keyspace.table
> >
> >
> >
> > This doesn’t work
> >
> > nodetool -h 192.168.1.10 cfstats keyspace.table
> >
> > nodetool: Failed to connect to ‘192.168.1.10:7199' - ConnectException:
> > 'Connection refused'.
> >
> >
> >
> > Where 192.168.1.10 is the machine IP,
> >
> > All firewalls are disabled and it worked fine on version 2.0.13
> >
> >
> >
> > This has happened on both of our upgraded clusters.
> >
> > Also no longer able to view the “CF: Total MemTable Size” & “flushes
> > pending” in Ops Center 5.1.1, related issue?
> >
> >
> >
> > This email (including any attachments) is proprietary to Aspect Software,
> > Inc. and may contain information that is confidential. If you have
> received
> > this message in error, please do not read, copy or forward this message.
> > Please notify the sender immediately, delete it from your system and
> destroy
> > any copies. You may not further disclose or distribute this email or its
> > attachments.
>
>
>
> --
> Yuki Morishita
>  t:yukim (http://twitter.com/yukim)
>

Reply via email to