Check Windows Processes

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: Check Windows Processes

Post by slansing »

Whatever argument you are passing the check, I'm not sure what you had previously set up, or what would be required as I cannot find this plugin anywhere. You could try with numbers, or text and see what it gives you, simple troubleshooting style :)
ofadl
Posts: 201
Joined: Mon Jun 03, 2013 8:57 am

Re: Check Windows Processes

Post by ofadl »

ok, so everytime i insert a number into <enter arguments here> i just get the number i input as output.


-bash: syntax error near unexpected token `1'



Every time i enter a word, i get

"-bash: syntax error near unexpected token `newline'"

path i used was:

/usr/lib/nagios/plugins/check_nrpe -H <10.200.50.176> -p 5666 -c check_procs_from_file -a <test>
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: Check Windows Processes

Post by slansing »

You are not wrapping the IP and argument in "<>" are you? That was to denote you needed to place your own info there.

What happens when you run:

Code: Select all

/usr/lib/nagios/plugins/check_nrpe
And:

Code: Select all

/usr/lib/nagios/plugins/check_nrpe -H <windowserverip>
ofadl
Posts: 201
Joined: Mon Jun 03, 2013 8:57 am

Re: Check Windows Processes

Post by ofadl »

i am getting this for /usr/lib/nagios/check_nrpe

Incorrect command line arguments supplied

NRPE Plugin for Nagios
Copyright (c) 1999-2008 Ethan Galstad (nagios@nagios.org)
Version: 2.12
Last Modified: 03-10-2008
License: GPL v2 with exemptions (-l for more info)
SSL/TLS Available: Anonymous DH Mode, OpenSSL 0.9.6 or higher required

Usage: check_nrpe -H <host> [-n] [-u] [-p <port>] [-t <timeout>] [-c <command>] [-a <arglist...>]

Options:
-n = Do no use SSL
-u = Make socket timeouts return an UNKNOWN state instead of CRITICAL
<host> = The address of the host running the NRPE daemon
[port] = The port on which the daemon is running (default=5666)
[timeout] = Number of seconds before connection times out (default=10)
[command] = The name of the command that the remote daemon should run
[arglist] = Optional arguments that should be passed to the command. Multiple
arguments should be separated by a space. If provided, this must be
the last option supplied on the command line.
-h,--help Print this short help.
-l,--license Print licensing information.
-n,--no-ssl Do not initial an ssl handshake with the server, talk in plaintext.

Note:
This plugin requires that you have the NRPE daemon running on the remote host.
You must also have configured the daemon to associate a specific plugin command
with the [command] option you are specifying here. Upon receipt of the
[command] argument, the NRPE daemon will run the appropriate plugin command and
send the plugin output and return code back to *this* plugin. This allows you
to execute plugins on remote hosts and 'fake' the results to make Nagios think
the plugin is being run locally.


and am getting a "check_nrpe: socket timeout after 10 seconds" when running

/usr/lib/nagios/plugins/check_nrpe -H 10.200.50.76
sreinhardt
-fno-stack-protector
Posts: 4366
Joined: Mon Nov 19, 2012 12:10 pm

Re: Check Windows Processes

Post by sreinhardt »

Lets verify the nrpe port is open and receptive to your nagios host.

nmap -p 5666 10.200.50.76

you can also try nrpe without ssl and see if that helps although my guess is it will not

./check_nrpe -H 10.200.50.76 -n
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
ofadl
Posts: 201
Joined: Mon Jun 03, 2013 8:57 am

Re: Check Windows Processes

Post by ofadl »

so i ran first command after installed the program nmap, and heres the output:

Starting Nmap 5.21 ( http://nmap.org ) at 2013-06-28 15:51 EDT
Note: Host seems down. If it is really up, but blocking our ping probes, try -PN
Nmap done: 1 IP address (0 hosts up) scanned in 3.06 seconds

second command, gives me an socket timeout after 10 seconds
sreinhardt
-fno-stack-protector
Posts: 4366
Joined: Mon Nov 19, 2012 12:10 pm

Re: Check Windows Processes

Post by sreinhardt »

Either your host is not up, or you do not have routes to it. This is a networking issue.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
ofadl
Posts: 201
Joined: Mon Jun 03, 2013 8:57 am

Re: Check Windows Processes

Post by ofadl »

i think it has to do with the routes to it, the host is working fine and there are several service checks working under it... would u know on how to go about solving this?
abrist
Red Shirt
Posts: 8334
Joined: Thu Nov 15, 2012 1:20 pm

Re: Check Windows Processes

Post by abrist »

Some troubleshooting:

Code: Select all

ping 10.200.50.76
route -n
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
ofadl
Posts: 201
Joined: Mon Jun 03, 2013 8:57 am

Re: Check Windows Processes

Post by ofadl »

i ran the ping 10.200.50.76 and didint get a reply then did route -n and got this:

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.200.40.1 0.0.0.0 UG 100 0 0 eth0
10.200.40.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
Locked