similar to: puppet kick not working against windows service

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 deployed MCollective to our Puppet clients. approx. ~ 200. Our platform requires the most secure setup possible, so PSK as securityprovider is not an option. Therefor I changed the security provider to aes_security reusing puppets certificates in the server.cfg as found in the docs (1) Our goal is to use mcollective to offload event-driven actions to agents running on designated nodes from

I''m trying to install mcollective on an environment for the first time and I''m having troubles: MC client (also the puppet master) activemq.xml <!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The

We are using Enterprise Ruby - I want to dig into Mcollective; however, there is no installation script in the *.tgz. Also, the rpms have various requirements from the stock distribution (RHEL5 in my case) that are already present under our Enterprise Ruby installation. Is there some clever way to weave this together. How to install the Mcollective without the typical setup.rb scripting.

I find the cause of the problem, because the client and server time not synchronization. 发件人: 刘亚丹 [mailto:lyflyd@gmail.com] 发送时间: 2012年7月10日 10:10 收件人: ''puppet-users@googlegroups.com'' 主题: puppet mcollective problem Hi, I am a new puppet user . I had some trouble when I using the mcollective. Soft info: Mcollective :2.0.0

Im new to puppet and installed it in my home lab to mess with, when i installed it i used the hostname rather than FQDN so went back and changed puppet and reran the certificate tool to regenerate the certificates etc, the agent works fine now but i am getting an mccollective error i think, is there anything in the config i need to change for mccollective after altering the name to the FQDN?

Hi All, I have a working installation of a Puppet Master (CA) with Puppet agents, this using The Foreman. I really see the usage of Puppet this way but because The Foreman supports pushing your classes/templates to you nodes (agents) and uses the depricated Run/Kick for it I''m looking into Mcollective. Mcollective is supported by The Foreman since 1.2, the version I''m

I''ve been trying to find information, suggestions, etc. for how to combine scaling Puppet with the use of management tools like Dashboard/Foreman and MCollective. Our current thinking for an initial deployment is two VMs as Puppet Master worker nodes fronted by a pair of NetScalers. However, I''m not sure how to go about implementing Dashboard or Foreman and MCollective servers in

When attempting to execute the mcollective puppet plugin: # mco puppet runonce -v aixl : execution expired aixj : execution expired I get an error, ''execution expired'' on some hosts. However, these hosts respond via mco ping and, I have verified the date/time on the servers. The puppet agent is also

I''m running a previously working set of modules with the Puppet master version 3.1.0-rc2. I''m getting the Error: stack level too deep Here is a chunk of the debug Debug: Scope(Class[Zabbix]): Retrieving template zabbix/zabbix.conf.php.erb Debug: template[/etc/puppet/environments/production/modules/zabbix/templates/zabbix.conf.php.erb]: Bound template variables for

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

Hi everyone, I run MCollective 1.2.1 together with ActiveMQ 5.5 under Scientific Linux 6.1 on Amazon EC2. Overall it works like a charm, but sometimes (eg. 1/30) discovery fails. Still the exit-code of mco will be 0, which is a problem for me as I use MCollective e.g. to trigger deployments from Jenkins. I would like to ask for some feedback on the following ideas, that could fix this problem.

I have a test setup like this: host ======= *puppet-idc*: Ubuntu 12.04 running ActiveMQ, Mcollective, puppet agent and server *puppet-node1*: Ubuntu 12.04 running MCollective and puppet agent *puppet-node2*: Ubuntu 12.04 running MCollective and puppet agent *puppet-node3*: CentOS 6.3 running MCollective and puppet agent I installed the *mcollective-plugins-puppetd plugin* on all *3 Ubuntu

Dear readers, I was shocked to see that "puppet kick" will be deprecated in 3.0.0 https://projects.puppetlabs.com/issues/15735 How can MCollective replace "puppet kick"? Hugs, Sandra -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit

Hi List, I would like to discuss with whoever is interested one topic that I suppose has general interest. I want to implement some kind of automatic testing on the status of a node after a Puppet Run. These tests involve trivial and less trivial things things like: - A local service is running - A local port is open - A remote server on a remote port is reachable by the node - An URL replies

Hi all, I''ve set up a Puppet environment with a master managing around 80 agents. I would like to set a limit on the number of agents that can be performing puppet runs at any given moment...so, for example, if there are already 3 puppet runs ongoing, the 4th agent should be put on hold until one of the 3 runs finishes. Is there a way to configure this? It would be perfect if it can be

Hello, I''ve mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2 setup from http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML. Now I''ve create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/ customer_status.rb. On the client; Running facter customer_status works. Running ''puppet agent --test'' works, customer_status

hi all , i want to disable runinterval option on puppetd . as i know , after every 1800 sec.( 30 mins) , puppet client pull configuration from puppet master . I want configuration to be pushed to puppet client when i wwould fire puppetrun on puppet master rather than after every 30 min , configuration pulled puppet client. runinterval :How often puppetd applies the client

Hello! By default puppet node connects to server periodically and looks if there is something execute. I''m wondering is it possible to make puppet clients not connect to server themselves? So that it would be possible to update a node only with puppetrun nodename. --- WBR, Sergey -- You received this message because you are subscribed to the Google Groups "Puppet Users"

I am experiencing a curious event, and wondering if others have seen this... As well, I have a question related to it. Today, I noticed my puppet summary report from Foreman this morning, that 60 of my 160 hosts all stopped reporting at nearly the exact same time, and have not since restarted. Investigating, it appears that my puppetmaster temporarily ran out of disk space on the /var