Re: [Puppet Users] Puppet/Nagios/PuppetDB slow performance

On 24.05.2013 16:58, Ken Barber wrote: Its probably the nagios resource, its well known for not scaling when the files contain a lot of entries. That would explain why your PuppetDB is showing low load - as its probably not the bottleneck. I second that. We have mysql storeconfigs, about 5000 S

Re: [Puppet Users] puppet-lint crashes and burns

On 11.07.2012 16:55, Peter Berghold wrote: [peter@chits1 manifests]$ ruby -v ruby 1.8.5 (2006-08-25) [x86_64-linux] [peter@chits1 manifests]$ ruby -v ruby 1.8.5 (2006-08-25) [x86_64-linux] [peter@chits1 manifests]$ uname -a Linux chits1.chi.sharkrivertech.com

Re: AW: [Puppet Users] OT: Monitoring solutions

On 25.06.2012 14:45, Bernd Adamowicz wrote: We got a totally integrated solution made up with Puppet, Icinga and stored resources. When integrating a new host into Puppet, one just has to wait until it gets monitored in Icinga - no more work to do. Some details are found here: http://www.bernd-ad

Re: [Puppet Users] Error 400 on SERVER:

Could not retrieve catalog from remote server: Error 400 on SERVER: No support for http method POST err: Could not retrieve catalog; skipping run Wild guess: Please check if your client is running a later version of puppet than the server. This error happened to me when my clients where upgrad

Re: [Puppet Users] Re: Puppetcamp

Someone else wanna join? Someone is going to stay at Eden Hotel? I will be arriving proably late in the evening at the 26th (around 9pm). Staying at the Best Western. Would like to join whatever you guys are doing if its still going on around that time. Regards Alex -- You received this mes

[Puppet Users] Re: yum provider executes rpm -e?

Fletch wrote: > I also noticed this today. > Is there a better yum provider? > I want to ensure cups and all the crap it comes with is absent. > puppet calls rpm -e cups and fails on dependencies check. We discussed this on irc a couple of days ago. I cant seem to find the logfile but if i remem

[Puppet Users] make sure module_xy (if present/defined) is executed before everything else

Greetings, Lets say i have a module, 'centos_base'[1] which kinda bootstraps or keeps a system to a certain standard. Packages, timezones, yum repos & prios, snmp config, ssh_auth keys, stuff like that. Now, i would like to make sure that if a node has this module, it should always be execute