Following the guide to setting up OO here: http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#setup-yum-repositories
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 14I, [2013-10-14T20:53:13.626790 #4405] INFO -- : activemq.rb:96:in `on_connecting' TCP Connection attempt 15 to stomp://mcollective broker dsx org:61613I, [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 15I, [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 = mcollectivecollectives = mcollectivelibdir = /opt/rh/ruby193/root/usr/libexec/mcollectivelogfile = /var/log/mcollective.logloglevel = debugdaemonize = 1direct_addressing = 1registerinterval = 30
# Pluginssecurityprovider = pskplugin.psk = unset
connector = activemqplugin.activemq.pool.size = 1plugin.activemq.pool.1.host = broker.dsx.orgplugin.activemq.pool.1.port = 61613plugin.activemq.pool.1.user = mcollectiveplugin.activemq.pool.1.password = marionette
# Factsfactsource = yamlplugin.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:
users mailing list
users lists openshift redhat com