【HELP】It can not be monitored

[rkennedy]

There isn't going to be another way to force IPv4 with this plugin, you would need to update.

[P3_25]

Hello.

Sorry in clumsy English.

I had permission of the update.

I install latest NSClient++(Ver. 0.4.4.19) in server C.
Do you not have any problem in this version?

Is there any setting to perform after installation?

[P3_25]

Hello.

Sorry in clumsy English.

Additional information and confirmation matter

There was a server D you are using a NSClient ++ of the same version as the server C.
This server D has been confirmed correctly from Server A and Server B.

Why can you not confirm only server C from server B?

The NSC.ini file of server D and server C was the same setting contents.
Because I obtain it, the permission of the update carries out the update.

I cannot understand why it turns out different to use the same file.
Where should I investigate to find a difference?

[rkennedy]

It is the NRPE plugin that needs to be updated, not NSClient++. You are trying to force IPv4, which didn't work on your previous version.

[Box293]

This guide shows you how to install the plugin on Nagios Core:
http://sites.box293.com/nagios/guides/n ... centos-6-5

[P3_25]

Hello.

Sorry in clumsy English.

A reply becomes slow and is sorry.

The problem was settled.

The IP address that I owned plural IP addresses in a server-side targeted for monitoring, and could not communicate with Nagios server B was set.

It was mysterious that PING went, but the problem was settled.

[dwhitfield]

The problem was settled.

I just want to double-check: are we ready to close the thread?