similar to: Interesting permissions issue with nagios_* providers

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

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

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.

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

Puppet version: 0.22.4 facterversion => 1.3.7 rubyversion => 1.8.5 Given the following: file { yum_repo_d: path => "/etc/yum.repos.d", ensure => directory, recurse => true, purge => true } yumrepo { pkg_repo: descr => "Packages Repository", enabled => 1, baseurl => "http://Some/path/", gpgcheck => 0,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I''me using nagios builtin types and I''m very surprised that the parameter *name* is not available for type nagios_host ?!? This parameter is required to use inheritance (http://nagios.sourceforge.net/docs/3_0/objectinheritance.html) and I don''t understand why it is not included in all nagios types ? Maybe someone has

We were using Naginator resources like nagios_host, etc. along with stored configurations and exported resources. Worked pretty well. However we have to separate the Puppet master and the Icinga (Nagios) server. They will be on different machines from now on. Are there any best practices for such a scenario? I already thought about some kind of ''rsync'' of the configuration from

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

I''ve tried to achieve my overall goals with several different features of Puppet, but I''ve hit a bit of a wall here. I think it''s time for me to explain what I''m trying to accomplish: I want the enabling of a service in my manifests to configure the monitoring of that service by a nagios server, without needless repetition. Let me explain how my

hi All, I''m a bit new to puppet. Is there a mailing list for puppet beginners?:) I have a service module called postfix, which defines file in a class: file { ''/etc/postfix/main.cf'': owner => "root", group => "root", mode => 644, content =>

Hi, so I''m trying to use the built in nagios_host type and there appears to be one huge glaring hole - the lack of a hostgroups parameter. And before anyone asks why I can''t use the nagios_hostgroup type, if someone can tell me how I can collect members without having to manage the hostgroup members manually, that would be fantastic. There''s a servicegroups parameter

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

Hello ! I''m trying to implement a Nagios solution based on David Schmitt''s Complete Config. But I the following error when running puppetd -t - v : notice: Starting catalog run err: //Node[monitoring]/nagios::target/Nagios::Host[]/File[/conf.d/ _host.cfg]/ensure: change from absent to present failed: Could not set present on ensure: No such file or directory - /conf.d/

I''m very interested in the way that puppet appears to be able to generate nagios configurations though I can''t seem to find any documenation on how it works: http://reductivelabs.com/trac/naginator is clearly a placeholder page... Meanwhile the various pieces of info at links such as: http://reductivelabs.com/trac/puppet/wiki/TypeReference#nagios-host are just teasing me.

Observe the following code sniget: user { nagios : comment => "Nagios Host Monitoring Service", shell => "/bin/bash", home => "/home/nagios", ensure => present } file { nagios-homedir : path => "/home/nagios", owner => "nagios",

Couple of questions. Firstly, what''s the plugin error about? puppet agent --onetime --test --verbose info: Retrieving plugin err: /File[/var/lib/puppet/lib]: Could not evaluate: Could not retrieve information from source(s) puppet://puppet/plugins info: Caching catalog for mon01.ap1.xxx.com info: Applying configuration version ''1346878830'' err:

Package: logcheck-database Severity: normal Tags: patch The rules in /etc/ignore.d/server/nagios contain the explicit version number "2". Now that lenny includes nagios3, those rules don't work anymore. Please change the rules to work for both nagios2 and 3. That can easily be done by replacing the 2 by (2|3) for example. -- System Information: Debian Release: lenny/sid APT

I''m sure people have hit this problem before. In my nagios module, the nagios command pipe file at /var/lib/nagios3/rw/nagios.cmd is owned by the nagios user, but needs to be written to by the www-data user. Adding the www-user to the nagios group is one solution, but that requires that the nagios module potentially modify the www-data user, which seems bad. What''s the best way

Is anyone working on Nagios 3.x RPMs? If not, perhaps I'll whip some up and submit them to some appropriate repository. Geoff Galitz Blankenheim NRW, Deutschland http://www.galitz.org