1.6 broken icmp.ping?

[manowar]

firstly, congrats to everyone on 1.6. Nice.

To the point though, it seems that all my icmp.ping items are now always returning failure even though the hosts are answering to fping fine. Anything amiss?

[manowar]

Yeah, there is definitely something screwy with this. Even setting up new hosts with icmp.ping wont get any data entered into the DB, I even get this on a fresh install as opposed to an upgrade.

Checking the debug logs, fping is returning all the right data (ie host alove, ping time x.xx ms. etc) but its not making it into the database. No obvious error.

This only seems to apply to icmpping and icmppingtime, everything else looks fine.

Can anyone else verify this?

ADMIN: I put this inteh wrong thread, could someone move it to troubleshooting?

[cjwallace]

I think i am seeing the same thing.

I have done a ICMP discovery but nothing is returned

[teferi]

I think i am seeing the same thing.

I have done a ICMP discovery but nothing is returned

I don't have this. icmpping works pretty correctly.

[radamand]

same issue, all icmp ping simple checks fail.

[manowar]

I saw this in the 1.6 manual:

ZABBIX uses external utility fping for processing of ICMP pings. The utility is not
part of ZABBIX distribution and has to be additionally installed. If the utility is
missing, has wrong permissions or its location does not match FpingLocation
defined in configuration file, ICPM pings (icmpping and icmppingsec) will not be
processed.

and noticed my fping permissions were slightly out (6755) so corrected them and restart zabbix_server hoping that would be the issue but same problem. Zabbix just doesnt seem to want to know about the results of these checks..

[radamand]

nope, my bad.

I fixed permissions on /usr/bin/fping
the config file was pointing at /usr/sbin/fping

[undead]

fping and source ip

I just got this issue too, but with zabbix_proxy.
Decision is:
1) comment #SourceIP=10.99.3.3
2) or find a 'fping' which understands the '-S' option
(mine don't understands it - so no discovery, and no icmpping )


----
If we look into icmpping.c we should see such code:
if (NULL != CONFIG_SOURCE_IP)
zbx_snprintf(source_ip, sizeof(source_ip), "-S%s ", CONFIG_SOURCE_IP);
else
*source_ip = '\0';
So, actually zabbix calls fping lile that:
/usr/sbin/fping -S10.99.3.3 -c3 2>/dev/null </tmp/zabbix_server_27359.pinger

I download fping from here http://fping.sourceforge.net/download/fping.tar.gz
and build It.
And it have no -S option.

Is it a bug?

[CeeEss]

I've got the same issues with 1.6. Which build of fping supports -S? Just downloaded 2.4b2 (because i thought the RPM version might have been compiled with certain flags not set) but this doesn't have -S either.

I just got this issue too, but with zabbix_proxy.
Decision is:
1) comment #SourceIP=10.99.3.3
2) or find a 'fping' which understands the '-S' option
(mine don't understands it - so no discovery, and no icmpping )


----
If we look into icmpping.c we should see such code:
if (NULL != CONFIG_SOURCE_IP)
zbx_snprintf(source_ip, sizeof(source_ip), "-S%s ", CONFIG_SOURCE_IP);
else
*source_ip = '\0';
So, actually zabbix calls fping lile that:
/usr/sbin/fping -S10.99.3.3 -c3 2>/dev/null </tmp/zabbix_server_27359.pinger

I download fping from here http://fping.sourceforge.net/download/fping.tar.gz
and build It.
And it have no -S option.

Is it a bug?

[CeeEss]

Also strange: fping2.2 for DOS defines -S as:

-S : size sweep. Ping with size1, size1 + 1, ..., size 2 datalength

[undead]

I have found two patches of fping.

http://wiki.version6.net/Patches

Maybe they help.


This thread is about it:
http://osdir.com/ml/network.smokepin.../msg00001.html

[CeeEss]

Argh. simple fix. fping had the wrong permissions.