search for: nagios_

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

...nately this means the monitoring server takes about 8 minutes to perform a Puppet run. I''m not exactly sure what the bottleneck is - whether it''s doing 3000 calls to PuppetDB (although the load on the PuppetDB server and its Postgres database are low), or whether it is parsing nagios_service.cfg that causes the slowdown. It''s about 500kb and 11,000 lines. I know it is possible to squirt the Nagios config into several smaller files when the resources are collected on the monitoring server, but I gather this also means that Nagios resources cannot be purged if the de...

...em 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 the default target is /etc/nagios/nagios_<name>.cfg. It''s basically trivial to change this, but I had to start somewhere. If you look in lib/puppet/type/nagios*, you''ll see basically one-line files, since each of the types is just generated using the model I created in my Naginator[1] library. Can anyone th...

...able 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 it is restarted. (/Nagios_service[check_ping_jasontest2.wishabi.net]) Whit[Completed_stage[main]],Whit[Completed_class[Nagios3_monitor]],Service[nagios3] still depend on me -- not purging The reason that I want this feature is that I have created several automation scripts so I can start a service through AWS giving it t...

Was just wondering, before I went too far down this path... I have to use Hyperic for monitoring and alerting. I''ve got... 110+ apps to monitor spread across 3 clusters of 3 nodes. I''ve puppetized nearly every other aspect of this setup, so am now looking to puppetize the monitoring. I know that puppet has rather extensive, built in support for Nagios, and I have heard that

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

Hello all, what exactly is the "design decision" that is needed here? We currently have the problem that 0.23.2-3 (debian package) does not work when it comes to collecting exported resources. The resources are saved in the database, so picking them up is the problem (db is Mysql5.x). This is a major problem for us, since we are using this a lot for our monitoring services. I

...alias => nagios, ; } service { nagios3: ensure => running, alias => nagios, hasstatus => true, hasrestart => true, require => Package[nagios], } # collect resources and populate /etc/nagios/nagios_*.cfg Nagios_host <<||>> Nagios_service <<||>> Nagios_hostextinfo <<||>> class target { @@nagios_host { $fqdn: ensure => present, alias => $hostname, address => $ipaddress, use => "generic-hos...

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