Are you running 'mco ping' from the same <hostname> on which you setup
activemq and client configuration?

Based on
https://forge.puppet.com/puppet/mcollective#i-just-want-to-run-it-whats-the-minimum-i-need,
I would expect that to work.

On Mon, Feb 27, 2017 at 11:20 AM Amrit Atmajit <[email protected]>
wrote:

Hi,



I am trying to configure mcollective in Puppet 4.x but, failed to do mco
ping.



Please find the steps that I tried to configure mcollective as follows and
let me know where I am missing:



·         Installed Puppet Server and Puppet in CentOS 7

·         Installed activemq module (puppet module install
puppetlabs-activemq)

·         Installed mcollective module (puppet module install
puppet-mcollective)

In site.pp:

node <hostname>  {

  include activemq



  class { '::mcollective':

    #middleware  => true,

    client      => true,

    middleware_hosts => [‘<hostname>'],

  }

}

·         On issue of “puppet agent –test”, activemq, mcollective client
and mcollective server installed properly.

·         Restarted the services of aactivemq and mcollective.



After following the above steps, “mco ping -v” command is complaining as
follows:



# *mco ping -v*

The ping application failed to run: Could not connect to ActiveMQ Server:



Could not connect to ActiveMQ Server:  (RuntimeError)

        from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/connector/activemq.rb:273:in
`rescue in connect'  <----

        from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/connector/activemq.rb:221:in
`connect'

        from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/client.rb:36:in
`block in initialize'

        from /opt/puppetlabs/puppet/lib/ruby/2.1.0/timeout.rb:75:in
`timeout'

        from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/client.rb:35:in
`initialize'

        from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/application/ping.rb:52:in
`new'

        from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/application/ping.rb:52:in
`main'

        from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/application.rb:293:in
`run'

        from
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/mcollective/applications.rb:23:in
`run'

        from /opt/puppetlabs/bin/mco:33:in `<main>'



Whether I’ve missed any configuration? How can I resolve configuring
mcollective in Puppet 4.x



Regards,

Amrit

-- 

---
You received this message because you are subscribed to the Google Groups
"mcollective-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
For more options, visit https://groups.google.com/d/optout.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"mcollective-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to