example42 / psick

Puppet Systems Infrastructure Construction Kit: The control-repo

Home Page:http://www.example42.com

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

munin service name incompatible with nagios check_procs

jskarpe opened this issue · comments

In Ubuntu 12.04 munin is executed as (as seen by check_proc plugin):

Ss       0 27456     1  51836  9720  0.0    18:27:15 /usr/sbin/munin /usr/sbin/munin-node

Where the servicename is munin-node, such that the check_procs nrpe check will fail in nagios.

Same goes for puppet agent, which shows up as:

Ss       0 31635     1 176148 81420  0.6       11:02 puppet          /usr/bin/ruby1.8 /usr/bin/puppet agentproc#=0 uid=0 vsz=176148 rss=81420 pid=31635 ppid=1 pcpu=0.60 stat=Ss etime=11:02 prog=puppet args=/usr/bin/ruby1.8 /usr/bin/puppet agent

(puppet, not ruby)

The munin part is fixed on the new module (just published):
https://github.com/example42/puppet-munin

About the puppet module, as you using the new one?:
https://github.com/example42/puppet-puppet

Yes, I'm using the new puppet module

Gotta verify this, since there's quite a mess with Puppet's porcess name on different distros/versions and even on the same distro version if you use packages from different sources (ie, epel/puppetlabs).

The quick fix is to provide the process name and eventually its argument by yourself something like:
class { 'puppet':
[..]
process => 'puppet',
process_args => 'agent',
}

note that as far as I see here:
https://github.com/example42/puppet-puppet/blob/master/manifests/params.pp
for Ubuntu 12.04 puppet process should already be set to 'puppet'

Sorry. I should have been clearer: Seems this is an issue when running master only. (My debug output is slightly off, as it's showing agent, not server)