Check_ping ok when host is down

[plessier]

Hello,
I ping 15 ip address from a Windows 7 host with the command check_ping.
When I ping these addresses with a ping with a ping command, everything works correctly (the down IP are down and the up ip are up).
When I use check_nrpe -H utt12039-c check_ping -a hosts = ipadress to check ip one by one, everything works.
With the same command my centreon say everything is UP

When I run command in sequential ; 4 ip are down ( the result is GOOD)
After investigation.

I tried reproduce the launch enviroment in centreon, launch all command in //,

I run the 15 check_ping in parallel
/usr/lib/nagios/plugins/check_nrpe -H utt12039 -c check_ping -a hosts=10.53.44.46 >> output_back.txt &
Result : randow ip are down, everything is up

The problem seem to come from that the system ask to check_ping at the same time and not in sequential.

Sorry for my english.
/usr/lib/nagios/plugins/check_nrpe -H utt12039
I (0.5.0.65 2016-11-13) seem to be doing fine...
utt12039 is a Windows 7.
Check_nrpe 2.14 run from a linux

[plessier]

Hello,

The software seems to recover the last buffer of the last ping

[mickem]

I always was a bit skeptical to the thread-safety of check_ping... I will investigate...

[plessier]

Hello, If you have tests that I can do to help you, it will be with pleasure Cordialement David PLESSIER System Administrator, Dailycer SAS - D. PLESSIER@DAILYCER-FR.COM Phone : +33 (0) 322 787 644 / FAX: +33 (0) 322 783 290 WARNING: information & attached files of this mail are only intended for the above mentioned addressees. Review, dissemination or disclosure is strictly prohibited. If you receive this email by error, please destroy it immediately. Thank you.

[peacand]

Hello,

I noticed the same issue for me today. I have a Centreon monitoring 6 IP using check_ping remotely via NRPE. In case one of them is UP and all the others are DOWN, they look all UP in my Centreon.

I also confirm it is related to threading. I've just tried to add the option "thread pool=1" in my server configuration to force a single thread. With that configuration the monitoring is all good. But of course, this is just a way to validate the root cause of the issue and not a viable solution.

Did you get a chance to work on the threading issue with check_ping ?