similar to: MCollective and Puppet with periodic runs disabled

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

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

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

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

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

If I want to run Puppet agent only on two nodes out of ten, how can I specify this with the Host Filters? I tried mco puppet runall 10 -I node1,node2 and different other variations, but this does not work. Is this at all possible? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving

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''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

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

I have a puppet server and various puppet agents. I want to do mcollective stuff. So please anyone tell me what should i install on puppet server and agent to run mcollective? Is there any need to install ActiveMQ also and where should i install it? Thanks in advance. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe

I''ve been thinking a lot about running mcollective on my production servers recently, especially about its nice integration with puppet (using facts and so on). However I''ve got some concern about its scalability - how publish/subscribe middleware scales in terms of speed and flooding the network. I run about 2000 servers. Has anyone got any experience running mcollective on

Hi, I am writing scripts for deployment of our software and I am also using MCollective on linux. I hope to use MCollective in order to reduce the requirement of opening a putty session to each VM and running the puppet agent manually the first time (when its registers/ creates keys etc). The problem I see with this is that I need to log in to each machine and install/configure mcollective

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, I am trying to use Hiera in puppet 3 and I have two nodes that both need the same configuration. In this case they are two web servers which have the same apache configuration. Rather than creating two seperate hiera files for node1.yaml and node2.yaml is there a way to group these by role (e.g. webserver.yaml)? I want to avoid duplicating the configuration if possible and keep the data

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 am running puppet 2.7.14 - CentOS 6 server, CentOS and windows 2008 R2 clients. I''m having problems with the "puppet kick" command - it works on linux clients, and on my windows box when "puppet agent --no-daemonize --verbose" is run from a command prompt. However, when I run it as a windows service, I get "Host blah failed: Connection refused -

Hi , I have installed puppet enterprise , master and agent in two nodes in a cluster. Everything works perfeclty except live mangement console . clicking this option take lot of time and finally it doesnot come up. It came 1 or 2 times. Can you explain what could be reason? Thanks Leo -- You received this message because you are subscribed to the Google Groups "Puppet Users"

Can anybody tell me what exactly ActiveMQ does? Is it a storage of messages produced by producer and ready to consume by consumer? M i understanding it correctly or not? Please tell me? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Hi all, I''ve been looking at a potential problem, as documented here: http://projects.puppetlabs.com/issues/19241 To do with a leak within the KahaDB persistence layer of ActiveMQ. Specifically, there are reports of the db.data file growing unbounded: https://issues.apache.org/jira/browse/AMQ-3956 I''m hoping to find out information from other PuppetDB users to see if this is