【HELP】It can not be monitored

[rkennedy]

Can you ping the machine? ping 192.168.4.254

[P3_25]

Hello.

Sorry in clumsy English.

Yes.
It is PING results from B to C.

PING 192.168.4.254 (192.168.4.254) 56(84) bytes of data.
64 bytes from 192.168.4.254: icmp_seq=1 ttl=128 time=0.615 ms
64 bytes from 192.168.4.254: icmp_seq=2 ttl=128 time=0.330 ms
64 bytes from 192.168.4.254: icmp_seq=3 ttl=128 time=0.325 ms
64 bytes from 192.168.4.254: icmp_seq=4 ttl=128 time=0.327 ms
64 bytes from 192.168.4.254: icmp_seq=5 ttl=128 time=0.336 ms

Could you check it?

[tmcdonald]

Open the remote host (C) command line and execute:

/usr/local/nagios/libexec/check_nrpe -H localhost

C:\"Program Files"\NSClient++\check_nrpe.exe --host 127.0.0.1

and post the results. If this is a 32-bit OS then the path will be C:\"Program Files (x86)"\NSClient++\check_nrpe.exe --host 127.0.0.1

[nozlaf]

Log into the remote host (C) as root and execute:

/usr/local/nagios/libexec/check_nrpe -H localhost

and post the results.

i'm pretty sure host C is windows

NSClient service of C also restarted, but a phenomenon doesn't change.
nsc.ini in C is attached.

[tmcdonald]

i'm pretty sure host C is windows

You are correct sir! I saw the NRPE and my brain immediately looked for Linux. I've updated my post to reflect this.

[P3_25]

Hello.

Sorry in clumsy English.

I log in to remote host C
I move to C:\"Program Files"\NSClient++
I want to carry out "check_nrpe.exe", but there is no "check_nrpe.exe". What can I do?

I attach screenshot in C:\"Program Files"\NSClient++\.
If there is a thing substituting for "check_nrpe.exe", please tell me.

By the way, I send the result of server A and server B.

server A
[root@serverA ~]# /usr/local/nagios/libexec/check_nrpe -H 127.0.0.1
NRPE v2.12

server B
[root@server B ~]# /usr/local/nagios/libexec/check_nrpe -H 127.0.0.1
Connection refused by host


Could you check it?

[P3_25]

Hello.

Sorry in clumsy English.

I'm sorry. I forgot to attach it.

I attach it.

[tgriep]

Login to server B, run the following command increasing the timeout value to see if that helps.

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H 192.168.4.254 -t 60

If this fails, check the C:\"Program Files (x86)"\NSClient++\nsclient.log file for any errors.
Another thing to check, check the firewall on that system and see if it is blocking the Nagios server B.

[P3_25]

Hello.

Sorry in clumsy English.

It is a practice result of /usr/local/nagios/libexec/check_nrpe -H 192.168.4.254 -t 60

[root@server B ~]# /usr/local/nagios/libexec/check_nrpe -H 192.168.4.254 -t 60
CHECK_NRPE: Socket timeout after 60 seconds.
[root@server B ~]#

I attach nsclient.log.

The firewall of server C was invalid.

Could you check it?

[tgriep]

Thanks for the log file.
One thing is that you are running a very old version of NSClient and you should upgrade it.
You can download a newer version from this site.
https://www.nsclient.org
The newer version on the NSClient, they changed the format of the options and the name of the nsc.ini file is now called nsclient.ini.
Before upgrading, make a copy of the nsc.ini file.

When you said that the firewall was invalid on server C, what do you mean by that and did you fix it?