Upgrade 24.10 to 25.10, ping status UNKNOWN

Can you append 

; echo "exited with $?"

to your command, that way you can see the command exit code.

I believe this script is the check icmp from nagios, so maybe for some reason it returns unknown since an update ?

I have the following code

CRITICAL - XXXXXXXXXXXXX: Host unreachable @ XXXXXXX. rta nan, lost 100%|rta=0.000ms;200.000;400.000;0; pl=100%;20;50;; rtmax=0.000ms;;;; rtmin=0.000ms;;;;
exited with 2
 

Error 2 mean critical.

This plugin was not updated since january 2024, what kind of ping/icmp should I use if this one is too old ?

Base-Ping-LAN-custom use the command base_centreon_ping

This command use is locked and defined as the following :

$USER1$/check_icmp -H $HOSTADDRESS$ -n $_SERVICEPACKETNUMBER$ -w $_SERVICEWARNING$ -c $_SERVICECRITICAL$ -b $_SERVICEPACKET_SIZE$ $_SERVICEEXTRAOPTIONS$

$USER1$ point to /usr/lib64/nagios/plugins

I’m wondering if its not a issue ? Look like the web interface didn’t understand correctly the ouput of the command.

Thanks

On a fresh installation using the VM template (Virtualbox), the ping with the same exact command is working as expected.
So there is something wrong during the migration from 24.10 to 25.10 as the webui seems to not understand (or there is a missing right somewhere) the output of the plugin and then display a UNKNOW status instead of critical.

Same command is used (locked) with the same binary 

$USER1$/check_icmp -H $HOSTADDRESS$ -n $_SERVICEPACKETNUMBER$ -w $_SERVICEWARNING$ -c $_SERVICECRITICAL$ -b $_SERVICEPACKET_SIZE$ $_SERVICEEXTRAOPTIONS$

Thanks, that’s did the trick !

I compare the configuration from a fresh install versus my env.

So, there is a behavior change in Centreon.