Process Count not working after NSclient upgrade

[ranjitw]

Hi ,

After upgrading to NSCP-0.4.3-x64.msi Process Count is not working . Even if the criteria is met the alarm is getting generated .

Below is the output:

[root@hostn libexec]# ./check_nrpe -H newnsclient -t 30 -c CheckProcState -a MinCritCount=2 notepad.exe
CRITICAL: notepad.exe : 0, notepad.exe : 1|'count'=4;0;2


When running the same on old NSclient NSClient++-Stable-64 it working fine.

[root@hostn libexec]# ./check_nrpe -H oldnsclient -t 30 -c CheckProcState -a MinCritCount=2 notepad.exe
CRITICAL: notepad.exe: 2 < critical|'notepad.exe'=2;0;2

Please help in getting this problem resolved.

I am attaching the nsclient ini files.

[tgriep]

It looks like there is a bug in the NSClient++ agent. I installed the latest nightly build and it worked correctly.
You can go to this link to download the nightly build.
http://www.nsclient.org/download/0.4.4/
Make sure you backup your nsclient.ini file and the install will overwrite it.

[ranjitw]

Hi tgriep,

Due to security restriction I am unable to download the agent. Can you please upload the binary to this post ?

It would be very helpful if you zip and upload.

Many thanks,

[scottwilkerson]

I have placed the file temporarily on one of our servers for download
https://assets.nagios.com/temp/nscp-0.4.4.2-x64.zip

[ranjitw]

Thank you , I will test and come back with the results.

[ranjitw]

Hi,

I should just do unzip of the file?

[tgriep]

Yes, you just need to unzip it to this folder.

Code: Select all

C:\Program Files\NSClient++

Make sure any other checks continue to run. As this is a nightly build, it may break other checks.

[ranjitw]

Hi,

I have not checked the process count . I am getting new errors now for all the checks :

NSClient - ERROR: Invalid return from command: check_drivesize

Please suggest how to resolve this issue.

[ranjitw]

Hi ,

Can you please let me know a less bug version (stable version ) which has Process count functionality working ?

[rkennedy]

Are you able to reinstall the previous version you were using before upgrading? That is the stable one that I would recommend.

At this time it seems the bug has been fixed as @tgriep mentioned, but you will have to wait for an official version to be released.