DataStax Support Forums » Topic: Not connected in Storage Capacity (Windows)

DataStax Support Forums » Topic: Not connected in Storage Capacity (Windows) http://www.datastax.com/support-forums/topic/not-connected-in-storage-capacity-windows Software, Support, and Training for Apache Cassandra en-US Thu, 23 May 2013 06:13:21 +0000 http://bbpress.org/?v=1.0.3 <![CDATA[Search]]> q http://www.datastax.com/support-forums/search.php mbulman on "Not connected in Storage Capacity (Windows)" http://www.datastax.com/support-forums/topic/not-connected-in-storage-capacity-windows#post-1128 Fri, 10 Feb 2012 17:23:40 +0000 mbulman 1128@http://www.datastax.com/support-forums/ Can you check the agent logs on each node for any errors? You can find the logs in <INSTALL DIRECTORY>\logs\ Anonymous on "Not connected in Storage Capacity (Windows)" http://www.datastax.com/support-forums/topic/not-connected-in-storage-capacity-windows#post-1127 Fri, 10 Feb 2012 15:14:50 +0000 Anonymous 1127@http://www.datastax.com/support-forums/ Starting NodeTool Address DC Rack Status State Load Owns T oken 8 5070591730234615865843651857942052864 192.168.0.145 datacenter1 rack1 Up Normal 3.2 MB 50.00% 0 192.168.0.154 datacenter1 rack1 Up Normal 3.22 MB 50.00% 8 5070591730234615865843651857942052864 address.yaml stomp_interface: 192.168.0.145 local_interface: 192.168.0.145 use_ssl: 0 still no luck any ideas? mbulman on "Not connected in Storage Capacity (Windows)" http://www.datastax.com/support-forums/topic/not-connected-in-storage-capacity-windows#post-1121 Thu, 09 Feb 2012 21:16:28 +0000 mbulman 1121@http://www.datastax.com/support-forums/ You'll want to make sure the local_interface property in address.yaml corresponds to the IP you see in the Address column of <code>nodetool -h localhost ring</code> (there is mention of how to run that in the article). Can you try changing those, restarting the Agent services, and seeing if that helps? Anonymous on "Not connected in Storage Capacity (Windows)" http://www.datastax.com/support-forums/topic/not-connected-in-storage-capacity-windows#post-1120 Thu, 09 Feb 2012 20:11:29 +0000 Anonymous 1120@http://www.datastax.com/support-forums/ I had OpsCenter working 100% when there was only one node in the cluster. When I added a second node it just didn't work. <a href="http://www.datastax.com/resources/articles/setup-and-monitor-a-multi-node-cassandra-cluster-on-windows" rel="nofollow">http://www.datastax.com/resources/articles/setup-and-monitor-a-multi-node-cassandra-cluster-on-windows</a> I am pretty sure its a OpsCenter problem but I am stuck. <a href="http://i.imgur.com/4OCnf.png" rel="nofollow">http://i.imgur.com/4OCnf.png</a> <-currently I have posted the config files below. Any help would be greatly appreciated. opscernterd.conf # [self-contained] opscenterd.conf # # paths must be relative to the top-level opscenter directory [jmx] # The default jmx port for Cassandra >= 0.8.0 is 7199. If you are using # Cassandra 0.7.*, the default is 8080, and you should change this to # reflect that. port = 7199 [webserver] port = 8888 interface = 0.0.0.0 staticdir = ./content log_path =E:\Cassandra\logs\opscenterd-http.log [logging] # level may be TRACE, DEBUG, INFO, WARN, or ERROR #level = INFO log_path =E:\Cassandra\logs\opscenterd.log [cassandra] # a comma-separated list of places to try for a connection to your Cassandra # cluster: seed_hosts = 127.0.0.1 # the API (Thrift) port on your Cassandra cluster #api_port = 9160 [agents] ssl_keyfile = ./ssl/opscenter.key ssl_certfile = ./ssl/opscenter.pem agent_keyfile = ./ssl/agentKeyStore agent_certfile = ./ssl/agentKeyStore.pem path_to_installscript = ./bin/install_agent.sh path_to_sudowrap = ./bin/sudo_with_pass.py path_to_deb = NONE path_to_rpm = NONE tmp_dir = ./tmp use_ssl=0 incoming_interface=0.0.0.0 [stat_reporter] ssl_key = ./ssl/stats.pem [authentication] # if this file does not exist, there will be no password protection. Use the # set_passwd.py tool (included with OpsCenter) to set passwords. passwd_file = ./passwds [cassandra_metrics] # A list of keyspaces to *not* collect metrics for, separated by commas #ignored_keyspaces = system, OpsCenter # A list of column families to *not* collect metrics for, separated # by commas. Each entry should be of the form "ks.cf". For example: # metrics_ignored_column_families = system.NodeInfo, system.Schema, Keyspace1.Standard1 #ignored_column_families = # OpsCenter stores performance data for your cluster at multiple granularities. # These values determine the expiration of each level of granularity. A value of # -1 indicates to never expire data for that level. Newly set expiration times # apply to data inserted after the value was changed and OpsCenter was restarted. # Data inserted prior to that point will expire at the previously specified rate. # Expire 1 minute data points after 7 days #1min_ttl = 604800 # Expire 5 minute data points after 4 weeks (28 days) #5min_ttl = 2419200 # Expire 2 hour data points after 365 days #2hr_ttl = 31536000 address.yaml main stomp_interface: 127.0.0.1 local_interface: 127.0.0.1 use_ssl: 0 address.yaml second node stomp_interface: 192.168.0.145 local_interface: 127.0.0.1 use_ssl: 0