similar to: Puppet agents stop reporting after master runs out of disk space...

I had installed puppet master and client on two different machines. machine A has puppet master and machine B has client. both are centos6 64 bit machines. Machine B (client) is successfully connected to master (machine A). My aim is to install New Relic agent (server monitorinig tool) on different clients. I had installed new relic agent on machine A and trying to build a module so that I

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, I want to run Puppet on a Windows 2003 Server. I already have a working Puppetmaster (Scientific Linux). I installed Puppet on Windows like shown here: http://projects.puppetlabs.com/projects/1/wiki/Puppet_Windows This worked very well. But when I want to run puppet. puppet agent --test --debug I get the following output: (I already tried different ruby and puppet versions without

Hi, This is the third or fourth time this happens. But puppetd gets a zombie shell childprocess and then never finishes the run. /opt/tc-puppet/bin/ruby /opt/tc-puppet/sbin/puppetd \_ [sh] <defunct> How do I begin looking on what can be wrong? This error has appeared on both 2.7.6 and 2.7.11. Regards, Elias -- You received this message because you are subscribed to the Google Groups

Hey all, I''ve been messing around with the hiera-foreman backend to see if it would let me migrate to hiera and use foreman and an ENC. https://github.com/torrancew/hiera-foreman It works by querying each node''s yaml file from foreman. Currently this code works when called from the hiera command line with the -m (mcollective option). It uses the mcollective facts to pull

We have a policy that requires all user passwords to expire after 90 days. We also use puppet for managing all users on our machines. Our hope was, when our passwords expire, we could update the puppet manifest which would propogate to all our servers, thus updating all our passwords. The problem is, the User type (w/ manage_passwords enabled and ruby- shadow installed) will only set the

Now, I am getting this .... Thanks for the help! puppet5 : Cannot validate input: Unknown validator: ''puppet_server_address''. Cannot validate input: Unknown validator: ''puppet_server_address''.puppetdev04 : Puppet command ''puppet agent --test --onetime --daemonize --color=false --no-splay

Hi, I have a Puppet Enterprise (2.0) puppetmaster running with Foreman, and having trouble getting it working as an External Node Classifier. In short, if I manually add a test client into site.pp, it will retrieve the proper catalog / classes, but I would like to avoid having to do that. I''m also using environments (production/testing/ development) as well, but think I have most of

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

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 -

http://saltstack.org/ http://puppetlabs.com/mcollective/ I found this link that talks about Func, Rundeck, Salt and mcollective, but it doesn''t really compare and contrast. http://www.coloandcloud.com/editorial/func-mcollective-salt-and-rundeck/(From a 10,000 overview Saltstack and mcollective look very similar. IE: both integrate with facter/puppet, have queuing mechanisms, allow remote

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

Hello, I''m trying to use External Node classification and I have not idea what is my mistake. I getting the following error : err: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `downcase'' for ["hola", {"mens"=>"HOLA"}]:Array on node casa I have a very simple parameter class : class hola( $mens =

Hi All, We are observing frequently issue that Puppet agent intermittently stops without doing any thing when lot of puppet agent hitting puppet master . In our environment , we have configured puppet master over Apache-passenger and we have used LDAP as node classifier. - puppet 5.5 - Apache-passenger 3.0.17 - CentOS 6.3 / 5.5 - OpenLDAP 2.4 Sometimes restarting Apache solves

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

New install of 2.5.1 on Ubuntu 10.10 server. Multiple (6) new installs on Ubuntu 12.04 clients running agent 2.7.14-1puppetlabs1 from the puppetlabs repo generating the following error. err: Could not retrieve catalog from remote server: Error 400 on SERVER: No matching value for selector param ‘undef’ at /opt/puppet/share/puppet/modules/pe_mcollective/manifests/init.pp:89 on node

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

So I''m new to puppet and I''m having a bear of a time just getting a test server going. I installed puppet and the puppet client via yum on CentOS on AWS, so that saved me some time. I followed a few various blog posts about getting everything set up and applying a file, etc. Now I am trying to install a module (puppetlabs/apache) and it''s failing miserably for me. I

Hello Everybody, I am trying to install the puppetdb on the same machine as am running my puppetmaster. I am getting the following error when am trying to connect the agent: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit ''replace facts'' command for ftldwshost180.wsdev.citrix.com to PuppetDB at