Kevin Keane wrote:
I've seen this happen when ping returned an error. In my case, it was
actually ping6 because it had a bad IPv6 address configured.
Since it's intermittent in your case, most likely the root cause is
something else, but ping is still returning an error. If I had to
occasionally, I'll get a response that flags nagios to go critical:
/sbin/ping -n -c 5 10.1.1.1
CRITICAL - Could not interpret output from ping command
This happens maybe once or twice a day. Is it getting confused with
something else?
It doesn't seem to happen on any consistant basis,
I've seen this happen when ping returned an error. In my case, it was
actually ping6 because it had a bad IPv6 address configured.
Since it's intermittent in your case, most likely the root cause is
something else, but ping is still returning an error. If I had to
venture a guess, maybe it's