search for: direct_address

...prevent systems from being overly +# chatty on the message bus by default. If you want a higher frequency, this +# may be set to 300 (5 minutes) +registerinterval = 600 + +# authorization +rpcauthorization = 1 +rpcauthprovider = action_policy +plugin.actionpolicy.allow_unconfigured = 1 +direct_addressing = 1 *Error: Could not back up /etc/puppetlabs/mcollective/server.cfg: Connection refused - connect(2)* *Error: Could not back up /etc/puppetlabs/mcollective/server.cfg: Connection refused - connect(2)* *Error: /Stage[main]/Pe_mcollective::Server/File[/etc/puppetlabs/mcollective/server.cfg...

Hi, I have looked all over the place and can''t seem to find a complete answer to my query I am setting up MCollective to run alongside my puppet deployment and am having some problems getting it to play as I want it to Basically, I need to make sure that puppet NEVER makes any changes without them being triggered by someone (I honestly can''t see how anyone would ever want

I am currently trying to get mcollective 2.2.4 up and running on RHEL 6 activeqm appears to be running and bound to the correct port, I see the server and client connections to the activemq box. However when I run mco ping all "seems to go well" except I get "No responses recieved" and above that I get the following log messages, debug 2013/05/29 17:02:12: activemq.rb:233:in

...> <import resource="jetty.xml"/> </beans> ---------- client.cfg main_collective = mcollective collectives = mcollective libdir = /usr/libexec/mcollective logger_type = console loglevel = debug # Plugins securityprovider = psk plugin.psk = mcopwd connector = activemq direct_addressing = 1 plugin.activemq.pool.size = 1 plugin.activemq.pool.1.host = puppet.test.italy.cloudlabcsi.local plugin.activemq.pool.1.port = 61613 plugin.activemq.pool.1.user = mcollective plugin.activemq.pool.1.password = mcopwd # Facts factsource = yaml plugin.yaml = /etc/mcollective/facts.yaml and th...