One other gotcha I've come across trying to use jmx was on machines with
multiple interfaces. The rmi server doesn't always bind to the one
you want. I add this to my JVM_OPTS in cassandra.in.sh
-Djava.rmi.server.hostname=$IP
where IP is
IP=`/sbin/ifconfig | grep 'inet addr:' | grep -v '127.0.0.1' | cut -d: -f2 |
awk '{ print $1}'`
This cause the rmi server to bind to the appropriate address for the vmware
I run this in, allowing me to connect via jconsole running on the host OS.
I use the same thing in EC2 but the ip address is gotten from a tool which
queries the interfaces setup by the ami and finds the right one.
-Anthony
On Sun, Sep 20, 2009 at 09:09:29PM -0500, Eric Evans wrote:
> On Sun, 2009-09-20 at 09:42 +0930, Chris Were wrote:
>
> > *sigh* I should have tried turning iptables off -- I can now see both
> > nodes. Thanks :)
> >
> >
> > That being said, I'm no expert in iptables rules. This is what I added
> > for cassandra, what rules do others use?
> >
> >
> > -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 9160
> > -j ACCEPT
> > -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 7000
> > -j ACCEPT
> > -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 7001
> > -j ACCEPT
> > -A RH-Firewall-1-INPUT -p tcp -m state --state NEW -m tcp --dport 8888
> > -j ACCEPT
>
> Assuming that you are using defaults, and you want to use nodeprobe (or
> any other jmx client) remotely then you'll also need to open tcp/8080.
>
> --
> Eric Evans
> eev...@rackspace.com
>
--
------------------------------------------------------------------------
Anthony Molinaro <antho...@alumni.caltech.edu>
