[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Trouble with "mco ping"






On Mon, Oct 14, 2013 at 4:55 PM, Kyle Crumpton (kcrumpto) <kcrumpto cisco com> wrote:
Hi all,


I got to section 9. I have made a node host that is registered by DNS, installed mcollective, and started the service. 

I run an mco ping and receive nothing on the broker.

So I went to my node to check the logs and they read as: 

I, [2013-10-14T20:52:43.596114 #4405]  INFO -- : activemq.rb:111:in `on_connectfail' TCP Connection to stomp://mcollective broker dsx org:61613 failed on attempt 14
I, [2013-10-14T20:53:13.626790 #4405]  INFO -- : activemq.rb:96:in `on_connecting' TCP Connection attempt 15 to stomp://mcollective broker dsx org:61613
I, [2013-10-14T20:53:43.658280 #4405]  INFO -- : activemq.rb:111:in `on_connectfail' TCP Connection to stomp://mcollective broker dsx org:61613 failed on attempt 15
I, [2013-10-14T20:54:13.688968 #4405]  INFO -- : activemq.rb:96:in `on_connecting' TCP Connection attempt 16 to stomp://mcollective broker dsx org:61613

So I checked to make sure. Here is my config for server.cfg on the node:

topicprefix = /topic/
main_collective = mcollective
collectives = mcollective
libdir = /opt/rh/ruby193/root/usr/libexec/mcollective
logfile = /var/log/mcollective.log
loglevel = debug
daemonize = 1
direct_addressing = 1
registerinterval = 30

# Plugins
securityprovider = psk
plugin.psk = unset

connector = activemq
plugin.activemq.pool.size = 1
plugin.activemq.pool.1.host = broker.dsx.org
plugin.activemq.pool.1.port = 61613
plugin.activemq.pool.1.user = mcollective
plugin.activemq.pool.1.password = marionette

# Facts
factsource = yaml
plugin.yaml = /etc/mcollective/facts.yaml


I see that the connector is set to activemq. Any idea why it's trying to connect to stomp, and why it's failing?
 
It's using Stomp because the activemq plugin is just an optimization of stomp for activemq:
  
http://docs.puppetlabs.com/mcollective/reference/plugins/connector_activemq.html

I'd check too that the DNS for broker.dsx.org *from the perspective of the node host* resolves to an IP address which is routeable from the node to the broker.

Check that you can ping both the name and the IP address, that the firewalls between and on the broker allow inbound connections on port 61613/tcp

It looks like the node can't find or can't talk to the real destination.
 
________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users




--
----
Mark Lamourine <markllama gmail com>
Dad, Hubbie, Software Developer, System Administrator, Road Cyclist

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]