Also if server has several vlan interfaces in different (private) networks SNMP checks fail if SourceIP is set and there is no route from sourceip to that address.
Looking at tcpdump the query from zabbix looks exactly the same as query from snmpget but zabbix never receives the data.
discussed at :
http://www.zabbix.com/forum/showthread.php?t=12018
http://www.zabbix.com/forum/showthread.php?t=11487
It exists also in Debian bug tracking system: [email protected]
Related issue: ZBX-3379.
this should be fixed in ZBX-3379
this issue mentioned both snmp and web monitoring, ZBX-3379 only fixed snmp. reopening.
CURLOPT_INTERFACE might be the solution (from http://curl.haxx.se/libcurl/c/curl_easy_setopt.html )
ZBX-8804 discusses the same problem with database connections
Fixed in svn://svn.zabbix.com/branches/dev/ZBX-591
Successfully tested
Available in 2.4.4rc1 r52152 and 2.5.0 (trunk) r52153.
(1) Documented in:
https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_244
https://www.zabbix.com/documentation/2.4/manual/introduction/whatsnew244
asaveljevs ChangeLog entry for this issue was improved since r52512 by capitalizing terms and adding proper spacing:
added interface (SourceIP) for outgoing connection in web monitoring, alerts(Ez Texting), vmware monitoring and simple checks(https services)
added interface (SourceIP) for outgoing connection in web monitoring, alerts (Ez Texting), VMware monitoring and simple checks (HTTPS services)
Similarly, documentation should have the same capitalization and spacing.
asaveljevs Did that. Please take a look. RESOLVED.
<richlv> the sentence seems to be very confusing to me. maybe it would be more clear if we would say that "web monitoring .... will now obey the SourceIP setting in the Zabbix server or proxy configuration file" or similar ? also, upgrade notes should explicitly say that in some cases the outgoing checks can be done from a different IP after the upgrade
asaveljevs Paraphrased the change using richlv's suggestion at https://www.zabbix.com/documentation/2.4/manual/installation/upgrade_notes_244 and https://www.zabbix.com/documentation/2.4/manual/introduction/whatsnew244 . RESOLVED.
martins-v Reviewed, with small formatting fixes. The current version seems satisfactory. CLOSED.
(2) The ChangeLog entry should also have the "G" component, because "net.tcp.service[https]" is available not only as a simple check, but also as an agent check. This should also be made clear in ChangeLog and in the documentation.
igorsh How about something like this:
...G...PS. [ZBX-591] added interface (SourceIP) for outgoing connection in web monitoring, alerts (Ez Texting), VMware monitoring, simple and agent checks (HTTPS services)
asaveljevs How about the following ChangeLog entry instead?
...G...PS. [ZBX-591] fixed net.tcp.service{.perf}[https], VMware and Web monitoring, and Ez Texting alerts to use SourceIP parameter (igors)
martins-v Perhaps:
...G...PS. [ZBX-591] fixed web monitoring, VMware monitoring, Ez Texting alerts and net.tcp.service{.perf}[https] items to use the SourceIP configuration parameter
asaveljevs Looks good. Fixed in pre-2.4.8rc1 and pre-3.0.0alpha6 directly in r57389. CLOSED.
I strongly second richlv! I have no idea what the documentation is saying there. I also find the term "outgoing" redundant. Never has a web server connected itself to a client and it says "source" already.
can this one be cleaned up still in 2015 ? 
Solved (1) and (2) on December 29.