Project

General

Profile

Actions

Bug #3145

closed

NRPEv2 problem with created configuration and check_nrpe2 (for example)

Added by Georg Bottenhofer almost 12 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
NRPE
Target version:
-
Start date:
08/14/2013
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Affected Version:
2.0.x
Affected Plus Version:
Affected Architecture:

Description

Currently I am experiencing a problem with the configuration of NRPEv2-Plugins.

Everytime the configuration is newly created some commands cannot be started because of wrong parameters which are currently added by default.

For example I am using check_nrpe2. If I configure it using the webinterface without value for warning and critical the following line will be createt in /usr/local/etc/nrpe.cfg:

command[check_diskspace]=/usr/local/libexec/nagios/check_nrpe2 -w -c -H 123.123.123.123 -c check_diskspace 

Of course I could write my command into the critical-field, but that does not make any sense.

The command should be like this:

command[check_diskspace]=/usr/local/libexec/nagios/check_nrpe2 -H 123.123.123.123 -c check_diskspace

Maybe the problem is located in /usr/local/pkg/nrpe2.ing in line 163:

$cmds[] = "command[{$cmd['name']}]={$nagios_check_path}/{$cmd['command']} -w {$cmd['warning']} -c {$cmd['critical']} {$cmd['extra']}\n";

There is no check if the fields for the values warning and critical are not empty.

This problem may affect other plugins too.

Actions #1

Updated by Jim Pingle almost 12 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:bb9868cafa6bc1be95bf2a1ae80b0bccc1dfc7fa.

Actions #2

Updated by Chris Buechler over 10 years ago

  • Category set to NRPE
  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF