Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C8A1010BFC for ; Thu, 17 Oct 2013 01:08:24 +0000 (UTC) Received: (qmail 72543 invoked by uid 500); 17 Oct 2013 01:08:21 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 72443 invoked by uid 500); 17 Oct 2013 01:08:21 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 72435 invoked by uid 99); 17 Oct 2013 01:08:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Oct 2013 01:08:20 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [74.125.245.84] (HELO na3sys010aog108.obsmtp.com) (74.125.245.84) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 17 Oct 2013 01:08:13 +0000 Received: from mail-we0-f182.google.com ([74.125.82.182]) (using TLSv1) by na3sys010aob108.postini.com ([74.125.244.12]) with SMTP ID DSNKUl84Z5odzzFmqKK1rliqOA1LQtIIBpp8@postini.com; Wed, 16 Oct 2013 18:07:52 PDT Received: by mail-we0-f182.google.com with SMTP id t61so1556574wes.13 for ; Wed, 16 Oct 2013 18:07:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=VK6hp/iHMHNJhtZDCyOhGDiEO1BFPdUFR/m5gCZEUfs=; b=DS70EwX87cg+3dybOO1PHhO0ABGmTCUTUKPWn21O64Wp6N8AUyZycxAetr1lu50lbT 4LpVtgDdzxAnLoR3p/SiPxURw2/JGnrEuU0IBFF9vPmF+OqOJTybbTspJzu7P5W7OsAv x4jwbRgpO6ToCyjeRP71mOxhXQLxC5m1YHPjN56R7OPVL3+glvsMgH/P6/n57QWfJuXs GgkDvGglbY0Npd2vVqRje7EzjJq2Hb1imLq07uOFaz+IHrxxd+iuS1CaKCUdaGLSvy3R f03jebMQjCEJnro6/p591+aisKfq9l6Ook24S7miwm/S8Qs8BjboouLuE0/OyJRsowz7 ICcA== X-Gm-Message-State: ALoCoQlyw3jMos1SKRNAGhuFDkwphLDSl62eZI3IlRPFb6UGYyCr48++/23qcGWvDodwIkAEKJp0qf1XyyocaAAGU9tY2l7Jvv+aTH5JH0phC0ObULwVWyUBQ1dY0ryhaYPaIZFRwT8SLGRM4lHdr5hfR0+8+JepM0LCMv9dhGh22RV6YbMycLM= X-Received: by 10.194.104.42 with SMTP id gb10mr4877875wjb.16.1381972069910; Wed, 16 Oct 2013 18:07:49 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.104.42 with SMTP id gb10mr4877872wjb.16.1381972069833; Wed, 16 Oct 2013 18:07:49 -0700 (PDT) Received: by 10.194.15.4 with HTTP; Wed, 16 Oct 2013 18:07:49 -0700 (PDT) Date: Thu, 17 Oct 2013 12:07:49 +1100 Message-ID: Subject: Opscenter 3.2.2 (?) jmx auth issues From: Sven Stark To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7bf198524ff15f04e8e5729a X-Virus-Checked: Checked by ClamAV on apache.org --047d7bf198524ff15f04e8e5729a Content-Type: text/plain; charset=ISO-8859-1 Hi guys, we have secured C* jmx with username/pw. We upgraded our Opscenter from 3.0.2 to 3.2.2 last week and noticed that the agents could not connect anymore ERROR [jmx-metrics-4] 2013-10-17 00:45:54,437 Error getting general metrics java.lang.SecurityException: Authentication failed! Credentials required at com.sun.jmx.remote.security.JMXPluggableAuthenticator.authenticationFailure(JMXPluggableAuthenticator.java:193) at com.sun.jmx.remote.security.JMXPluggableAuthenticator.authenticate(JMXPluggableAuthenticator.java:145) even though the credentials were correctly in /etc/opscenter/clusters/foo-cluster.conf [jmx] username = secret password = verysecret port = 20001 Checks with other jmx based tools (nodetool, jmxtrans) confirm that the jmx setup is correct. Downgrading Opscenter to 3.0.2 immediately resolved the issue. Could anybody confirm whether that's a known bug? Cheers, Sven --047d7bf198524ff15f04e8e5729a Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi guys,

we have secured C* = jmx with username/pw. We upgraded our Opscenter from 3.0.2 to 3.2.2 last we= ek and noticed that the agents could not connect anymore

ERROR [jmx-metrics-4] 2013-10-17 00:45:54,437 Error getting general me= trics
java.lang.SecurityException: Authentication failed! Credent= ials required
= at com.sun.jmx.remote.security.JMXPluggableAuthenticator.authenticationFail= ure(JMXPluggableAuthenticator.java:193)
at com.sun.jmx.remo= te.security.JMXPluggableAuthenticator.authenticate(JMXPluggableAuthenticato= r.java:145)

even though the credentials were corre= ctly in /etc/opscenter/clusters/foo-cluster.conf

[jmx]
username =3D secret
password = =3D verysecret
port =3D 20001

Checks wit= h other jmx based tools (nodetool, jmxtrans) confirm that the jmx setup is = correct.

Downgrading Opscenter to 3.0.2 immediately resolved the= issue. Could anybody confirm whether that's a known bug?

Cheers,
Sven
--047d7bf198524ff15f04e8e5729a--