similar to: mcollective puppet plugin not working for centos

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.

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

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

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

*Not sure if this a feature or a issue, if its a feature is there a way to configure it in puppet or mcollective? 1st Attempt(Failed) ------------------------------------------------------------------------------------------------------------------- * [root@mcqpuppetserver ~]# mco puppet runonce -v Discovering hosts using the mc method for 2 second(s) .... 1 * [

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?

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

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

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

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

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

An HTML attachment was scrubbed... URL: http://oss.oracle.com/pipermail/ocfs2-users/attachments/20110303/0fbefee6/attachment.html

Hi all, I am currently deploying tinc as an alternative to OpenVPN. My setup includes a lot of nodes and some of them are sitting together behind the same router on the same network segment. (E.g. connected to the same switch.) I noticed, that those nodes do never talk directly to each other via their private ip-addresses, but instead use the NATed address they got from the router.

I''m getting these errors when running ''puppet agent --test'' after doing a new installation of an agent: err: /Stage[main]/Pe_mcollective::Plugins/File[/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb]/content: change from {md5}512f42272699eaa085c83d2cc67c27ea to {md5}8fa3e9125fd917948445e3d2621d40e5 failed: Could not back up