Simple check ping returns no data through proxy
I have a zabbix server (2.0.2) set up and a zabbix proxy (2.0.5) at another site that feeds data back. I have some networking equipment that I am only using a simple check with icmpping[,1] and icmppingsec[,1] as my items. These are applied by a template, the same no matter what site they are at. Anything on the proxy side is returning 0's for both ping and pingsec, but the zabbix server is getting proper values.
On the proxy I have followed the instructions on how to chown/chmod the fping bin so it can be run by zabbix. In the item list for the devices being monitored via proxy it doesn't show an error for the ping[] item (it did before the chmod), and if I turn the proxy log to 4 I see that it is properly running the ping commands:
# cat /var/log/zabbix/zabbix_proxy.log | grep fping
10876:20130410:151313.961 /usr/sbin/fping -q -C2 2>&1 </tmp/zabbix_proxy_10876.pinger
10876:20130410:151323.967 /usr/sbin/fping -q -C2 2>&1 </tmp/zabbix_proxy_10876.pinger
10876:20130410:151330.973 /usr/sbin/fping -q -C2 2>&1 </tmp/zabbix_proxy_10876.pinger
Any thoughts on what else to check? All other data is coming back from the proxy OK.
**EDIT**
Looks like the proxy is running SELinux, and it is having the same issue. Solution that worked for me posted here:
On the proxy I have followed the instructions on how to chown/chmod the fping bin so it can be run by zabbix. In the item list for the devices being monitored via proxy it doesn't show an error for the ping[] item (it did before the chmod), and if I turn the proxy log to 4 I see that it is properly running the ping commands:
# cat /var/log/zabbix/zabbix_proxy.log | grep fping
10876:20130410:151313.961 /usr/sbin/fping -q -C2 2>&1 </tmp/zabbix_proxy_10876.pinger
10876:20130410:151323.967 /usr/sbin/fping -q -C2 2>&1 </tmp/zabbix_proxy_10876.pinger
10876:20130410:151330.973 /usr/sbin/fping -q -C2 2>&1 </tmp/zabbix_proxy_10876.pinger
Any thoughts on what else to check? All other data is coming back from the proxy OK.
**EDIT**
Looks like the proxy is running SELinux, and it is having the same issue. Solution that worked for me posted here:
