Howdy,
After working just fine for a long while, I'm suddenly running into this
error on my puppetmaster and any other host that touches the nagios types.
Error: Failed to apply catalog: Could not parse configuration for
nagios_host: undefined method `For=' for
#
I'm not even sure where t
Hi, do we have any good document on installation of nagios by using puppet.
I am using puppet 4.3 enterprise version and cent os 7. I have checked
couple of url but those are not working.
Thanks,
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" gr
Hi folks,
I'm not sure if I'm thinking about the problem the wrong way, but I'm
trying to design a way to have one directory of user information in
hiera which feeds the creation of unix users as well as nagios contacts.
I have a hiera data structure like this:
unifiedusers:
jon:
nagio
Hi All..
Is that any example Nagios module without storeconfig but using Hiera in
RHEL?
Because don't have time now for build the module need finish deployment
about 1 week :),
I try search via puppetforge so far I have only found with storeconfig for
RHEL, but for debian found by dhoppe. Anybody
Agreed with what Matthias said. Puppet's naginator stuff doesn't play
very well with non-Puppet nagios configurations. Essentially, you have
to pick one of:
- remove the default template from that file, and create it with Puppet
elsewhere
- put all of the contents of that file in Puppet
- total
On Tue, 11 Feb 2014 06:53:42 -0800 (PST)
druide.st...@gmail.com wrote:
> I have a strange problem here. Most of my Nagios configuration are
> from file {} directive, but I also need to modify a couple of Nagios'
> default configuration. To do this, I use classes like this:
>
> class nagios::gabar
Hi,
I have a strange problem here. Most of my Nagios configuration are from
file {} directive, but I also need to modify a couple of Nagios' default
configuration. To do this, I use classes like this:
class nagios::gabarits {
nagios_host { 'linux-server':
use => 'generic-host',
Hi steve,
So, you have all the "services" defined statically on the Nagios server?
That setup only works, I think, if you install your Nagios server at the
very end of your deployment process and all the clients are up and ready
before the server. If you do a parallel deployment, then there is
> What I do know from querying the database is that all the exported resources
> are present in the puppetdb database (in catalog_resources).
Did you query via the REST interface, or the database directly. The
REST interface might be more clear, as this is pretty much what the
puppetdb terminus us
On 9/20/13 10:20 AM, Ken Barber wrote:
What I do know from querying the database is that all the exported resources
are present in the puppetdb database (in catalog_resources).
Did you query via the REST interface, or the database directly. The
REST interface might be more clear, as this is pre
I've set up puppetdb to manage my nagios configuration, running puppetdb
on my puppet server (on ~RHEL 6), and running postgres for the puppetdb
store. The nodes to be managed have some standard nagios host/service
exported resources, e.g.:
@@nagios_host { $fqdn:
ensure => pre
I am using the nagios puppet module to create and manage services via
stored configurations. The original module, stored all service cheks in
one file and this was causing my puppet run on my nagios server to take 30+
minutes. I have read here (
http://pieter.barrezeele.be/2009/05/11/puppet-an
Hi there,
On 30/08/13 05:34 PM, mike wrote:
> [..]
> Error: Could not find any host matching 'node1.example.com' (config file
> '/etc/nagios/resource.d/host_node1.example.com.cfg', starting on line 4)
> Error: Could not expand hostgroups and/or hosts specified in service
> (config file
Hello,
i 'm try automatizando my nagios monitoring i've running puppet with
puppetDB and postgres and this running ok. The problem that present in
this moment is the nagios structure in the server with generate puppet for
example:
When I connect my node agent (puppet agent --test) and my nagios
Hi all - I am setting up dynamic monitoring using puppet/nagios modules.
I am following this doc to achieve basic setup
http://www.allgoodbits.org/articles/view/32
Here is my configs
[root@ip-10-172-161-25 puppet]# cat modules/nagios/manifests/init.pp
class nagios::server {
pack
Hi All,
I currently make use of Icinga (nagios fork) + Puppet for fully automated
monitoring. It's worked great up to this point. I've recently been asked to
integrate fine grained notifications support into icinga. I'm not entirely
sure puppet manifests are the right place to manage contacts,
On Tue, Aug 06, 2013 at 06:20:09AM -0700, jcbollinger wrote:
>
> Because there is a difference between unmanaged resources and resources
> that are managed 'absent'. Only resources that are actually declared for
> the target node are managed, whether declared directly or via collection of
> vi
On Monday, August 5, 2013 3:33:11 PM UTC-5, John Santana wrote:
>
> On Mon, Aug 05, 2013 at 04:22:41PM -0400, Gabriel Filion wrote:
> >
> > you need to export the resource with ensure => absent and run puppet on
> > the host, then on the nagios server so that everything runs fine.
>
> Dozens
On 05/08/13 04:33 PM, puppetl...@downhomelinux.com wrote:
> On Mon, Aug 05, 2013 at 04:22:41PM -0400, Gabriel Filion wrote:
>>
>> you need to export the resource with ensure => absent and run puppet on
>> the host, then on the nagios server so that everything runs fine.
>
> Dozens of VMs are routi
On Mon, Aug 05, 2013 at 04:22:41PM -0400, Gabriel Filion wrote:
>
> you need to export the resource with ensure => absent and run puppet on
> the host, then on the nagios server so that everything runs fine.
Dozens of VMs are routinely destroyed on a weekly basis and in an
automated fashion based
Hi there,
On 05/08/13 10:51 AM, John Santana wrote:
> When I remove the host from the database via
>
> delete from fact_values where host_id='N';
> delete from resources where host_id='N';
> delete from hosts where id='N';
if you remove the host exported resource in the manifests and the DB,
the
Nagios is restarted every time a host or service is added, but never when
removing hosts or services.
The client resources:
@@nagios_host { "$::fqdn":
ensure=> 'present',
alias => "$::hostname",
address => "$::ipaddress",
use => 'linux-server',
}
@@nagios_service
On 06/28/2013 04:57 PM, Stephen Jahl wrote:
In my experience, exporting nagios_command resources doesn't work so
well. What I've found works best, is to define nagios_command{}'s
directly on the server, rather than exporting and collecting them there
later.
In my setup, the only resource that ex
In my experience, exporting nagios_command resources doesn't work so well.
What I've found works best, is to define nagios_command{}'s directly on the
server, rather than exporting and collecting them there later.
In my setup, the only resource that export is the nagios_host. I define
commands and
Shameless plug.
I wrote a module to do pretty much what you are trying to achieve.
http://forge.puppetlabs.com/rendhalver/monitoring
It currently works on CentOS and Fedora. Debian/Ubuntu support is in progress.
I also have a couple of other modules for managing nrpe and icinga
Feel free to have a
Hello folks,
I am currently using Puppet to forge the nagios configuration files. Using
exported ressources it really works well - to a point.
The one thing I am banging my head against is the service definitions. The
services use stuff like remote-nrpe-zombie-procs, which of course, is not
de
I recently downloaded the nagios puppet module (
https://github.com/duritong/puppet-nagios) for my environment. I have
noticed that the lib file 'mountpoints.rb' for this module causes issue
when a windows puppet node is run. When I remove this library file
completely, none of the issues I am
Hi,
On 02/11/2013 02:12 PM, Jamie Cressey wrote:
>
> Is there a way to create a list such as ;
> name1:username1:emailaddress1
> name2:username2:emailaddress2
classic use case for defined types.
http://docs.puppetlabs.com/guides/language_guide.html#defined-resource-types
Your type will look lik
I'm currently defining nagioscontacts one-by-one like so;
@@nagios_contact { username1:
ensure => present,
use => "generic-contact",
contact_name => username1,
alias => "user1",
email => "emailaddress1",
target => "/etc/nagios/conf.d/co
Hi,
Nagios servers tend to quickly become complex beasts :-) I know what
all of the advantages of managing them cleanly with puppet are, never
missing a single typical check from being added ever again being the
main one, but there are so many downsides that I'm still not entirely
convinced that i
Hi all,
I would like to install a nagios server without reinventing the wheel.
I know there's nagios (client?) functionality in core puppet, and a lot of
modules in the forge. Unfortunately, the most promising one, thias/nagios
uses thias/apache_httpd, and I would like to stick with puppetlabs/
On 2012-10-11 14:59, TFML wrote:
> I've got a Nagios setup with puppet to add nodes/contacts/command
> running at one datacenter, I'm trying to setup a second Nagios server
> using the same manifests, but I'm getting this error:
>
> info: Retrieving plugin
> info: Loading facts in snmpd
> info: Lo
How are you setting up the nagios resources?
On 12 October 2012 04:59, TFML wrote:
> I've got a Nagios setup with puppet to add nodes/contacts/command running at
> one datacenter, I'm trying to setup a second Nagios server using the same
> manifests, but I'm getting this error:
>
> info: Retrievi
I've got a Nagios setup with puppet to add nodes/contacts/command running at
one datacenter, I'm trying to setup a second Nagios server using the same
manifests, but I'm getting this error:
info: Retrieving plugin
info: Loading facts in snmpd
info: Loading facts in snmpd
err: Could not retrieve
On 12 September 2012 01:24, Gabriel Filion wrote:
> On 12-09-10 11:32 PM, Peter Brown wrote:
>>> hum, was the purge functionality ever fixed for nagios types? I've
>>> > wanted to use that for some time but fwir it was not implemented.
>> Purge generally works if you don't change the target for an
On 12-09-10 11:32 PM, Peter Brown wrote:
>> hum, was the purge functionality ever fixed for nagios types? I've
>> > wanted to use that for some time but fwir it was not implemented.
> Purge generally works if you don't change the target for any of the
> the nagios types and keep the names the same
On 11 September 2012 12:51, Gabriel Filion wrote:
> On 12-09-10 10:46 PM, Bruno Leon wrote:
>> resources { "nagios_service":
>> #notify => Service["nagios3"]
>> purge => true,
>> }
>>
>> resources { "nagios_host":
>> #notify => Service["nagios3"]
>> purge => true,
>> }
>>
On 12-09-10 10:46 PM, Bruno Leon wrote:
> resources { "nagios_service":
> #notify => Service["nagios3"]
> purge => true,
> }
>
> resources { "nagios_host":
> #notify => Service["nagios3"]
> purge => true,
> }
>
>
>
> And make Nagios service subrscribe to the file /etc
resources { "nagios_service":
#notify => Service["nagios3"]
purge => true,
}
resources { "nagios_host":
#notify => Service["nagios3"]
purge => true,
}
And make Nagios service subrscribe to the file /etc/nagios (cheksum => mtime)
--
Bruno
On September 10, 2012 01:17
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
servic
There should be a "nagcmd" group which both nagios and your apache
user are members of. The nagios.cmd pipe should have permission of
0660 and ownership of nagios:nagcmd. If you were using check_mk
livestatus then the livestatus.cmd socket would have the same perms
and ownership.
Usually this is t
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
No worries.
Glad you got it working.
On 23 August 2012 14:35, Marc Lucke wrote:
> I inherited the module so I'm not sure. I did see some check_commands with !
> and was wondering; I didn't connect the dots.
>
> Thank you!! :)
>
> On 23/08/2012, at 2:18 PM, Peter Brown wrote:
>
>> Hi,
>>
>> $AR
I inherited the module so I'm not sure. I did see some check_commands with !
and was wondering; I didn't connect the dots.
Thank you!! :)
On 23/08/2012, at 2:18 PM, Peter Brown wrote:
> Hi,
>
> $ARG1 in a nagios check is what comes after the first ! in the check.
> Which module are you using
Hi,
$ARG1 in a nagios check is what comes after the first ! in the check.
Which module are you using to generate your nagios setup?
On 23 August 2012 13:44, Marc Lucke wrote:
> I note that the check_https command that the puppet module generates is
> check_http -H $HOSTNAME -S $ARG1
>
> I'd lik
I note that the check_https command that the puppet module generates is
check_http -H $HOSTNAME -S $ARG1
I'd like to specify $ARG1 so that so that I can check return strings, check SSL
certificates et al. but I couldn't find any way to do it other than
nagios_command which seems pretty wasteful
As one who has previously used Puppet to drive Nagios configurations (and
attempted to contribute patches to Puppetlabs), allow me offer a somewhat
fabulous alternative: check_mk. check_mk is a package that can be used to
generate your Nagios configuration in a programmatic fashion. Here's how
it
Hi everyone,
I am reconsidering how I am using the Puppet nagios functionality, at
the moment I am creating one service for each check on each host. A
lot of them are identical, and would be better tied to hostgroups to
simplify my config. Namely, I have about 5,000 checks in there now
which will
Verizon Wireless BlackBerry
-Original Message-
From: Jonathan Gazeley
Sender: puppet-users@googlegroups.com
Date: Mon, 15 Aug 2011 17:03:02
To: Puppet Users
Reply-To: puppet-users@googlegroups.com
Subject: [Puppet Users] Nagios hostgroups
Hi all,
I'm using various exported resources for
wrote:
>
> Sent from my Verizon Wireless BlackBerry
>
> -Original Message-
> From: Jonathan Gazeley
> Sender: puppet-users@googlegroups.com
> Date: Mon, 15 Aug 2011 17:03:02
> To: Puppet Users
> Reply-To: puppet-users@googlegroups.com
> Subject: [Puppet Us
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Jonathan Gazeley
Sender: puppet-users@googlegroups.com
Date: Mon, 15 Aug 2011 17:03:02
To: Puppet Users
Reply-To: puppet-users@googlegroups.com
Subject: [Puppet Users] Nagios hostgroups
Hi all,
I'm using va
Hi all,
I'm using various exported resources for Nagios, including
@@nagios_host, @@nagios_service and others.
Elsewhere in my manifest I am using all of these commands to realise the
resources on my Nagios server. All of these commands work fine except
for Nagios_hostgroup which does not pr
On 03-03-11 08:04, Gabriel Filion wrote:
> On 11-03-02 02:27 PM, Brian Gallew wrote:
>> I've found that Puppet/Naginator has the bad habit of occasionally
>> breaking the Nagios config. Here's how I worked around this: 1) When
>> you collect your Nagios resource, store them all in a temporary
>> d
On 11-03-02 02:27 PM, Brian Gallew wrote:
> I've found that Puppet/Naginator has the bad habit of occasionally breaking
> the Nagios config. Here's how I worked around this:
> 1) When you collect your Nagios resource, store them all in a temporary
> directory (in my case, ~nagios/var/tmp)
> 2) P
I've found that Puppet/Naginator has the bad habit of occasionally breaking the
Nagios config. Here's how I worked around this:
1) When you collect your Nagios resource, store them all in a temporary
directory (in my case, ~nagios/var/tmp)
2) Purge that directory with a cron job every night (so
Hello,
I finally abandoned the idea of having a group-based sane-looking Nagios
configuration with puppet, because there are too many weirdnesses in
Naginator. And unfortunately I can't really bring any help with patches
since I don't write any ruby..
There are some great nagios modules out there
Dude, I struggled with that for more than 6 months, and the position of the
Puppet people was, "you're doing it wrong". Since that didn't help my problem
I ended up doing it this way:
1) Create a new fact (see attached) that reports back to the master server on
what classes are defined on the c
On 02-03-11 14:49, Brian Gallew wrote:
> Sadly, signs point to "no".
Too bad. But since I run a patched Puppetmaster anyway, I can do what I
want :-)
Unfortunately, it doesn't solve my problem.
I am trying to do the same thing as Gabriel Filion in this post:
http://groups.google.com/group/puppet
Sadly, signs point to "no".
On Wed, Mar 2, 2011 at 5:15 AM, Martijn Grendelman wrote:
> Hi,
>
> A question for the devs. Will this:
>
> http://projects.puppetlabs.com/issues/4020
>
> make it into a release any time soon?
>
> Best regards,
> Martijn.
>
> --
> You received this message because you
Hi,
A question for the devs. Will this:
http://projects.puppetlabs.com/issues/4020
make it into a release any time soon?
Best regards,
Martijn.
--
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
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 s
On Sep 30, 2010, at 3:04 PM, Greg Haase wrote:
> I believe that in the past I was able to view this information on my puppet
> server with
>
> ralsh nagios_host
>
> It would give me a listing of what was stored in nagios_host. Now when I do
> this I see nothing.
I'm not sure if you mean that y
Greg Haase writes:
> I am exporting my resources to the database. I can verify that this is
> occurring. Yet I am not getting all of the the
>
> Nagios_host <<|target ==nagios_hosts.${fqdn}.cfg|>>
>
> files written to my nagios server and I am interested in finding out how to
> trace down this f
Avi,
I am exporting my resources to the database. I can verify that this is
occurring. Yet I am not getting all of the the
Nagios_host <<|target ==nagios_hosts.${fqdn}.cfg|>>
files written to my nagios server and I am interested in finding out how to
trace down this functionality of the collec
Greg Haase wrote:
Are you aware of any documentation that clearly explains how this
collect/export functionality works?
Exporting and collecting resources relies on stored configuration[1]
being enabled on your Puppet Master. You should ensure that the database
is configured and working befor
Stephen,
Ah the David Schmitt nagios module. This is what I based my work on. I used
it as a model.
Are you aware of any documentation that clearly explains how this
collect/export functionality works?
Greg
On 9/30/10 3:31 PM, "Steven Wagner" wrote:
> Hi Greg,
>
> I'm on my phone at the mo
Hi Greg,
I'm on my phone at the moment so I don't have the exact link handy, but there
is a module on GitHub that works. I tinkered with it a lot in my old setup but
found most of my problems were due to not really understanding how the
collect/export functionality worked.
This is my favorite
Greetings,
I am working on getting Nagios implemented with Puppet so that when I add a
node to Puppet a Nagios configuration file is generated.
I can get nagios installed and configured on the server and the client with
no problems. Yet getting the client configuration file on to the server is
On 20/07/10 08:06 AM, Tore wrote:
> Hi,
>
> We currently have a module `nagios` which install nrpe and nagios
> plugins for all nodes. The default node have this module included.
>
> Currently we have a customer who wants to monitor their own services.
> We will still monitor them, but they want
Hi,
We currently have a module `nagios` which install nrpe and nagios
plugins for all nodes. The default node have this module included.
Currently we have a customer who wants to monitor their own services.
We will still monitor them, but they want to do their own checks, fair
enough.
How would
On Tue, Jul 6, 2010 at 11:03 AM, James Turnbull wrote:
> Douglas Garstang wrote:
>> On Tue, Jul 6, 2010 at 12:46 AM, Peter Meier wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
Also, none of the other files created by puppet types are set to be
readable only by root. I
Douglas Garstang wrote:
> On Tue, Jul 6, 2010 at 12:46 AM, Peter Meier wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>> Also, none of the other files created by puppet types are set to be
>>> readable only by root. I think this might be a bug in puppet.
>>> Surprised no one has no
On Tue, Jul 6, 2010 at 12:46 AM, Peter Meier wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>> Also, none of the other files created by puppet types are set to be
>> readable only by root. I think this might be a bug in puppet.
>> Surprised no one has noticed it before.
>
> http://proj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Also, none of the other files created by puppet types are set to be
> readable only by root. I think this might be a bug in puppet.
> Surprised no one has noticed it before.
http://projects.puppetlabs.com/issues/3299
cheers pete
-BEGIN PGP SIGN
On Mon, Jul 5, 2010 at 6:57 PM, Gabriel Filion wrote:
> On 2010-07-05 19:34, Douglas Garstang wrote:
>> First off, does anyone use the puppet built in nagios types?
>>
>> I just started to play with them, and I noticed that nagios_host
>> writes the nagios_host.cfg file as owned by root, and reada
On 2010-07-05 19:34, Douglas Garstang wrote:
> First off, does anyone use the puppet built in nagios types?
>
> I just started to play with them, and I noticed that nagios_host
> writes the nagios_host.cfg file as owned by root, and readable by
> root, and no on else. Is there a reason for that? S
First off, does anyone use the puppet built in nagios types?
I just started to play with them, and I noticed that nagios_host
writes the nagios_host.cfg file as owned by root, and readable by
root, and no on else. Is there a reason for that? Since nagios runs as
the nagios user, it can't read the
I was thinking I'd have to look at the master logs on server, but looks like
each host has the state file. So am I correct in assuming that the state.yaml
will only get updated/touched on successful run? This is why I was thinking of
checking server logs on master to be sure that it completed
Daniel Wittenberg wrote:
> Anyone written a check for nagios to make sure their nodes are
> checking in and updating correctly? I think I'd rather have a
> passive check on the nagios server that just alerts me if something
> hasn't checked in for last 24 hours rather than having antoher
> dashboa
Anyone written a check for nagios to make sure their nodes are checking in and
updating correctly? I think I'd rather have a passive check on the nagios
server that just alerts me if something hasn't checked in for last 24 hours
rather than having antoher dashboard to go look at. Anyone tried
Hello,
I've been working for the past two days on transforming a Nagios module
to make it "hostgroup"-aware, that is, to include hosts in groups to
reuse services intead of always redefining them for every host.
I tested giving a list of strings to the "hostgroups" attribute to the
nagios_host re
I do a very simple check:
# warn if the state files are 90 minutes old, critical at 150
minutes
nagios::service { "puppet_running": check_command =>
"check_puppet_age!7500!9000!2048!2047",
notifications_enabled => 0, }
}
check_puppet_age is: command_line => '/usr/li
Peter Berghold wrote:
> Has anybody out there written a custom check for Nagios to determine
> if puppetd and/or puppetmasterd is running? I am considering writing
> one if not.
FWIW, I've got an overengineered check_puppet and puppetstatus tool
at: http://tmz.fedorapeople.org/scripts/puppetstatus
On 05/27/2010 02:37 PM, Peter Berghold wrote:
Has anybody out there written a custom check for Nagios to determine
if puppetd and/or puppetmasterd is running? I am considering writing
one if not.
--
You received this message because you are subscribed to the Google
Groups "Puppet Users" gro
On Thu, May 27, 2010 at 12:19 PM, Michael DeHaan wrote:
> On Thu, May 27, 2010 at 2:37 PM, Peter Berghold
> wrote:
>> Has anybody out there written a custom check for Nagios to determine if
>> puppetd and/or puppetmasterd is running? I am considering writing one if
>> not.
I did a minimal check
On Thu, May 27, 2010 at 2:37 PM, Peter Berghold wrote:
> Has anybody out there written a custom check for Nagios to determine if
> puppetd and/or puppetmasterd is running? I am considering writing one if
> not.
>
I've found a few things:
http://www.kallisti.net.nz/blog/2009/02/monitoring-puppet-
Has anybody out there written a custom check for Nagios to determine if
puppetd and/or puppetmasterd is running? I am considering writing one if
not.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us.
On 3/2/2010 4:40 PM, Joe McDonagh wrote:
gehel wrote:
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[/con
gehel wrote:
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
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 fai
So I'm revisiting puppet's management of nagios now that 0.25.1 is out
and I want to say thanks for the updates to all the nagios types.
However, there is one huge, gaping hole that's been asked about before
in 2 different threads but that's never been addressed: object
inheritance. For it to wo
Hi there
I was reading the type reference, which seems to be autogenerated. It seems
current (last generated on Mon Mar 30 02:57:00 + 2009)
It mentions some types for supporting nagios.
If I recall correctly, from last time I tried to use this feature, it
wasn't producing nagios configura
Hi all,
Best Practices Question: I've got Nagios configured via puppet, and (of
course) I want to monitor services. Where should I put the @@nagios_service
definitions? (example uses apache2)
a) In the apache2 module (high-coupling)
b) In the nagios module (doesn't make sense)
c) In some nagio
Hi all,
I'm using Puppet 0.24.7 with exported resources to configure Nagios 3
on Debian Lenny. The problem is that when Puppet creates new files
they have permissions -rw--- , which means that Nagios can't read
them.
Does anyone else have this setup?
Thanks,
Graham
--~--~-~-
I have done this:
class nrpe inherits puppet::master {
include nagios2::nrpe
user { "nagios":
groups => 'puppet',
}
file { "/usr/lib/nagios/plugins/check_puppet":
ensure => "present",
95 matches
Mail list logo
