Localhost PING WARNING - System call sent warnings to stderr

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
TBT
Posts: 625
Joined: Wed May 18, 2011 1:26 pm

Localhost PING WARNING - System call sent warnings to stderr

Post by TBT »

In an effort to upgrade from XI 5.9.1, we first need to migrate XI off Debian 10 to Debian 11. After successfully migrating/restoring the application to the new Debian 11 server, the localhost ping check is warning: "PING WARNING - System call sent warnings to stderr"

Command ran from CCM:

Code: Select all

/usr/local/nagios/libexec/check_ping -H 127.0.0.1 -w 100.0,20% -c 500.0,60% -p 5
PING WARNING - System call sent warnings to stderr Packet loss = 0%, RTA = 0.14 ms|rta=0.136000ms;100.000000;500.000000;0.000000 pl=0%;20;60;0
I've exhausted troubleshooting without resolve, and hoping others may have a suggestion on what to check?

Thanks in advance.
Nagios XI 2024R2.2.1 (8 Servers)
Nagios Fusion 2024R1.0.2
TBT
Posts: 625
Joined: Wed May 18, 2011 1:26 pm

Re: Localhost PING WARNING - System call sent warnings to stderr

Post by TBT »

One difference to be noted between the old (Debian 10) vs new (Debian 11) servers are the permissions & ownership after restore.

Old
-rwxrwxr-x 1 www-data nagios 227056 Dec 6 2021 /usr/local/nagios/libexec/check_ping

New
-rwxr-xr-x 1 root nagios 212280 Jun 24 10:21 /usr/local/nagios/libexec/check_ping


That said, the /usr/local/nagios/libexec/ directory has a mix of permissions & ownership on both servers.
Nagios XI 2024R2.2.1 (8 Servers)
Nagios Fusion 2024R1.0.2
kg2857
Posts: 490
Joined: Wed Apr 12, 2023 5:48 pm

Re: Localhost PING WARNING - System call sent warnings to stderr

Post by kg2857 »

There's no point in checking the server (localhost) w/ ping. If there's no networking you will never know it. You need a remote nagios instance to verify this one is working. Don't get me started on local and geographical redundancy :)
That's not a solution to the specific issue. I'd look at check_ping -h to see if there's an option that helps, or look at check_tcp.
Post Reply