Details

      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.

        Issue Links

          Activity

          Hide
          Hannu Ylitalo added a comment -

          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.

          Show
          Hannu Ylitalo added a comment - 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.
          Show
          richlv added a comment - discussed at : http://www.zabbix.com/forum/showthread.php?t=12018 http://www.zabbix.com/forum/showthread.php?t=11487
          Hide
          Alexei Vladishev added a comment - - edited

          It exists also in Debian bug tracking system: 522904@bugs.debian.org

          Show
          Alexei Vladishev added a comment - - edited It exists also in Debian bug tracking system: 522904@bugs.debian.org
          Hide
          Aleksandrs Saveljevs added a comment -

          Related issue: ZBX-3379.

          Show
          Aleksandrs Saveljevs added a comment - Related issue: ZBX-3379 .
          Hide
          richlv added a comment -

          this should be fixed in ZBX-3379

          Show
          richlv added a comment - this should be fixed in ZBX-3379
          Hide
          richlv added a comment -

          this issue mentioned both snmp and web monitoring, ZBX-3379 only fixed snmp. reopening.

          Show
          richlv added a comment - this issue mentioned both snmp and web monitoring, ZBX-3379 only fixed snmp. reopening.
          Hide
          richlv added a comment -

          CURLOPT_INTERFACE might be the solution (from http://curl.haxx.se/libcurl/c/curl_easy_setopt.html )

          Show
          richlv added a comment - CURLOPT_INTERFACE might be the solution (from http://curl.haxx.se/libcurl/c/curl_easy_setopt.html )
          Hide
          richlv added a comment -

          ZBX-8804 discusses the same problem with database connections

          Show
          richlv added a comment - ZBX-8804 discusses the same problem with database connections
          Hide
          Igors Homjakovs (Inactive) added a comment -

          Fixed in svn://svn.zabbix.com/branches/dev/ZBX-591

          Show
          Igors Homjakovs (Inactive) added a comment - Fixed in svn://svn.zabbix.com/branches/dev/ZBX-591
          Hide
          Andris Zeila added a comment -

          Successfully tested

          Show
          Andris Zeila added a comment - Successfully tested
          Hide
          Igors Homjakovs (Inactive) added a comment - - edited

          Available in 2.4.4rc1 r52152 and 2.5.0 (trunk) r52153.

          Show
          Igors Homjakovs (Inactive) added a comment - - edited Available in 2.4.4rc1 r52152 and 2.5.0 (trunk) r52153.
          Hide
          Igors Homjakovs (Inactive) added a comment - - edited

          (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

          Aleksandrs Saveljevs 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.

          Aleksandrs Saveljevs 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

          Aleksandrs Saveljevs 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 Valkovskis Reviewed, with small formatting fixes. The current version seems satisfactory. CLOSED.

          Show
          Igors Homjakovs (Inactive) added a comment - - edited (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 Aleksandrs Saveljevs 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. Aleksandrs Saveljevs 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 Aleksandrs Saveljevs 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 Valkovskis Reviewed, with small formatting fixes. The current version seems satisfactory. CLOSED.
          Hide
          Aleksandrs Saveljevs added a comment - - edited

          (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.

          Igors Homjakovs 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)
          

          Aleksandrs Saveljevs 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 Valkovskis 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
          

          Aleksandrs Saveljevs Looks good. Fixed in pre-2.4.8rc1 and pre-3.0.0alpha6 directly in r57389. CLOSED.

          Show
          Aleksandrs Saveljevs added a comment - - edited (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. Igors Homjakovs 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) Aleksandrs Saveljevs 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 Valkovskis 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 Aleksandrs Saveljevs Looks good. Fixed in pre-2.4.8rc1 and pre-3.0.0alpha6 directly in r57389. CLOSED.
          Hide
          Volker Fröhlich added a comment -

          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.

          Show
          Volker Fröhlich added a comment - 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.
          Hide
          richlv added a comment -

          can this one be cleaned up still in 2015 ?

          Show
          richlv added a comment - can this one be cleaned up still in 2015 ?
          Hide
          Aleksandrs Saveljevs added a comment -

          Solved (1) and (2) on December 29.

          Show
          Aleksandrs Saveljevs added a comment - Solved (1) and (2) on December 29.

            People

            • Assignee:
              Unassigned
              Reporter:
              Hannu Ylitalo
            • Votes:
              5 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: