http://www.datastax.com/support-forums/topic/opscenter-131-and-cassandra-106 Software, Support, and Training for Apache Cassandra en-US Sat, 18 May 2013 11:42:08 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/opscenter-131-and-cassandra-106#post-1001 Thu, 05 Jan 2012 20:34:37 +0000 Anonymous 1001@http://www.datastax.com/support-forums/ <p>OK, I've found it. The rpc_address-setting was set to localhost and didn't worked somehow. But it worked before. Don't know why. I have set it now to the specific IP-addresses of the nodes.</p> <p>Thanks for support. </p> http://www.datastax.com/support-forums/topic/opscenter-131-and-cassandra-106#post-1000 Thu, 05 Jan 2012 20:29:36 +0000 nickmbailey 1000@http://www.datastax.com/support-forums/ <p>OpsCenter does not use hector, it uses another thrift client called Telephus. It sounds like thrift on your cluster is broken. Perhaps there are errors in the cassandra log? </p> http://www.datastax.com/support-forums/topic/opscenter-131-and-cassandra-106#post-999 Thu, 05 Jan 2012 20:27:03 +0000 Anonymous 999@http://www.datastax.com/support-forums/ <p>Ok, will do so, but on my nodes there shouldnt be a firewall configured. BTW: what i recognized as well (but this is then not opscenter specific) is, that the hector client is also not connecting anymore in a client i wrote:</p> <p>214 [main] INFO me.prettyprint.cassandra.connection.CassandraHostRetryService - Host detected as down was added to retry queue: xx.xx.xx.xx(xx.xx.xx.xx):9160<br /> 219 [Hector.me.prettyprint.cassandra.connection.CassandraHostRetryService-1] WARN me.prettyprint.cassandra.connection.CassandraHostRetryService - Downed xxx.xx.xx.xx(xx.xx.xx.xx):9160 host still appears to be down: Unable to open transport to 78.46.</p> <p>This is weird, because this also worked before with 1.0.5. Is opscenter also using hector?</p> <p>wei </p> http://www.datastax.com/support-forums/topic/opscenter-131-and-cassandra-106#post-998 Thu, 05 Jan 2012 19:53:27 +0000 nickmbailey 998@http://www.datastax.com/support-forums/ <p>Daniel,</p> <p>It may help to change the logging level to DEBUG in opscenterd.conf. I'm not sure what is causing the problem here. The most likely candidate I would say is a firewall issue preventing OpsCenter from connecting to port 9160 on your cluster. That doesn't explain why it would break when upgrading from 1.0.5 to 1.0.6 though.</p> <p>Can you check if the debug log provides any more information. </p> http://www.datastax.com/support-forums/topic/opscenter-131-and-cassandra-106#post-997 Thu, 05 Jan 2012 19:48:05 +0000 Anonymous 997@http://www.datastax.com/support-forums/ <p>OK, I have restarted several times. And I have installed a fresh cassandra cluster with no data etc and the log also doesn't show any error I think:</p> <p>2012-01-05 20:45:41+0100 [] INFO: Server Shut Down.<br /> 2012-01-05 20:45:42+0100 [] INFO: Log opened.<br /> 2012-01-05 20:45:42+0100 [] INFO: twistd 10.2.0 (/usr/bin/python2.6 2.6.6) starting up.<br /> 2012-01-05 20:45:42+0100 [] INFO: reactor class: twisted.internet.selectreactor.SelectReactor.<br /> 2012-01-05 20:45:42+0100 [] INFO: set uid/gid 0/0<br /> 2012-01-05 20:45:42+0100 [] INFO: Logging level set to 'info'<br /> 2012-01-05 20:45:42+0100 [] INFO: OpsCenterdService startService<br /> 2012-01-05 20:45:42+0100 [] INFO: OpsCenter version: 1.3.1<br /> 2012-01-05 20:45:42+0100 [] INFO: Compatible agent version: 2.4<br /> 2012-01-05 20:45:42+0100 [] INFO: HTTP BASIC authentication disabled<br /> 2012-01-05 20:45:42+0100 [] INFO: agent_config items: {'metrics_enabled': 1, 'http_server_port': 61621, 'metrics_ignored_column_families': '', 'metrics_ignored_keyspaces': 'system, OpsCenter', 'jmx_port': 7199}<br /> 2012-01-05 20:45:42+0100 [] INFO: opscenterd.WebServer.OpsCenterdWebServer starting on 8888<br /> 2012-01-05 20:45:42+0100 [] INFO: Starting factory &lt;opscenterd.WebServer.OpsCenterdWebServer instance at 0x2a28a70&gt;<br /> 2012-01-05 20:45:42+0100 [] INFO: Starting CassandraCluster service<br /> 2012-01-05 20:45:42+0100 [] INFO: morbid.morbid.StompFactory starting on 61619<br /> 2012-01-05 20:45:42+0100 [] INFO: Starting factory &lt;morbid.morbid.StompFactory instance at 0x2a4f200&gt;<br /> 2012-01-05 20:45:42+0100 [] INFO: morbid.morbid.StompFactory starting on 61620<br /> 2012-01-05 20:45:42+0100 [] INFO: Starting PushService<br /> 2012-01-05 20:45:42+0100 [] INFO: (No candidate nodes to expand pool to target size 5 from 0; there are 1 pending requests. Expected candidate node retry in 0.1 seconds.)<br /> 2012-01-05 20:45:42+0100 [] INFO: (No candidate nodes to expand pool to target size 5 from 0; there are 1 pending requests. Expected candidate node retry in 0.1 seconds.)<br /> 2012-01-05 20:45:42+0100 [] INFO: (No candidate nodes to expand pool to target size 5 from 0; there are 1 pending requests. Expected candidate node retry in 0.1 seconds.)<br /> 2012-01-05 20:45:42+0100 [] INFO: (No candidate nodes to expand pool to target size 5 from 0; there are 1 pending requests. Expected candidate node retry in 0.1 seconds.)<br /> 2012-01-05 20:45:42+0100 [] INFO: (No candidate nodes to expand pool to target size 5 from 0; there are 1 pending requests. Expected candidate node retry in 0.1 seconds.)<br /> 2012-01-05 20:45:42+0100 [] INFO: CPU Info: ['2800.000', '2800.000']<br /> 2012-01-05 20:45:42+0100 [] INFO: Mem Info: 3934MB<br /> 2012-01-05 20:45:42+0100 [] INFO: OS Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-34squeeze1) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 23:13:22 UTC 2011<br /> 2012-01-05 20:45:42+0100 [] INFO: Package Manager: aptitude </p> http://www.datastax.com/support-forums/topic/opscenter-131-and-cassandra-106#post-990 Thu, 05 Jan 2012 18:31:38 +0000 nickmbailey 990@http://www.datastax.com/support-forums/ <p>Daniel,</p> <p>That error from the log is the connection pool attempting to fill the pool. I believe there should be errors before that in the log indicating the initial connection failure. You may want to restart the OpsCenter process and then check for errors as the process starts up. </p> http://www.datastax.com/support-forums/topic/opscenter-131-and-cassandra-106#post-989 Thu, 05 Jan 2012 18:10:39 +0000 Anonymous 989@http://www.datastax.com/support-forums/ <p>It's always showing:</p> <p>2012-01-05 19:05:43+0100 [] INFO: (No candidate nodes to expand pool to target size 5 from 0; there are 0 pending requests. Expected candidate node retry in 182.0 seconds.)</p> <p>when I 'ring' the nodes via nodetool all seems fine:</p> <p>Address DC Rack Status State Load Owns Token<br /> 85070591730234615865843651857942052864<br /> xxx.xxx.xxx.xxx datacenter1 rack1 Up Normal 277.53 MB 50.00% 0<br /> xxx.xxx.xxx.xxx datacenter1 rack1 Up Normal 285.68 MB 50.00% 85070591730234615865843651857942052864 </p> http://www.datastax.com/support-forums/topic/opscenter-131-and-cassandra-106#post-988 Thu, 05 Jan 2012 17:31:39 +0000 nickmbailey 988@http://www.datastax.com/support-forums/ <p>Daniel,</p> <p>OpsCenter should work with 1.0.6. It would help if you could post the OpsCenter log so we can diagnose what is causing thrift communication problems. It should be located at /var/log/opscenter/opscenterd.log. </p> http://www.datastax.com/support-forums/topic/opscenter-131-and-cassandra-106#post-986 Thu, 05 Jan 2012 13:53:31 +0000 Anonymous 986@http://www.datastax.com/support-forums/ <p>Hi and thanks for this nice tool,</p> <p>I have just upgraded a 2 node cassandra cluster to version 1.0.6. The 1.0.5 version worked fine with the OpsCenter, but now the OpsCenter always returns me the message: "OpsCenter has not established a connection to your Cassandra cluster." Are they not compatible with each other? </p> <p>Thanks &amp; best regards</p> <p>Daniel </p>