search for: registerinterval

...uppet agent +plugin.puppet.config = /etc/puppetlabs/puppet/puppet.conf + +plugin.puppet.splay = true +plugin.puppet.splaylimit = 120 + +# Periodcally broadcast metdata for registration purposes. +# This registration plugin will broadcast current Facter fact values. +registration = Meta +# registerinterval is intentionally "long" to 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....

...# Basic stuff registration_collective = mcollective libdir = /usr/libexec/mcollective logfile = /var/log/mcollective.log loglevel = debug daemonize = 1 main_collective = mcollective collectives = mcollective # Plugins securityprovider = psk plugin.psk = mcopwd # Registration #registerinterval = 300 #registration = Meta # Middleware connector = activemq 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 plugin.activemq.pool.1.ssl = 0 # NRPE #plugin.nrpe....

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

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