Passive Monitoring

[vignesha]

Hello Team,
In our environment, we have newly configured passive monitoring for windows servers and we are facing issue for CPU Usage is giving (No output returned from plugin) error also I have checked in the windows server CPU usage script is present and am able to execute the script from powershell.

Please help us to resolve the issue.

[npolovenko]

Hello, @vignesha. What agent are you using for monitoring? The NCPA or the NSClient? Please upload the relevant config from the windows server and the log file. For NSClient that would be the nsclient.ini and nsclient.log and for ncpa that would be ncpa.cfg, ncpa_passive.log, and win32service_ncpapassive.log.

[vignesha]

Hi,

I am monitoring using NRDS and i have PM the further details.

Let me know any further details required.

[tgriep]

I see the plugin getting ran in the log files for NRDS but the plugin is not returning anything. Can you login to the Windows system, open a command prompt and run the following command?

Code: Select all

powershell -ExecutionPolicy Bypass -File C:\PROGRA~1\Nagios\NRDS_Win\plugins\check_cpu.ps1 -w 70 -c 80

Please show the full output.
Thanks

[vignesha]

Hi,

I am able to run the command as administrator but not as user.

User Output:
PS C:\Users\V5FA6YI> powershell -ExecutionPolicy Bypass -File C:\PROGRA~1\Nagios\NRDS_Win\plugins\check_cpu.ps1 -w 70 -c
80
The term 'powershell' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:11
+ powershell <<<< -ExecutionPolicy Bypass -File C:\PROGRA~1\Nagios\NRDS_Win\plugins\check_cpu.ps1 -w 70 -c 80
+ CategoryInfo : ObjectNotFound: (powershell:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\V5FA6YI>

[tgriep]

The NRDS agent is set to run as a system account and that account does not have sufficient permissions to run the plugin so you will have to set the ExecutionPolicy to unrestricted and possibly set the Remote signed as well for the system.
Typically, you would just open a powershell window as an administrator and run the following.

Code: Select all

Set-ExecutionPolicy unrestricted
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned

Try that out and see if this helps.