check_snmp_process_wizard.pl lag?

[jbennett]

Code: Select all

# ./check_multi_procs.pl -b /usr/local/nagios/libexec/check_procs -u root -f lane:ves_ocr
Multiple process check failed on :
PROCS CRITICAL: 2 processes with UID = 0 (root), args 'lane'
PROCS CRITICAL: 2 processes with UID = 0 (root), args 'ves_ocr'

I'm going to look into NRDS. Thanks for the link.

EDIT: I'm seeing the following:

These settings affect Nagios XI's ability to accept and process passive host and service check results from external applications, services, and remote Nagios servers. Enabling inbound checks is important in distributed monitoring environments, and in environments where external applications and services send data to Nagios.

This has nothing to do with SNMP Traps, does it?

[abrist]

Yep, NRDS is an alternative to snmp traps for passive checks.

[jbennett]

Code: Select all

# ./check_multi_procs.pl -b /usr/local/nagios/libexec/check_procs -u root -f lane:ves_ocr
Multiple process check failed on :
PROCS CRITICAL: 2 processes with UID = 0 (root), args 'lane'
PROCS CRITICAL: 2 processes with UID = 0 (root), args 'ves_ocr'

It seems that I am still getting this process as critical?

[slansing]

What do you get as a return when you check only one valid process, a standard process that would reside on the system other than the two you just tested?

[jbennett]

What do you get as a return when you check only one valid process, a standard process that would reside on the system other than the two you just tested?

Here are some examples. I tried a false process in ves_tfer and it returned OK when there was no process by that name.

Code: Select all

 # ./check_multi_procs.pl -b /usr/local/nagios/libexec/check_procs -u root -f lane
Multiple process check failed on :
PROCS CRITICAL: 2 processes with UID = 0 (root), args 'lane'
 # ps ax | grep lane
 2210 ?        SLs    0:00 lane -c /home/rite/config -p 2 -m -d 0x00ff -L 200000

Code: Select all

 # ./check_multi_procs.pl -b /usr/local/nagios/libexec/check_procs -u root -f ves_tfer
Multiple process check OK
 # ps ax | grep ves_tfer
 #

Code: Select all

 # ./check_multi_procs.pl -b /usr/local/nagios/libexec/check_procs -u root -f ves_cap_trx
Multiple process check failed on :
PROCS CRITICAL: 2 processes with UID = 0 (root), args 'ves_cap_trx'
 # ps ax | grep ves_cap_trx
 2139 ?        SL     0:00 ves_cap_trx -c /home/rite/config/ves_cap_config.ini -m -d 0xFF -L 8000000 -p 2

[scottwilkerson]

I looked through the code a bit and you are not specifying a -c which defaults to 1 for min and max for quantity of processes, which would make the plugin return OK if it was outside of 1:1 but not

What do you get when you run

Code: Select all

./check_multi_procs.pl -b /usr/local/nagios/libexec/check_procs -u root -f ves_cap_trx -s 0 -x 2

[jbennett]

I still don't think it's working correctly. I have stopped the 'lane' process and verified that it is no longer running, yet the plug-in still shows that it is ok:

Code: Select all

# stoplane
# ps ax | grep lane
# ./check_multi_procs.pl -b /usr/local/nagios/libexec/check_procs -u root -f lane -s 0 -x 2
Multiple process check OK
# startlane
# ps ax | grep lane
 5277 ?        SLs    0:00 lane -c /home/rite/config -p 2 -m -d 0x00ff -L 2000000

[lmiltchev]

I am getting similar results on my test box. We will need to do some more digging into this.

[jbennett]

Just wanted to check in on this and see if anything was ever found. I'm trying to run this now via NRDS on our new kernel that's being pushed out.

[lmiltchev]

Nothing conclusive. I noticed, though, there is a note in the README file:

Note : This module is deprecated if you use last version of check_procs

What is the version of the check_procs that you are using?

Code: Select all

/usr/local/nagios/libexec/check_procs -V