Page 2 of 2
Re: [Help] check_process_memory.sh configuration
Posted: Tue Oct 28, 2014 11:10 am
by sreinhardt
Did you have a user logged into Windows at that time? It looks like the query went correctly, but you may not have had explorer running as it was not consuming any memory. We should be able to check the nscp.exe binary like you initially posted with:
Code: Select all
./check_nt -H 192.168.160.129 -p 12489 -v COUNTER -l "\\Process(nscp.exe)\\Working Set"
Re: [Help] check_process_memory.sh configuration
Posted: Tue Oct 28, 2014 12:25 pm
by sh.shekhar89
sreinhardt wrote:Did you have a user logged into Windows at that time? It looks like the query went correctly, but you may not have had explorer running as it was not consuming any memory. We should be able to check the nscp.exe binary like you initially posted with:
Code: Select all
./check_nt -H 192.168.160.129 -p 12489 -v COUNTER -l "\\Process(nscp.exe)\\Working Set"
Hi sreinhardt,
i got the same output :
" [root@nagios libexec]# ./check_nt -H 192.168.160.129 -p 12489 -v COUNTER -l "\\Process(nscp.exe)\\Working Set"
0
[root@nagios libexec]# "
And users have logged into windows.
Re: [Help] check_process_memory.sh configuration
Posted: Tue Oct 28, 2014 2:44 pm
by lmiltchev
Open the Performance Monitor, right-click on the perf counter and see what is the "
exact" name under the "Data" tab. Most probably, you will need to run:
Code: Select all
./check_nt -H 192.168.160.129 -p 12489 -v COUNTER -l "\\Process(explorer)\\Working Set"
instead of
Code: Select all
./check_nt -H 192.168.160.129 -p 12489 -v COUNTER -l "\\Process(explorer.exe)\\Working Set"
Example:
Code: Select all
[root@testbox libexec]# ./check_nt -H 192.168.x.x -s password -p 12489 -v COUNTER -l "\\Process(explorer)\\Working Set"
99512300
[root@testbox libexec]# ./check_nt -H 192.168.x.x -s password -p 12489 -v COUNTER -l "\\Process(firefox)\\Working Set"
754577000
Re: [Help] check_process_memory.sh configuration
Posted: Wed Aug 16, 2017 3:21 am
by Pitone_Maledetto
Hi all,
I know this thread is very old but my comment could help someone now.
The error is encountered because in the plugin script the default check_nt port is set to 1248 instead of 12489.
That means that if you don't specify the port number with -p then it defaults to the wrong one and you get a "Connection refused" therefore the rest of the script will fail.
Moreover bc does not support -r switch anymore so take it out.
Regards
Re: [Help] check_process_memory.sh configuration
Posted: Wed Aug 16, 2017 11:05 am
by lmiltchev
Thanks for the feedback, Pitone_Maledetto!
@sh.shekhar89 it's been almost 3 years since your last post, so I am going to lock this topic. If you have any more issues, please start a new thread. If you want to reopen the existing thread, PM me or anyone on the Nagios support forum. We will unlock it for you. Thank you!