search for: nagios3

Dear all, I''m seeing this strange thing: When I run "*puppet agent -td*" on the node (Nagios, in this example case), puppet fails to install Nagios3 (on Debian) with this: Debug: Executing ''/usr/bin/dpkg-query -W --showformat ${Status} ${Package} > ${Version}\n nagios3'' > Debug: Executing ''/usr/bin/apt-get -q -y -o > DPkg::Options::=--force-confold install nagios3'' Error: Could not update: Exe...

...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 two tags a hostname and a puppetclass. So when I decommission a server the puppetmaster recognizes...

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 prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (...

...9;'nagios'', } } When this definition is run, it seems that ${nagios_cfgdir} and $ {name} are undefined. I am probably missing something quite simple, but I cant put my finger on it ... Any help ? My Nagios class is as follow : class nagios { $nagios_cfgdir = ''/etc/nagios3'' include apache package { nagios3 : alias => ''nagios'', ensure => latest; [ ''nagios3-common'', ''nagios-plugins-basic'' ]: ensure => installed, before => Package[''nagios''...

...eving 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: /Stage[main]/Xxx::Nagios::Server/File[/var/lib/nagios3]: Failed to generate additional resources using ''eval_generate'': Cannot manage files of type fifo notice: Finished catalog run in 3.63 seconds Secondly, I think puppet is smoking crack. Why is it telling me that it can''t manage files of type fifo when that is not what th...

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

...0 tagmail.rb The foreman is "err: Could not autoload foreman: Function foreman already defined" And the storeconfig is: " warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 21 in file /etc/ puppet/manifests/classes/nagios3.pp warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 22 in file /etc/ puppet/manifests/classes/nagios3.pp warning: You cannot collect exported resources without storeconfigs being set; the collection will be ignored on line 24 in f...

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

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 to do this? I tried to e...

When an error occurs in prerun_command, puppet continues execution instead of stopping. We can see the error at the log file, but puppet cotinues doing changes: puppetd[18430]: Failed to prepare catalog: Could not run command from prerun_command: Execution of ''/path/to/command'' returned 1: We want to prevent changes when an error occurs in prerun_command. Our puppet.conf:

...;'m curious to see what others came up with to fix this. For those that are curious as to how I fixed the "wrong file" problem I came up a solution where in my site.pp file I have the following: if ( $operatingsystem == "Debian ) { Nagios_host { target => "/etc/nagios3/conf.d/puppet_hosts.pp" } --- etc --- } -- Peter L. Berghold Owner, Shark River Technical Solutions LLC -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com....

So, my favorite RPM repository (EPEL) only has the ancient nagios-2.12 or so. What's the repo you use for Nagios 3? -- Florin Andrei http://florin.myip.org/

...9;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 non-automated nagios3 server is configured: Each service is declared once per type (or type+role, but there are very few types distinguished by role, so we''ll ignore that for now). Services are members of hostgroups and servicegroups, and hosts join hostgroups in order to activate monitoring. Servicegrou...