similar to: Puppet nagios integration problem

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.

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

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?

Hello, I have another quick one about puppet dashboard. We are using the Debian one for Squeeze (1.0.4) and as the database has significantly grown, if/when we click on a list of unresponsive nodes to check them, the web interface sits there doing nothing then the puppetmaster process starts timing out for all nodes compiling their catalogs. Has anyone got a workaround for this? Does it involve

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:

I''m trying to generate (and manage) nagios configuration based on what classes have been included by nodes. I''ve seen the example at http://docs.puppetlabs.com/guides/exported_resources.html, and I''m doing that now. However, it has some problems: - puppet runs are very slow on the nagios node - when I want to change the service configuration in nagios, I have to wait

Anyone hosting deb packages for puppet 2.6.9, or know how to build it from the tar.gz. I know sid has 2.7.1 but i''m after fixes in 2.6.9, which I think won''t be up-streamed until 2.7.2 I''ve been using 2.6.5 along with the init.d scripts. I had a look in the tar.gz of 2.6.9 but couldn''t find the service scripts or any control files. Cheers, Matt -- You

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

Hello all, I use puppetmaster on a Debian Squeeze server (packaged from Debian 2.6.2-4) I am using a template for Debian Servers which works great for Lenny in order to update my sources.list automagically, here goes: deb http://ftp.ie.debian.org/debian <%= lsbdistcodename %> main contrib non-free deb http://security.debian.org/ <%= lsbdistcodename %>/updates main Now the problem

Hi, I''m happily aware of the way that there is no concept of unmanaging something and when this is in the context of a file ownership or whatever, then that makes sense. But when this is applied to things like nagios configuration data the principle seems to come unstuck. Or at least, it seems so to me. Say I have a nagios_service which uses another template nagios_service. I am about

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

Hi Steve Thanks for all your help, i followed your answers and found on that nagios was being run as user nagios....and if i executed the last command it asked for a password [i tried nagios password,root password etc] but it did not work..it the end i opened nagios.cfg and changed the NAGIOS_USER to root and changed the ownership permissons on the script also to root..I now get the correct

Folks: I''ve started to play around with the comprehensive integrated module set from example42 (http://www.example42.com/). Following the instructions, I set up one node as a nagios server, with ''include nagios''. I set up another node to be monitored via nagios, with ''include nagios::target". I set $monitor=true for the base node, which is inherited by

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

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/

Hello, Has anyone managed a successful installation of Nagios using the RPMForge packages on CentOS 5.5? It looks like it should have worked, I followed the guides for Fedora and CentOS here (with appropriate path adjustments): http://nagios.sourceforge.net/docs/3_0/quickstart-fedora.html http://wiki.centos.org/HowTos/Nagios The SELinux policies look fine (I tend to ignore instructions to

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

Hello CentOS users, I have problems posting the question below to the Nagios mailing list (my subscription is not accepted for some reason). Has anybody of you already had this probably frequent problem with Nagios in CentOS? I can''t use check_squid from command-plugins.cfg (s. below) Thank you for any hints Alex ---------- Forwarded message ---------- To: nagios-users at

Hi I would like to contribute to the wiki.centos.org: username: boel subject: nagios incompatibility with centos 5.2 location: http://wiki.centos.org/HowTos/Nagios content: A security feature of centos 5.2 SELinux prevents the access from the apache httpd server to the needed /var/nagios files. The error manifests itself in the /var/log/messages as "SELinux is preventing the tac.cgi from