Archive | Icinga RSS feed for this section

Re-generate Nagios_service target-files

Some time ago I ran into the the problem that when having a Puppet configuration like this Nagios_service <<| |>> { target => "${baseconfigdir}/${conf_file_srvs}", } which is about collecting all stored configurations of type nagios_service, this works pretty well when executed for the first time. However, every subsequent Puppet run will not regenerate the target […]

Read full story Comments { 0 }

Monitoring Puppet – Part 3

Ever been concerned about the health of your Puppet agents? You know they are executing, but you don’t know if execution is successful? I’d like to show how to achieve this by monitoring the syslog of the Puppet machines. In case any errors occur during Puppet’s execution, the appropriate error messages will be logged to […]

Read full story Comments { 0 }

Monitoring Puppet – Part 2

As mentioned in one of my previous posts here, there are some more possibilities of observing the health of a Puppet agent. This one shows how I observe the state of an agent using its file /var/lib/puppet/state/state.yaml. Every time the Puppet agent executes, this file is being regenerated. By simply checking the age of the […]

Read full story Comments { 0 }

Make NRPE talk to rsyslog

Ever wondered why switching the NRPE daemon to debug mode has no effect in any log files at all? I did, a lot of times. You may have a configuration something like this in your nrpe.cfg file: log_facility=daemon pid_file=/var/run/nrpe.pid server_port=5666 nrpe_user=nrpe nrpe_group=nrpe allowed_hosts=some.ip.address.here debug=1 Line 1 indicates it should log everything to the syslog daemon. […]

Read full story Comments { 0 }

NRPE and SELinux

Ever had an Unable to read output error when executing an Icinga/Nagios remote check using NRPE? I’m pretty sure you had since everyone working with NRPE will run into this error sooner or later. Most solutions are trivial (e.g. wrong file permissions) and I don’t want to repeat the few thousand posts already covering this […]

Read full story Comments { 0 }