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 7E3121088E for ; Wed, 30 Oct 2013 11:01:37 +0000 (UTC) Received: (qmail 54445 invoked by uid 500); 30 Oct 2013 11:01:31 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 54388 invoked by uid 500); 30 Oct 2013 11:01:29 -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 54309 invoked by uid 99); 30 Oct 2013 11:01:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Oct 2013 11:01:26 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of nigel.leach@uk.bnpparibas.com designates 155.140.133.163 as permitted sender) Received: from [155.140.133.163] (HELO lonmail6.bnpparibas.com) (155.140.133.163) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Oct 2013 11:01:16 +0000 X-IronPort-AV: E=Sophos;i="4.93,600,1378854000"; d="scan'208";a="120001096" From: Nigel LEACH To: "user@cassandra.apache.org" Subject: RE: OpsCenter not connecting to Cluster Thread-Topic: OpsCenter not connecting to Cluster Thread-Index: Ac7Uy6YiR6KUqDcXTSeyICGxDZmp6AACMTRgACFrbOAAASFTYA== Date: Wed, 30 Oct 2013 11:00:49 +0000 Message-ID: References: <1db2f89777a3459a8e69b3353fa41634@AMSPR06MB069.eurprd06.prod.outlook.com> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Fixed - Sort of. I noticed in the Cassandra system log that thrift was linked to localhost, = not xx.xx.xx.xx, or its hostname. Binding thrift service to localhost/127.0.0.1:9160. So, in the OpsCenter GUI I entererd localhost as the name of a server in th= e Cluster, and all works. Regards Nigel -----Original Message----- From: Nigel LEACH = Sent: 30 October 2013 10:50 To: user@cassandra.apache.org Subject: RE: OpsCenter not connecting to Cluster Hello Pieter, Thank you for the response. I picked up on the stackoverlow l= ink, but I am already setting rpc_server_type as sync. As you say they are = Ubuntu, and I am Redhat, but I'm not on top RPC implementations to know whe= ther that is relevent. = Another point, in my original mail I missed of two lines from my log DEBUG: Trying to connect to node xx.xx.xx.xx over thrift DEBUG: Not returning SASL credentials for xx.xx.xx.xx Lastly, I can connect successfully to all the JMX's (via VisualVM) on the d= efault 7199 port. Regards, Nigel -----Original Message----- From: pieter.callewaert@be-mobile.be [mailto:pieter.callewaert@be-mobile.be= ] = Sent: 29 October 2013 18:30 To: user@cassandra.apache.org Subject: RE: OpsCenter not connecting to Cluster Hi Nigel, I've currently have a simular problem. However, it has only been reproduced= on Ubuntu... Are you using hsha as rpc_server_type? http://stackoverflow.com/questions/19633980/adding-cluster-error-creating-c= luster-call-to-cluster-configs-timed-out is a guy with the same problem, sh= owing how to reproduce. I know the ppl of datastax are now investigating this, but no fix yet... Kind regards, Pieter Callewaert -----Original Message----- From: Nigel LEACH [mailto:nigel.leach@uk.bnpparibas.com] = Sent: dinsdag 29 oktober 2013 18:24 To: user@cassandra.apache.org Subject: OpsCenter not connecting to Cluster Cassandra 2.0.1 OpsCenter 3.2.2 Java 1.7.0_25 RHEL 6.4 This is a new test cluster with just three nodes, two seed nodes, SSL turne= d off, and GossipingPropertyFileSnitch. Pretty much out of the box environm= ent, with both Cassandra and OpsCenter via DataStax yum repository. Cassandra seems fine, and OpsCenter is installed on a seed node. The OpsCen= ter gui comes up, but is unable to connect to the cluster, I get this error INFO: Starting factory INFO: will retry in = 2 seconds DEBUG: Problem while pinging node: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/opscenterd/ThriftService.p= y", line 157, in checkThriftConnection UserError: User aborted connection: Shutdown requested. WARN: ProcessingError while calling CreateClusterConfController: Unable to = connect to cluster INFO: Stopping factory = Not getting very far troubleshooting it, any clues would be much appreciate= d. Should I try installing the OpsCenter agent manually maybe? Many Thanks, Nigel ___________________________________________________________ This e-mail may contain confidential and/or privileged information. If you = are not the intended recipient (or have received this e-mail in error) plea= se notify the sender immediately and delete this e-mail. Any unauthorised c= opying, disclosure or distribution of the material in this e-mail is prohib= ited. Please refer to http://www.bnpparibas.co.uk/en/email-disclaimer/ for additi= onal disclosures. ___________________________________________________________ This e-mail may contain confidential and/or privileged information. If you = are not the intended recipient (or have received this e-mail in error) plea= se notify the sender immediately and delete this e-mail. Any unauthorised c= opying, disclosure or distribution of the material in this e-mail is prohib= ited. Please refer to http://www.bnpparibas.co.uk/en/email-disclaimer/ for additi= onal disclosures. ___________________________________________________________ This e-mail may contain confidential and/or privileged information. If you = are not the intended recipient (or have received this e-mail in error) plea= se notify the sender immediately and delete this e-mail. Any unauthorised c= opying, disclosure or distribution of the material in this e-mail is prohib= ited. Please refer to http://www.bnpparibas.co.uk/en/email-disclaimer/ for additi= onal disclosures.