DataStax Support Forums » Topic: failed: Connection was refused by other side: 111: Connection refused.

DataStax Support Forums » Topic: failed: Connection was refused by other side: 111: Connection refused. http://www.datastax.com/support-forums/topic/failed-connection-was-refused-by-other-side-111-connection-refused Software, Support, and Training for Apache Cassandra en-US Sat, 25 May 2013 09:56:11 +0000 http://bbpress.org/?v=1.0.3 <![CDATA[Search]]> q http://www.datastax.com/support-forums/search.php ynixon on "failed: Connection was refused by other side: 111: Connection refused." http://www.datastax.com/support-forums/topic/failed-connection-was-refused-by-other-side-111-connection-refused#post-7989 Mon, 17 Dec 2012 16:05:28 +0000 ynixon 7989@http://www.datastax.com/support-forums/ thanks, you information helped mbulman on "failed: Connection was refused by other side: 111: Connection refused." http://www.datastax.com/support-forums/topic/failed-connection-was-refused-by-other-side-111-connection-refused#post-7986 Mon, 17 Dec 2012 09:28:42 +0000 mbulman 7986@http://www.datastax.com/support-forums/ ynixon, opscenterd will only create agent.tar.gz if ssl is enabled (it is by default), and setup.py has not already been run for that instance. It should be something that you only need to run once. You can look in opscenterd.log for messages starting with "Configuring agent communication". That will let you know if SSL is enabled or not. If it is, and bin/setup.py is going to run, you'll see another log message that says "SSL files do not exist. Attempting to create them now....". ynixon on "failed: Connection was refused by other side: 111: Connection refused." http://www.datastax.com/support-forums/topic/failed-connection-was-refused-by-other-side-111-connection-refused#post-7985 Mon, 17 Dec 2012 09:18:59 +0000 ynixon 7985@http://www.datastax.com/support-forums/ From the documentation I understand that the first time opscenter is started, a file called agent.tar.gz should create automatically at some former installations it happened and somehow it is not happening anymore :( After some reading I understand that this file can be created by running bin/setup.py should I relay on the automatic way or manual way ? tupton on "failed: Connection was refused by other side: 111: Connection refused." http://www.datastax.com/support-forums/topic/failed-connection-was-refused-by-other-side-111-connection-refused#post-7952 Tue, 11 Dec 2012 17:14:04 +0000 tupton 7952@http://www.datastax.com/support-forums/ ynixon, That warning is just informing you that OpsCenter cannot connect to the agent on that node, which makes sense if there are no agents running yet. Once the agent is installed and running, OpsCenter will connect and begin collecting node metrics. Cheers, Thomas ynixon on "failed: Connection was refused by other side: 111: Connection refused." http://www.datastax.com/support-forums/topic/failed-connection-was-refused-by-other-side-111-connection-refused#post-7943 Tue, 11 Dec 2012 15:01:23 +0000 ynixon 7943@http://www.datastax.com/support-forums/ after moved cassandra from endpoint_snitch: SimpleSnitch to PropertyFileSnitch at the startup of tarball opscenter I get in opscenterd.log: WARN: HTTP request <a href="http://172.17.4.26:61621/cluster/datacenter?node_ip=172.17.4.26" rel="nofollow">http://172.17.4.26:61621/cluster/datacenter?node_ip=172.17.4.26</a> failed: Connection was refused by other side: 111: Connection refused. opscenterd.conf ================ [webserver] port = 8888 interface = 172.17.4.26 [logging] level=DEBUG [agents] use_ssl = false cassandra-topology.properties ============================= 172.17.4.26=DC1:RAC1 default=DC1:RAC1 at this stage there are no agents (still waiting for agent.tar.gz to be created ..)