[ZBX-591] SourceIP not used for web monitoring Created: 2008 Nov 06 Updated: 2017 May 30 Resolved: 2016 Jan 11 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | 1.6, 2.2.0 |
Fix Version/s: | 2.4.4rc1, 2.5.0 |
Type: | Incident report | Priority: | Blocker |
Reporter: | Hannu Ylitalo | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 5 |
Labels: | sourceip, webmonitoring | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
64 bit CentOS 5.2 |
Issue Links: |
|
Description |
Seems that when using virtual network interface (eth0:1) for polling and specifying SourceIP in zabbix_server.conf zabbix uses eth0's IP for polling SNMP and Web services rather than the specified SourceIP. SourceIP works fine on agent checks. Applies to at least zabbix 1.6.1, haven't tried other versions. |
Comments |
Comment by Hannu Ylitalo [ 2009 Feb 12 ] |
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. |
Comment by richlv [ 2009 Sep 24 ] |
discussed at : http://www.zabbix.com/forum/showthread.php?t=12018 |
Comment by Alexei Vladishev [ 2010 Apr 11 ] |
It exists also in Debian bug tracking system: 522904@bugs.debian.org |
Comment by Aleksandrs Saveljevs [ 2011 Jan 05 ] |
Related issue: |
Comment by richlv [ 2012 Dec 12 ] |
this should be fixed in |
Comment by richlv [ 2013 Dec 04 ] |
this issue mentioned both snmp and web monitoring, |
Comment by richlv [ 2014 Feb 18 ] |
CURLOPT_INTERFACE might be the solution (from http://curl.haxx.se/libcurl/c/curl_easy_setopt.html ) |
Comment by richlv [ 2014 Sep 22 ] |
ZBX-8804 discusses the same problem with database connections |
Comment by Igors Homjakovs (Inactive) [ 2015 Feb 05 ] |
Fixed in svn://svn.zabbix.com/branches/dev/ZBX-591 |
Comment by Andris Zeila [ 2015 Feb 10 ] |
Successfully tested |
Comment by Igors Homjakovs (Inactive) [ 2015 Feb 11 ] |
Available in 2.4.4rc1 r52152 and 2.5.0 (trunk) r52153. |
Comment by Igors Homjakovs (Inactive) [ 2015 May 27 ] |
(1) Documented in: asaveljevs ChangeLog entry for this issue was improved since r52512 by capitalizing terms and adding proper spacing:
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. |
Comment by Aleksandrs Saveljevs [ 2015 May 27 ] |
(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. |
Comment by Volker Fröhlich [ 2015 May 27 ] |
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. |
Comment by richlv [ 2015 Dec 24 ] |
can this one be cleaned up still in 2015 ? |
Comment by Aleksandrs Saveljevs [ 2015 Dec 29 ] |
Solved (1) and (2) on December 29. |