Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of osishkin@gmail.com designates
 209.85.161.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:cc:content-type;
        b=iu/6ouHwYhaKxN61U4e3VDEG92pedGL7VDGRgnn4DATfw+WR1wcWbIY9QIxmHeHyBg
         1dESxk6DxcImDeXFkM1snERLCqkF8Q+MWvVKsER7FxUfCy4CO8nGmbIwCExdrwUd7CGT
         EWGPEXHQw6Q9iRdbxYvKRZ8mn4ashNhkJdM3I=
MIME-Version: 1.0
Reply-To: osishkin@gmail.com
In-Reply-To: <AANLkTikpQXGzFC7mhpPJv1OzcW-WN4jwCQMjYRiOrP8g@mail.gmail.com>
References: <AANLkTinueKf9ffkd_HjA-HPUTQKS+QXO2Dc8Z9BNojfs@mail.gmail.com>
	<AANLkTinOB03dKP3qi=TsR9G6_hwpDXh=RqD4hXc2wPjK@mail.gmail.com>
	<AANLkTikAQLXwQeARd=Cg7fcF1JRWqV1sVdPqs8AhLKGS@mail.gmail.com>
	<AANLkTikpQXGzFC7mhpPJv1OzcW-WN4jwCQMjYRiOrP8g@mail.gmail.com>
Date: Thu, 5 Aug 2010 17:45:19 +0300
Message-ID: <AANLkTin-q-sUZhm921df6wtVDf5cHYALENh88FFJQdsm@mail.gmail.com>
Subject: Re: Please need help with Munin: Cassandra Munin plugin problem
From: osishkin osishkin <osishkin@gmail.com>
To: Peter Schuller <peter.schuller@infidyne.com>
Cc: user@cassandra.apache.org, Brandon Williams <driftx@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

I've managed to find the problem. Not a IBM vs. Sun JRE issue.
It had to do with my RHEL distribution JRE defintions which caused
conflicts (from /etc/java/java.conf...). When invoking with absolute
path to java executable, instead of simply java the errors were gone.
So no more errors in munin-node.log.

However I now get errors in munin-update.log, such as
Aug 05 17:35:01 [18822] - Warning: Unknown option "value" in
"my_machine_name:compactions_bytes.bytes.value".
And this is true for every Cassandra plugin. Any idea as to what may
be the cause for this error?

Thank you
Aviad
On Wed, Aug 4, 2010 at 7:04 PM, Peter Schuller
<peter.schuller@infidyne.com> wrote:
>> Are you saying this based on your personal experience?
>> Or is this just an educated guess?
>
> Whatever the cause, the end result is that
> javax.management.remote.JMXConnector does not exist. So the most
> likely culprits would be that CLASSPATH is different, or you're using
> a different JVM. For example, on many operating systems "java" is a
> wrapper that selects which JVM to use - possibly depending on
> environment variables.
>
> I can't speak to the comment about IBM and whether their JRE would be
> expected to include the JMX classes; but certainly some CLASSPATH or
> JVM mismatch seems likely.
>
> --
> / Peter Schuller
>