similar to: Disable masterhttp.log

Hi all, I''m working on setting up Puppet to write out my Nagios configs. A few weeks back I inserted a few dummy Nagios checks into my Puppet config, and the Nagios configs were written out properly. I''ve now added loads of Nagios host and service checks like this: @@nagios_service { "check_smtp_${hostname}": check_command =>

Hi all, I''m aware that using a "define" can be used to create multiple resources from a list of items, like this: define print { notify{"the message is: ${name}": } } print{["one", "two", "three"]: } This would be the same as making these resources by hand: notify{"the message is: one": } notify{"the message is:

Hi all, For months now I''ve been using Puppet with PuppetDB backend to manage my Nagios configs. We now have 1200+ services being checked and including servicedependency, host, hostdependency, command and other Nagios resources being managed, that''s about 3000 resources in total. Unfortunately this means the monitoring server takes about 8 minutes to perform a Puppet run.

Hi, I''ve just been configuring my new Puppet 3.1.1 / Dashboard setup with Passenger to use PuppetDB for the inventory service. I configured it via the puppetdb forge module, and it all seems to be configured correctly as far as the docs describe. When I look at a node in the dashboard, under the inventory section, I just see: Could not retrieve facts from inventory service: 404

Hello, Puppet client is receiving the 500 error when trying to talk to the puppetmaster server. Apache error log on the server shows -> Could not prepare for execution: Got 1 failure(s) while initializing: change from absent to file failed: Could not set ''file on ensure: Permission denied - /var/lib/puppet/log/masterhttp.log Permissions on this file are open and the file is owned

Dear all, I see this error message in my *masterhttp.log* repeatedly: ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0 state=SSLv3 > read client certificate A: tlsv1 alert unknown ca > I saw a similar mail in the list but there was no definitive answer to that post. Does anyone know what am I missing here? I do understand what *unknown ca* means but I can''t think

Hi all, I''m having some problems working with puppet-selinux[1] I''ve successfully deployed the module in nodes.pp and got it to set various SELinux modes, by using class { selinux: mode => ''permissive'' } or class { selinux: mode => ''enforcing'' } Now I want to load a custom SELinux policy file. According to the docs, the correct

I''m a noob puppeteer. I''m following the directions here: http://shapeshed.com/setting-up-puppet-on-ubuntu-10-04/ I''m running two identical Ubuntu VMs. I can apparently set up the master ok. But, when I try to connect with an agent I get the following error from the agent: Error: Failed to apply catalog: SSL_connect returned=1 errno=0 state=SSLv3 read server

Hi chaps, Since overnight, my puppetmaster has been crashing every now and then (it has crashed about 5 times this morning). We upgraded to puppet 3.2.2 about a week ago but the problems only started this morning. There was nothing in the logs so I ran it in debug mode and captured this: /usr/lib/ruby/site_ruby/1.8/puppet/util/methodhelper.rb:14: [BUG] Segmentation fault ruby 1.8.7

puppet maser conf: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl [master] classfile = $vardir/classes.txt localconfig = $vardir/localconfig user = root group = root fileserverconfig = /etc/puppet/fileserver.conf reportdir = /home/logs/puppet/reports masterhttplog = /home/logs/puppet/masterhttp.log masterlog =

I have the reporting enabled on puppet and am seeing several errors per day from random clients. The errors on the client are always ''cannot retrieve file metadata'' errors, for example (from a client machine''s syslog): puppetd[22451]: (//syslog-ng/Config-file[syslogngconf]/File[/opt/ syslog-ng/etc/syslog-ng.conf]) Failed to retrieve current state of resource: Could not

Hi, I just upgrade my puppet server from version 2.6.7 to 2.7.3 and now I can''t connect new clients. When trying to connect the clients I''m denied with the following error message: err: Could not request certificate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed. This is often because the time is out of sync on the server or

After upgrading my puppetmaster to 0.24.7 from 0.24.6 i am getting the following errors in the puppetmaster logs. Any help would be appreciated. Thu Dec 18 16:11:39 +1100 2008 Puppet (err): Could not store configs: undefined method `environment='' for #<Puppet::Rails::Host:0xb72c0c38> I do not use environment''s and they are not defined anywhere in the puppet.conf

Hi all, I am new to Puppet and now I do some test with 2 Virtual Machines running Centos 6.4 and puppet 3.3.1 And I manage to sign the client cert, but still I can not get any file updated on the client VM. If I run the client in test mode puppet agent --server=p-master.localdomain --noop --test There is no errors in the output. Info: Retrieving plugin Info: Caching catalog for

Hello, I''m new to Puppet, and I''m trying to configure my first Agent/Master node. It''s running under 3 VM''s (Ubuntu server 12.04), a master running with Passenger, and 2 Agents. (But I''m only configuring one at the moment) Well, I followed this<http://engineering.yakaz.com/managing-an-infrastructure-datacenter-with-foreman-and-puppet.html>

Can someone, anyone, help me understand what it takes -- if indeed it''s even possible -- to use a custom CA with puppetmasterd. Such that, for every client it signs, the cert for that client actually says something meaningful about my organization, and was ultimately signed by our own root CA. I made a valid sub-CA for my puppet server, signed by my organization''s root CA. I

Over the years many shops have come to start running puppet via cron to address memory leaks in earlier versions of Ruby, but the official position was that puppet was meant to be run as a continually running service. I am wondering if the official position has changed. On one hand many if not all of the early Ruby issues have been fixed, on the other, the addition of mcollective into the mix as

I left my new puppetmasterd running last night. came in with a stack trace below. A number of questions: 1. Where did /Settings come from? 2. Is there a way to dump the contents of the catalog to understand? 3. I want to change the perms for all that stuff 4. puppetd is not running on this host, does puppetmasterd act like a puppetd? notice: Compiled catalog for inst01.corp.631h.metaweb.com

Hi friends, Somehow puppetmasterd 2.6.5 is failing to get started on Centos 5. I am getting the below error. I am yet to configure any agent with this server. puppetmasterd --no-daemonize --verbose --debug debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/ dscl does not exist debug:

Seeing ''SSL_read'' errors being logged by puppetmaster. Anyone know what causes these or how to correct? They''re sporadic, not happening all the time or on all puppet runs. /var/log/puppet/masterhttp.log [2011-07-25 10:00:10] ERROR OpenSSL::SSL::SSLError: SSL_read:: internal error /var/log/messages Jul 25 10:00:10 cmd-box puppet-master[22572]: SSL_read:: internal error