similar to: Puppet/Nagios/PuppetDB slow performance

I am using stored configs to manage my nagios host and services checks and I have run into a problem that I have been unable to solve. When the stored configs are purged from puppet the nagios server correctly removes them from the services and hosts file but does not notify the nagios service and instead throws an error. So the entries are still there and nagios still reports on them until

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 everyone, I recently ran into an issue where my puppetmaster can''t run puppet on itself. It errors out with the following: Error: Could not retrieve catalog from remote server: execution expired Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run I''m running Puppet 3 with passanger and puppetdb (hsql). I''ve tried restarting

Hello All, I''m reviewing switching to puppet from chef and am trying to identify how to port the various features. I have hit a stumbling block searching for nodes. In Chef i could search for a node by role, but I am lost as how to do this with puppet and classes. Example: I want my load-balancing node to look for all application server nodes and grab their ip address (and hostname

Hi all, I''ve just merged in support for builtin Nagios types into the 0.24.x branch, and I''d like people to give them a once-over before I incorporate them into a release (based on a few (hopefully small) outstanding bugs in 0.24.1, I expect I''ll put out a 0.24.2 in the next week or so). The only thing I''d currently consider a gotcha right now is that

PuppetDB 1.3.0 is now available for download! This is a backward compatible feature release of PuppetDB. ============= ## Downloads ## ============= Available in native package format at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Puppet module: http://forge.puppetlabs.com/puppetlabs/puppetdb Source (same license as Puppet): http://github.com/puppetlabs/puppetdb/ # Documentation

Is this the best option for accessing puppetdb data from modules? http://forge.puppetlabs.com/dalen/puppetdbquery Any other recommendations? -- 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 puppet-users+unsubscribe@googlegroups.com. To post to this

Hi folks, For the first time since I started playing with puppet I started down the road of using exported resources This was inspired by my reading all of the nagios related recipes that went something along the lines of class nagios { package {nagios: ensure=> latest } service {nagios : ensure => running , enable => true} Nagios_host <<! !>>

I''m trying to query puppetdb for a list of hosts maching a certain regex (on hostname) and only returns 2 facts (ipaddress and hostname) I''m trying to follow: http://docs.puppetlabs.com/puppetdb/latest/api/query/tutorial.html and I''m not even quite sure, wether or not, I should use a facts or a nodes, or a resources query ? I get some of the queries to return just

I have puppetdbquery working on my puppet-2.7.16 puppet master but I am getting an error when using it with puppet-3.0.0-rc5 https://github.com/dalen/puppet-puppetdbquery This is the error I am getting: err: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined method `start'' for #<Puppet::Network::HTTP::Connection:0x7fa6e25db7c8> How would I go

It seems that the nagios_service type will not write out the "name" property of nagios service objects. I had thought this was an oversight or a bug, till I saw this thread: http://www.mail-archive.com/puppet-bugs@googlegroups.com/msg10387.html which seems to imply that this is a deliberate "feature". Is this prohibition on "name" really the desired behaviour?

Hi folks, I noticed an interesting problem with the nagios_* providers especially in Debian. Besides writing to the wrong file (I fixed that issue) I''ve noticed there is a umask issue where the config files end up being owned by root with perms 0640. This causes nagios to spit milk out of its nose because it cannot read the configuration files. I came up with a kludgey solution to the

Hi, Since the below is a little long, I put my question at the top: how do I troubleshoot awful exported resources performance in puppet and is there anything I can tweak to get it to run under 10 minutes in larger environments? I have a fairly modest environment (118 nodes, but prod will be at least twice as large). I''m trying to move my distributed nagios setup to one based on

PuppetDB, a component of the Puppet Data Library, is a centralized storage daemon for auto-generated data. This initial release of PuppetDB targets the storage of catalogs and facts: * It’s a drop-in, 100% compatible replacement for storeconfigs * It’s a drop-in, 100% compatible replacement for inventory service * It hooks into your Puppet infrastructure using Puppet’s pre-existing

Hello ! I''m using a lot of nagios_ commands in my puppet manifests and I saw a problem when using ''undef'' in exported resources : Here is a simple example : define nagios::service::distributed ($ensure=present, $service_description, $host_name=false, $contact_groups=false) { nagios_service {$name: ensure => $ensure, use =>

I have some middleware where the successful configuration of node B is dependent on the successful configuration of node A. Node B must pull additional information from node A during its configuration. Is there any built in functionality in puppet for checking the completion status of other nodes? Right now my intent is to write a custom function to query the puppetdb which is storing

All- Poking around in the bug database it looks like storeconfigs is being actively worked on. I am using 2.7.6 on my master as well as all the clients. I have clients boot , start puppet and get a signed cert via auto signing. The nagios module (and currently the only thing puppet does) complains a lot during compile time about not having storeconfigs enabled, which is not the case in my

I have a requirement where I want a Fact to be stored in PuppetDB during the manifest run and not during the initial fact gathering phase. I know I can, in my manifests, create a file in /etc/facter/facts.d or I can write a Ruby script that will then be distributed by plugin sync. But both of these methods will only publish the fact during the initial phase of the puppet agent run. What I

Hi, I have a Ruby class in "nagios" module - it''s located in nagios/ manifests/ssa_nagios_checks.rb and looks like this hostclass :ssa_nagios_checks do ... end In nagios/manifests/init.pp I have class nagios::server { ... include ssa_nagios_checks ... } And I get the following error .... debug: importing ''/etc/puppet/modules/nagios/manifests/

Hello, I am currently trying to get the puppetdb dashboard and the puppet dashboard working on the same system. Puppet dashboard is working great but after "successfully" installing puppetdb following puppet''s opensource instructions the puppetdb dashboard just doesn''t seem to exist (according to some sites I should be able to get to it by going to