Lucho Lopez | 26 Jan 09:12 2014
Picon

Re: zabbix-proxy: What am I doing wrong?

2014-01-24 J C Lawrence <claw <at> kanga.nu>
>
> What am I doing wrong in getting an active zabbix proxy to work?
>
> I have a host which is seemingly happy running the zabbix-server in
> AWS.  I then have a number of other hosts running zabbix-agent, which
> register themselves on build with the zabbix-server by API call using
> pyzabbix ala:
>
>    c = zapi.host.create ({
>      "host": HOST_TAG,
>      "interfaces": [
> {
>          "type": 1,
>          "main": 1,
>          "useip": 1,
>          "ip": HOST_IP,
>          "dns": "",
>          "port": "10050"
> },
> {
>         "type": 2,
>          "main": 1,
>          "useip": 1,
>          "ip": HOST_IP,
>          "dns": "",
>          "port": "161"
> }
> ],
>      "templates": [
> {
>          "templateid": "10050" # Zabbix agent
> },
> {
>          "templateid": "10069" # SNMP Linux
>        },
> {
>          "templateid": "10094" # HTTP
>        },
> {
>          "templateid": "10095" # HTTPS
>        },
> {
>          "templateid": "10102" # SSH
>        },
> {
>          "templateid": "10104" # Ping
>        },
> ],
>      "groups": [{"groupid": GROUP_ID}],
> }
>    )
>
> This works just fine. Nice pretty green lights, and graphs and all the
> good stuff.  Life is good.  I mention this to show that the various
> configurations seem to be setup correctly for the non proxy case.
>
> However I'm now getting ready to move all the agent boxes into VPCs, and
> I'll have a dozen or more VPCs that I'd like to monitor with a single
> external server which collects data from hosts in the VPCs via a proxy.
> So before I went whole hog with the VPCs, I deployed a host running
> zabbix proxy, and have the agent hosts register themselves with the
> zabbix server ala:
>
>    c = zapi.host.create ({
>      "host": HOST_TAG,
>      "interfaces": [
> {
>          "type": 1,
>          "main": 1,
>          "useip": 1,
>          "ip": HOST_IP,
>          "dns": "",
>          "port": "10050"
> },
> {
>         "type": 2,
>          "main": 1,
>          "useip": 1,
>          "ip": HOST_IP,
>          "dns": "",
>          "port": "161"
> }
> ],
>      "templates": [
> {
>          "templateid": "10050" # Zabbix agent
> },
> {
>          "templateid": "10069" # SNMP Linux
>        },
> {
>          "templateid": "10094" # HTTP
>        },
> {
>          "templateid": "10095" # HTTPS
>        },
> {
>          "templateid": "10102" # SSH
>        },
> {
>          "templateid": "10104" # Ping
>        },
> ],
>      "groups": [{"groupid": GROUP_ID}],
>      "proxy_hostid": PROXY_ID,   # <======== This is the only change
> }
>    )
>
> The ID used for the proxy_hostid is taken from the Zabbix database as
> the ID of the proxy created under Administration/DM. The Zabbix proxy
> is configured as an active proxy.  And this...almost works. Well,
> actually it doesn't work at all.  No monitoring data gets through.  Why?
>

Are you sure that your "PROXY_ID" is the correct "proxy_hostid"?

If EVERY host registered in zabbix server "ala" has its own "hostid", then the  zabbix proxy has its own "hostid" too. Therefore, I think you are using the proxy's id to fill the proxy's HOSTID field...

Please don't offense, I don't speak english and I'm trying to explain my idea :)

--
Luis from Uruguay <Lucho>

>
> The hosts are registered with the Zabbix server just fine and show as
> being proxied by the right proxy host.  The individual proxies report
> under Administration/DM as frequently sending information in the zabbix
> UI.  But, there's no data and all the proxied hosts alert with all their
> monitors failing.  There's no contact with the zabbix agent on the
> target hosts, nor SNMP, nor ICMP, etc.
>
> The zabbix server logs show:
>
>    1249:20140124:033726.303 cannot send list of active checks to
> [10.239.54.86]: host [prodBETA-mon-1] not found
>    1249:20140124:033733.249 cannot send list of active checks to
> [10.139.61.196]: host [prodBETA-lb-1] not found
>    1249:20140124:033738.341 cannot send list of active checks to
> [10.211.151.240]: host [prodBETA-web-2] not found
>    1249:20140124:033753.177 cannot send list of active checks to
> [10.239.142.80]: host [prodBETA-web-1] not found
>
> The zabbix proxy logs show:
>
>   16921:20140124:034025.473 cannot send list of active checks to
> [10.239.54.86]: host [prodBETA-mon-1] not found
>   16921:20140124:034033.473 cannot send list of active checks to
> [10.139.61.196]: host [prodBETA-lb-1] not found
>   16921:20140124:034037.165 cannot send list of active checks to
> [10.211.151.240]: host [prodBETA-web-2] not found
>   16921:20140124:034052.956 cannot send list of active checks to
> [10.239.142.80]: host [prodBETA-web-1] not found
>
> The zabbix agent logs show:
>
>   16091:20140124:034025.441 No active checks on server: host
> [prodBETA-mon-1] not found
>   16093:20140124:034025.473 No active checks on server: host
> [prodBETA-mon-1] not found
>   16092:20140124:034126.434 No active checks on server: host
> [prodBETA-mon-1] not found
>   16091:20140124:034225.452 No active checks on server: host
> [prodBETA-mon-1] not found
>
> DNS for those names above (eg prodBETA-web-1) is _NOT_ setup, but all
> monitoring is configured in terms of raw IP addresses, not DNS. Yes, the
> "name" of the proxy in Administration/DM is the same as the value of
> Hostname in zabbix_proxy.conf.  I checked, and all the names line up
> perfectly.  In addition the IP address of the proxy is listed in the
> values of Server and ServerActive in the agent config.  Ports 80 (HTTP),
> 443 (HTTPS), 162 (SNMP), 10050 (Zabbix), 10051 (Zabbix), ICMP echo and
> request, and port 161 UDP (snmptrap) are open among the zabbix server,
> proxy and agent hosts -- and yet they all alert as failing.
>
> BTW this is all with Zabbix 2.2 from the Ubuntu packages.
>
> So, what am I missing?
>
> -- JCL

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Zabbix-users mailing list
Zabbix-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zabbix-users
Lucho Lopez | 26 Jan 09:36 2014
Picon

Re: zabbix-proxy: What am I doing wrong?




2014-01-26 Lucho Lopez <luislopez72 <at> gmail.com>
>
> 2014-01-24 J C Lawrence <claw <at> kanga.nu>
>
> >
> > What am I doing wrong in getting an active zabbix proxy to work?
> >
> > I have a host which is seemingly happy running the zabbix-server in
> > AWS.  I then have a number of other hosts running zabbix-agent, which
> > register themselves on build with the zabbix-server by API call using
> > pyzabbix ala:
> >
> >    c = zapi.host.create ({
> >      "host": HOST_TAG,
> >      "interfaces": [
> > {
> >          "type": 1,
> >          "main": 1,
> >          "useip": 1,
> >          "ip": HOST_IP,
> >          "dns": "",
> >          "port": "10050"
> > },
> > {
> >         "type": 2,
> >          "main": 1,
> >          "useip": 1,
> >          "ip": HOST_IP,
> >          "dns": "",
> >          "port": "161"
> > }
> > ],
> >      "templates": [
> > {
> >          "templateid": "10050" # Zabbix agent
> > },
> > {
> >          "templateid": "10069" # SNMP Linux
> >        },
> > {
> >          "templateid": "10094" # HTTP
> >        },
> > {
> >          "templateid": "10095" # HTTPS
> >        },
> > {
> >          "templateid": "10102" # SSH
> >        },
> > {
> >          "templateid": "10104" # Ping
> >        },
> > ],
> >      "groups": [{"groupid": GROUP_ID}],
> > }
> >    )
> >
> > This works just fine. Nice pretty green lights, and graphs and all the
> > good stuff.  Life is good.  I mention this to show that the various
> > configurations seem to be setup correctly for the non proxy case.
> >
> > However I'm now getting ready to move all the agent boxes into VPCs, and
> > I'll have a dozen or more VPCs that I'd like to monitor with a single
> > external server which collects data from hosts in the VPCs via a proxy.
> > So before I went whole hog with the VPCs, I deployed a host running
> > zabbix proxy, and have the agent hosts register themselves with the
> > zabbix server ala:
> >
> >    c = zapi.host.create ({
> >      "host": HOST_TAG,
> >      "interfaces": [
> > {
> >          "type": 1,
> >          "main": 1,
> >          "useip": 1,
> >          "ip": HOST_IP,
> >          "dns": "",
> >          "port": "10050"
> > },
> > {
> >         "type": 2,
> >          "main": 1,
> >          "useip": 1,
> >          "ip": HOST_IP,
> >          "dns": "",
> >          "port": "161"
> > }
> > ],
> >      "templates": [
> > {
> >          "templateid": "10050" # Zabbix agent
> > },
> > {
> >          "templateid": "10069" # SNMP Linux
> >        },
> > {
> >          "templateid": "10094" # HTTP
> >        },
> > {
> >          "templateid": "10095" # HTTPS
> >        },
> > {
> >          "templateid": "10102" # SSH
> >        },
> > {
> >          "templateid": "10104" # Ping
> >        },
> > ],
> >      "groups": [{"groupid": GROUP_ID}],
> >      "proxy_hostid": PROXY_ID,   # <======== This is the only change
> > }
> >    )
> >
> > The ID used for the proxy_hostid is taken from the Zabbix database as
> > the ID of the proxy created under Administration/DM. The Zabbix proxy
> > is configured as an active proxy.  And this...almost works. Well,
> > actually it doesn't work at all.  No monitoring data gets through.  Why?
> >
>
> Are you sure that your "PROXY_ID" is the correct "proxy_hostid"?
>
> If EVERY host registered in zabbix server "ala" has its own "hostid", then the  zabbix proxy has its own "hostid" too. Therefore, I think you are using the proxy's id to fill the proxy's HOSTID field...
>
> Please don't offense, I don't speak english and I'm trying to explain my idea :)

I found this... the proxy_hostid must be a string.
https://www.zabbix.com/documentation/2.2/manual/api/reference/host/object#host

> --
> Luis from Uruguay <Lucho>
>
> >
> > The hosts are registered with the Zabbix server just fine and show as
> > being proxied by the right proxy host.  The individual proxies report
> > under Administration/DM as frequently sending information in the zabbix
> > UI.  But, there's no data and all the proxied hosts alert with all their
> > monitors failing.  There's no contact with the zabbix agent on the
> > target hosts, nor SNMP, nor ICMP, etc.
> >
> > The zabbix server logs show:
> >
> >    1249:20140124:033726.303 cannot send list of active checks to
> > [10.239.54.86]: host [prodBETA-mon-1] not found
> >    1249:20140124:033733.249 cannot send list of active checks to
> > [10.139.61.196]: host [prodBETA-lb-1] not found
> >    1249:20140124:033738.341 cannot send list of active checks to
> > [10.211.151.240]: host [prodBETA-web-2] not found
> >    1249:20140124:033753.177 cannot send list of active checks to
> > [10.239.142.80]: host [prodBETA-web-1] not found
> >
> > The zabbix proxy logs show:
> >
> >   16921:20140124:034025.473 cannot send list of active checks to
> > [10.239.54.86]: host [prodBETA-mon-1] not found
> >   16921:20140124:034033.473 cannot send list of active checks to
> > [10.139.61.196]: host [prodBETA-lb-1] not found
> >   16921:20140124:034037.165 cannot send list of active checks to
> > [10.211.151.240]: host [prodBETA-web-2] not found
> >   16921:20140124:034052.956 cannot send list of active checks to
> > [10.239.142.80]: host [prodBETA-web-1] not found
> >
> > The zabbix agent logs show:
> >
> >   16091:20140124:034025.441 No active checks on server: host
> > [prodBETA-mon-1] not found
> >   16093:20140124:034025.473 No active checks on server: host
> > [prodBETA-mon-1] not found
> >   16092:20140124:034126.434 No active checks on server: host
> > [prodBETA-mon-1] not found
> >   16091:20140124:034225.452 No active checks on server: host
> > [prodBETA-mon-1] not found
> >
> > DNS for those names above (eg prodBETA-web-1) is _NOT_ setup, but all
> > monitoring is configured in terms of raw IP addresses, not DNS. Yes, the
> > "name" of the proxy in Administration/DM is the same as the value of
> > Hostname in zabbix_proxy.conf.  I checked, and all the names line up
> > perfectly.  In addition the IP address of the proxy is listed in the
> > values of Server and ServerActive in the agent config.  Ports 80 (HTTP),
> > 443 (HTTPS), 162 (SNMP), 10050 (Zabbix), 10051 (Zabbix), ICMP echo and
> > request, and port 161 UDP (snmptrap) are open among the zabbix server,
> > proxy and agent hosts -- and yet they all alert as failing.
> >
> > BTW this is all with Zabbix 2.2 from the Ubuntu packages.
> >
> > So, what am I missing?
> >
> > -- JCL
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Zabbix-users mailing list
Zabbix-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zabbix-users
Patrik Uytterhoeven | 26 Jan 10:22 2014
Picon

Re: Installation on CentOS 6 (Ganesh Hariharan)

This guide should work 

https://www.zabbix.com/documentation/2.2/manual/installation/install_from_packages

zabbix-web-mysql => replace mysql with the database u want like pgsqlas u can see packages are available in the repohttp://repo.zabbix.com/zabbix/2.2/rhel/6/x86_64/



-----Original message-----
> From:zabbix-users-request <at> lists.sourceforge.net <zabbix-users-request <at> lists.sourceforge.net>
> Sent: Sunday 26th January 2014 9:37
> To: zabbix-users <at> lists.sourceforge.net
> Subject: Zabbix-users Digest, Vol 69, Issue 5
>
> Send Zabbix-users mailing list submissions to
> zabbix-users <at> lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/zabbix-users
> or, via email, send a message with subject or body 'help' to
> zabbix-users-request <at> lists.sourceforge.net
>
> You can reach the person managing the list at
> zabbix-users-owner <at> lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Zabbix-users digest..."
>
>
> Today's Topics:
>
> 1. Installation on CentOS 6 (Ganesh Hariharan)
> 2. zabbix-proxy: What am I doing wrong? (J C Lawrence)
> 3. Re: zabbix-proxy: What am I doing wrong? (Lucho Lopez)
> 4. Re: zabbix-proxy: What am I doing wrong? (Lucho Lopez)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 23 Jan 2014 18:23:20 +0530
> From: Ganesh Hariharan <ghariharan <at> gmail.com>
> Subject: [Zabbix-users] Installation on CentOS 6
> To: zabbix-users <at> lists.sourceforge.net
> Message-ID:
> <CABj+Yo+csFTfCNqQnrVFTAALsEk2QSiiHaBNNXXJoEEjuVmHWQ <at> mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I get the below error while installing zabbix web
>
> error: Failed dependencies:
> zabbix-web-database = 2.2.0-1.el6 is needed by zabbix-web-2.2.0-1.el6.noarch
>
> but I am unable to get the rpm in question from the zabbix site, is that
> anything I am missing? or is there any alternative...
>
>
> TIA
> G
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Thu, 23 Jan 2014 20:04:36 -0800
> From: J C Lawrence <claw <at> kanga.nu>
> Subject: [Zabbix-users] zabbix-proxy: What am I doing wrong?
> To: zabbix-users <at> lists.sourceforge.net
> Message-ID: <52E1E654.5060504 <at> kanga.nu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> What am I doing wrong in getting an active zabbix proxy to work?
>
> I have a host which is seemingly happy running the zabbix-server in
> AWS. I then have a number of other hosts running zabbix-agent, which
> register themselves on build with the zabbix-server by API call using
> pyzabbix ala:
>
> c = zapi.host.create ({
> "host": HOST_TAG,
> "interfaces": [
> {
> "type": 1,
> "main": 1,
> "useip": 1,
> "ip": HOST_IP,
> "dns": "",
> "port": "10050"
> },
> {
> "type": 2,
> "main": 1,
> "useip": 1,
> "ip": HOST_IP,
> "dns": "",
> "port": "161"
> }
> ],
> "templates": [
> {
> "templateid": "10050" # Zabbix agent
> },
> {
> "templateid": "10069" # SNMP Linux
> },
> {
> "templateid": "10094" # HTTP
> },
> {
> "templateid": "10095" # HTTPS
> },
> {
> "templateid": "10102" # SSH
> },
> {
> "templateid": "10104" # Ping
> },
> ],
> "groups": [{"groupid": GROUP_ID}],
> }
> )
>
> This works just fine. Nice pretty green lights, and graphs and all the
> good stuff. Life is good. I mention this to show that the various
> configurations seem to be setup correctly for the non proxy case.
>
> However I'm now getting ready to move all the agent boxes into VPCs, and
> I'll have a dozen or more VPCs that I'd like to monitor with a single
> external server which collects data from hosts in the VPCs via a proxy.
> So before I went whole hog with the VPCs, I deployed a host running
> zabbix proxy, and have the agent hosts register themselves with the
> zabbix server ala:
>
> c = zapi.host.create ({
> "host": HOST_TAG,
> "interfaces": [
> {
> "type": 1,
> "main": 1,
> "useip": 1,
> "ip": HOST_IP,
> "dns": "",
> "port": "10050"
> },
> {
> "type": 2,
> "main": 1,
> "useip": 1,
> "ip": HOST_IP,
> "dns": "",
> "port": "161"
> }
> ],
> "templates": [
> {
> "templateid": "10050" # Zabbix agent
> },
> {
> "templateid": "10069" # SNMP Linux
> },
> {
> "templateid": "10094" # HTTP
> },
> {
> "templateid": "10095" # HTTPS
> },
> {
> "templateid": "10102" # SSH
> },
> {
> "templateid": "10104" # Ping
> },
> ],
> "groups": [{"groupid": GROUP_ID}],
> "proxy_hostid": PROXY_ID, # <======== This is the only change
> }
> )
>
> The ID used for the proxy_hostid is taken from the Zabbix database as
> the ID of the proxy created under Administration/DM. The Zabbix proxy
> is configured as an active proxy. And this...almost works. Well,
> actually it doesn't work at all. No monitoring data gets through. Why?
>
> The hosts are registered with the Zabbix server just fine and show as
> being proxied by the right proxy host. The individual proxies report
> under Administration/DM as frequently sending information in the zabbix
> UI. But, there's no data and all the proxied hosts alert with all their
> monitors failing. There's no contact with the zabbix agent on the
> target hosts, nor SNMP, nor ICMP, etc.
>
> The zabbix server logs show:
>
> 1249:20140124:033726.303 cannot send list of active checks to
> [10.239.54.86]: host [prodBETA-mon-1] not found
> 1249:20140124:033733.249 cannot send list of active checks to
> [10.139.61.196]: host [prodBETA-lb-1] not found
> 1249:20140124:033738.341 cannot send list of active checks to
> [10.211.151.240]: host [prodBETA-web-2] not found
> 1249:20140124:033753.177 cannot send list of active checks to
> [10.239.142.80]: host [prodBETA-web-1] not found
>
> The zabbix proxy logs show:
>
> 16921:20140124:034025.473 cannot send list of active checks to
> [10.239.54.86]: host [prodBETA-mon-1] not found
> 16921:20140124:034033.473 cannot send list of active checks to
> [10.139.61.196]: host [prodBETA-lb-1] not found
> 16921:20140124:034037.165 cannot send list of active checks to
> [10.211.151.240]: host [prodBETA-web-2] not found
> 16921:20140124:034052.956 cannot send list of active checks to
> [10.239.142.80]: host [prodBETA-web-1] not found
>
> The zabbix agent logs show:
>
> 16091:20140124:034025.441 No active checks on server: host
> [prodBETA-mon-1] not found
> 16093:20140124:034025.473 No active checks on server: host
> [prodBETA-mon-1] not found
> 16092:20140124:034126.434 No active checks on server: host
> [prodBETA-mon-1] not found
> 16091:20140124:034225.452 No active checks on server: host
> [prodBETA-mon-1] not found
>
> DNS for those names above (eg prodBETA-web-1) is _NOT_ setup, but all
> monitoring is configured in terms of raw IP addresses, not DNS. Yes, the
> "name" of the proxy in Administration/DM is the same as the value of
> Hostname in zabbix_proxy.conf. I checked, and all the names line up
> perfectly. In addition the IP address of the proxy is listed in the
> values of Server and ServerActive in the agent config. Ports 80 (HTTP),
> 443 (HTTPS), 162 (SNMP), 10050 (Zabbix), 10051 (Zabbix), ICMP echo and
> request, and port 161 UDP (snmptrap) are open among the zabbix server,
> proxy and agent hosts -- and yet they all alert as failing.
>
> BTW this is all with Zabbix 2.2 from the Ubuntu packages.
>
> So, what am I missing?
>
> -- JCL
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 26 Jan 2014 06:12:47 -0200
> From: Lucho Lopez <luislopez72 <at> gmail.com>
> Subject: Re: [Zabbix-users] zabbix-proxy: What am I doing wrong?
> To: "zabbix-users <at> lists.sourceforge.net"
> <zabbix-users <at> lists.sourceforge.net>
> Message-ID:
> <CALjfk2BRCMmoqvu=b5AQRtVU94CLxmWQ6fCOYdCsT6giaApgrg <at> mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 2014-01-24 J C Lawrence <claw <at> kanga.nu>
> >
> > What am I doing wrong in getting an active zabbix proxy to work?
> >
> > I have a host which is seemingly happy running the zabbix-server in
> > AWS. I then have a number of other hosts running zabbix-agent, which
> > register themselves on build with the zabbix-server by API call using
> > pyzabbix ala:
> >
> > c = zapi.host.create ({
> > "host": HOST_TAG,
> > "interfaces": [
> > {
> > "type": 1,
> > "main": 1,
> > "useip": 1,
> > "ip": HOST_IP,
> > "dns": "",
> > "port": "10050"
> > },
> > {
> > "type": 2,
> > "main": 1,
> > "useip": 1,
> > "ip": HOST_IP,
> > "dns": "",
> > "port": "161"
> > }
> > ],
> > "templates": [
> > {
> > "templateid": "10050" # Zabbix agent
> > },
> > {
> > "templateid": "10069" # SNMP Linux
> > },
> > {
> > "templateid": "10094" # HTTP
> > },
> > {
> > "templateid": "10095" # HTTPS
> > },
> > {
> > "templateid": "10102" # SSH
> > },
> > {
> > "templateid": "10104" # Ping
> > },
> > ],
> > "groups": [{"groupid": GROUP_ID}],
> > }
> > )
> >
> > This works just fine. Nice pretty green lights, and graphs and all the
> > good stuff. Life is good. I mention this to show that the various
> > configurations seem to be setup correctly for the non proxy case.
> >
> > However I'm now getting ready to move all the agent boxes into VPCs, and
> > I'll have a dozen or more VPCs that I'd like to monitor with a single
> > external server which collects data from hosts in the VPCs via a proxy.
> > So before I went whole hog with the VPCs, I deployed a host running
> > zabbix proxy, and have the agent hosts register themselves with the
> > zabbix server ala:
> >
> > c = zapi.host.create ({
> > "host": HOST_TAG,
> > "interfaces": [
> > {
> > "type": 1,
> > "main": 1,
> > "useip": 1,
> > "ip": HOST_IP,
> > "dns": "",
> > "port": "10050"
> > },
> > {
> > "type": 2,
> > "main": 1,
> > "useip": 1,
> > "ip": HOST_IP,
> > "dns": "",
> > "port": "161"
> > }
> > ],
> > "templates": [
> > {
> > "templateid": "10050" # Zabbix agent
> > },
> > {
> > "templateid": "10069" # SNMP Linux
> > },
> > {
> > "templateid": "10094" # HTTP
> > },
> > {
> > "templateid": "10095" # HTTPS
> > },
> > {
> > "templateid": "10102" # SSH
> > },
> > {
> > "templateid": "10104" # Ping
> > },
> > ],
> > "groups": [{"groupid": GROUP_ID}],
> > "proxy_hostid": PROXY_ID, # <======== This is the only change
> > }
> > )
> >
> > The ID used for the proxy_hostid is taken from the Zabbix database as
> > the ID of the proxy created under Administration/DM. The Zabbix proxy
> > is configured as an active proxy. And this...almost works. Well,
> > actually it doesn't work at all. No monitoring data gets through. Why?
> >
>
> Are you sure that your "PROXY_ID" is the correct "proxy_hostid"?
>
> If EVERY host registered in zabbix server "ala" has its own "hostid", then
> the zabbix proxy has its own "hostid" too. Therefore, I think you are
> using the proxy's id to fill the proxy's HOSTID field...
>
> Please don't offense, I don't speak english and I'm trying to explain my
> idea :)
>
> --
> Luis from Uruguay <Lucho>
>
> >
> > The hosts are registered with the Zabbix server just fine and show as
> > being proxied by the right proxy host. The individual proxies report
> > under Administration/DM as frequently sending information in the zabbix
> > UI. But, there's no data and all the proxied hosts alert with all their
> > monitors failing. There's no contact with the zabbix agent on the
> > target hosts, nor SNMP, nor ICMP, etc.
> >
> > The zabbix server logs show:
> >
> > 1249:20140124:033726.303 cannot send list of active checks to
> > [10.239.54.86]: host [prodBETA-mon-1] not found
> > 1249:20140124:033733.249 cannot send list of active checks to
> > [10.139.61.196]: host [prodBETA-lb-1] not found
> > 1249:20140124:033738.341 cannot send list of active checks to
> > [10.211.151.240]: host [prodBETA-web-2] not found
> > 1249:20140124:033753.177 cannot send list of active checks to
> > [10.239.142.80]: host [prodBETA-web-1] not found
> >
> > The zabbix proxy logs show:
> >
> > 16921:20140124:034025.473 cannot send list of active checks to
> > [10.239.54.86]: host [prodBETA-mon-1] not found
> > 16921:20140124:034033.473 cannot send list of active checks to
> > [10.139.61.196]: host [prodBETA-lb-1] not found
> > 16921:20140124:034037.165 cannot send list of active checks to
> > [10.211.151.240]: host [prodBETA-web-2] not found
> > 16921:20140124:034052.956 cannot send list of active checks to
> > [10.239.142.80]: host [prodBETA-web-1] not found
> >
> > The zabbix agent logs show:
> >
> > 16091:20140124:034025.441 No active checks on server: host
> > [prodBETA-mon-1] not found
> > 16093:20140124:034025.473 No active checks on server: host
> > [prodBETA-mon-1] not found
> > 16092:20140124:034126.434 No active checks on server: host
> > [prodBETA-mon-1] not found
> > 16091:20140124:034225.452 No active checks on server: host
> > [prodBETA-mon-1] not found
> >
> > DNS for those names above (eg prodBETA-web-1) is _NOT_ setup, but all
> > monitoring is configured in terms of raw IP addresses, not DNS. Yes, the
> > "name" of the proxy in Administration/DM is the same as the value of
> > Hostname in zabbix_proxy.conf. I checked, and all the names line up
> > perfectly. In addition the IP address of the proxy is listed in the
> > values of Server and ServerActive in the agent config. Ports 80 (HTTP),
> > 443 (HTTPS), 162 (SNMP), 10050 (Zabbix), 10051 (Zabbix), ICMP echo and
> > request, and port 161 UDP (snmptrap) are open among the zabbix server,
> > proxy and agent hosts -- and yet they all alert as failing.
> >
> > BTW this is all with Zabbix 2.2 from the Ubuntu packages.
> >
> > So, what am I missing?
> >
> > -- JCL
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 4
> Date: Sun, 26 Jan 2014 06:36:30 -0200
> From: Lucho Lopez <luislopez72 <at> gmail.com>
> Subject: Re: [Zabbix-users] zabbix-proxy: What am I doing wrong?
> To: "zabbix-users <at> lists.sourceforge.net"
> <zabbix-users <at> lists.sourceforge.net>
> Message-ID:
> <CALjfk2AwNK5=CHVE-81936wpcR6p+pqKXCS_VErCt1J42YTEzw <at> mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 2014-01-26 Lucho Lopez <luislopez72 <at> gmail.com>
> >
> > 2014-01-24 J C Lawrence <claw <at> kanga.nu>
> >
> > >
> > > What am I doing wrong in getting an active zabbix proxy to work?
> > >
> > > I have a host which is seemingly happy running the zabbix-server in
> > > AWS. I then have a number of other hosts running zabbix-agent, which
> > > register themselves on build with the zabbix-server by API call using
> > > pyzabbix ala:
> > >
> > > c = zapi.host.create ({
> > > "host": HOST_TAG,
> > > "interfaces": [
> > > {
> > > "type": 1,
> > > "main": 1,
> > > "useip": 1,
> > > "ip": HOST_IP,
> > > "dns": "",
> > > "port": "10050"
> > > },
> > > {
> > > "type": 2,
> > > "main": 1,
> > > "useip": 1,
> > > "ip": HOST_IP,
> > > "dns": "",
> > > "port": "161"
> > > }
> > > ],
> > > "templates": [
> > > {
> > > "templateid": "10050" # Zabbix agent
> > > },
> > > {
> > > "templateid": "10069" # SNMP Linux
> > > },
> > > {
> > > "templateid": "10094" # HTTP
> > > },
> > > {
> > > "templateid": "10095" # HTTPS
> > > },
> > > {
> > > "templateid": "10102" # SSH
> > > },
> > > {
> > > "templateid": "10104" # Ping
> > > },
> > > ],
> > > "groups": [{"groupid": GROUP_ID}],
> > > }
> > > )
> > >
> > > This works just fine. Nice pretty green lights, and graphs and all the
> > > good stuff. Life is good. I mention this to show that the various
> > > configurations seem to be setup correctly for the non proxy case.
> > >
> > > However I'm now getting ready to move all the agent boxes into VPCs, and
> > > I'll have a dozen or more VPCs that I'd like to monitor with a single
> > > external server which collects data from hosts in the VPCs via a proxy.
> > > So before I went whole hog with the VPCs, I deployed a host running
> > > zabbix proxy, and have the agent hosts register themselves with the
> > > zabbix server ala:
> > >
> > > c = zapi.host.create ({
> > > "host": HOST_TAG,
> > > "interfaces": [
> > > {
> > > "type": 1,
> > > "main": 1,
> > > "useip": 1,
> > > "ip": HOST_IP,
> > > "dns": "",
> > > "port": "10050"
> > > },
> > > {
> > > "type": 2,
> > > "main": 1,
> > > "useip": 1,
> > > "ip": HOST_IP,
> > > "dns": "",
> > > "port": "161"
> > > }
> > > ],
> > > "templates": [
> > > {
> > > "templateid": "10050" # Zabbix agent
> > > },
> > > {
> > > "templateid": "10069" # SNMP Linux
> > > },
> > > {
> > > "templateid": "10094" # HTTP
> > > },
> > > {
> > > "templateid": "10095" # HTTPS
> > > },
> > > {
> > > "templateid": "10102" # SSH
> > > },
> > > {
> > > "templateid": "10104" # Ping
> > > },
> > > ],
> > > "groups": [{"groupid": GROUP_ID}],
> > > "proxy_hostid": PROXY_ID, # <======== This is the only change
> > > }
> > > )
> > >
> > > The ID used for the proxy_hostid is taken from the Zabbix database as
> > > the ID of the proxy created under Administration/DM. The Zabbix proxy
> > > is configured as an active proxy. And this...almost works. Well,
> > > actually it doesn't work at all. No monitoring data gets through. Why?
> > >
> >
> > Are you sure that your "PROXY_ID" is the correct "proxy_hostid"?
> >
> > If EVERY host registered in zabbix server "ala" has its own "hostid",
> then the zabbix proxy has its own "hostid" too. Therefore, I think you are
> using the proxy's id to fill the proxy's HOSTID field...
> >
> > Please don't offense, I don't speak english and I'm trying to explain my
> idea :)
>
> I found this... the proxy_hostid must be a string.
> https://www.zabbix.com/documentation/2.2/manual/api/reference/host/object#host
>
> > --
> > Luis from Uruguay <Lucho>
> >
> > >
> > > The hosts are registered with the Zabbix server just fine and show as
> > > being proxied by the right proxy host. The individual proxies report
> > > under Administration/DM as frequently sending information in the zabbix
> > > UI. But, there's no data and all the proxied hosts alert with all their
> > > monitors failing. There's no contact with the zabbix agent on the
> > > target hosts, nor SNMP, nor ICMP, etc.
> > >
> > > The zabbix server logs show:
> > >
> > > 1249:20140124:033726.303 cannot send list of active checks to
> > > [10.239.54.86]: host [prodBETA-mon-1] not found
> > > 1249:20140124:033733.249 cannot send list of active checks to
> > > [10.139.61.196]: host [prodBETA-lb-1] not found
> > > 1249:20140124:033738.341 cannot send list of active checks to
> > > [10.211.151.240]: host [prodBETA-web-2] not found
> > > 1249:20140124:033753.177 cannot send list of active checks to
> > > [10.239.142.80]: host [prodBETA-web-1] not found
> > >
> > > The zabbix proxy logs show:
> > >
> > > 16921:20140124:034025.473 cannot send list of active checks to
> > > [10.239.54.86]: host [prodBETA-mon-1] not found
> > > 16921:20140124:034033.473 cannot send list of active checks to
> > > [10.139.61.196]: host [prodBETA-lb-1] not found
> > > 16921:20140124:034037.165 cannot send list of active checks to
> > > [10.211.151.240]: host [prodBETA-web-2] not found
> > > 16921:20140124:034052.956 cannot send list of active checks to
> > > [10.239.142.80]: host [prodBETA-web-1] not found
> > >
> > > The zabbix agent logs show:
> > >
> > > 16091:20140124:034025.441 No active checks on server: host
> > > [prodBETA-mon-1] not found
> > > 16093:20140124:034025.473 No active checks on server: host
> > > [prodBETA-mon-1] not found
> > > 16092:20140124:034126.434 No active checks on server: host
> > > [prodBETA-mon-1] not found
> > > 16091:20140124:034225.452 No active checks on server: host
> > > [prodBETA-mon-1] not found
> > >
> > > DNS for those names above (eg prodBETA-web-1) is _NOT_ setup, but all
> > > monitoring is configured in terms of raw IP addresses, not DNS. Yes, the
> > > "name" of the proxy in Administration/DM is the same as the value of
> > > Hostname in zabbix_proxy.conf. I checked, and all the names line up
> > > perfectly. In addition the IP address of the proxy is listed in the
> > > values of Server and ServerActive in the agent config. Ports 80 (HTTP),
> > > 443 (HTTPS), 162 (SNMP), 10050 (Zabbix), 10051 (Zabbix), ICMP echo and
> > > request, and port 161 UDP (snmptrap) are open among the zabbix server,
> > > proxy and agent hosts -- and yet they all alert as failing.
> > >
> > > BTW this is all with Zabbix 2.2 from the Ubuntu packages.
> > >
> > > So, what am I missing?
> > >
> > > -- JCL
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>
> ------------------------------
>
> _______________________________________________
> Zabbix-users mailing list
> Zabbix-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zabbix-users
>
>
> End of Zabbix-users Digest, Vol 69, Issue 5
> *******************************************
>

Upcoming Events:

Puppet Fundamentals Training | http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february

Puppet Introduction Course | http://www.open-future.be/puppet-introduction-course-7th-february

Zabbix Certified Training | http://www.open-future.be/zabbix-certified-training-10-till-12th-february

Zabbix for Large Environments Training | http://www.open-future.be /zabbix-large-environments-training-13-till-14th-february

Subscribe to our newsletter: http://eepurl.com/BUG8H


------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Zabbix-users mailing list
Zabbix-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zabbix-users
Ganesh Hariharan | 26 Jan 16:33 2014
Picon

Re: Installation on CentOS 6 (Ganesh Hariharan)

Thx, I have configured with binary, now working on web monitoring, , pls share any oointers on transactional monitoring..., I shall read the url shared as eell
G

This guide should work 

https://www.zabbix.com/documentation/2.2/manual/installation/install_from_packages

zabbix-web-mysql => replace mysql with the database u want like pgsql as u can see packages are available in the repo http://repo.zabbix.com/zabbix/2.2/rhel/6/x86_64/



-----Original message-----
> From:zabbix-users-request <at> lists.sourceforge.net <zabbix-users-request <at> lists.sourceforge.net>
> Sent: Sunday 26th January 2014 9:37
> To: zabbix-users <at> lists.sourceforge.net
> Subject: Zabbix-users Digest, Vol 69, Issue 5
>
> Send Zabbix-users mailing list submissions to
> zabbix-users <at> lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/zabbix-users
> or, via email, send a message with subject or body 'help' to
> zabbix-users-request <at> lists.sourceforge.net
>
> You can reach the person managing the list at
> zabbix-users-owner <at> lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Zabbix-users digest..."
>
>
> Today's Topics:
>
> 1. Installation on CentOS 6 (Ganesh Hariharan)
> 2. zabbix-proxy: What am I doing wrong? (J C Lawrence)
> 3. Re: zabbix-proxy: What am I doing wrong? (Lucho Lopez)
> 4. Re: zabbix-proxy: What am I doing wrong? (Lucho Lopez)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 23 Jan 2014 18:23:20 +0530
> From: Ganesh Hariharan <ghariharan <at> gmail.com>
> Subject: [Zabbix-users] Installation on CentOS 6
> To: zabbix-users <at> lists.sourceforge.net
> Message-ID:
> <CABj+Yo+csFTfCNqQnrVFTAALsEk2QSiiHaBNNXXJoEEjuVmHWQ <at> mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I get the below error while installing zabbix web
>
> error: Failed dependencies:
> zabbix-web-database = 2.2.0-1.el6 is needed by zabbix-web-2.2.0-1.el6.noarch
>
> but I am unable to get the rpm in question from the zabbix site, is that
> anything I am missing? or is there any alternative...
>
>
> TIA
> G
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 2
> Date: Thu, 23 Jan 2014 20:04:36 -0800
> From: J C Lawrence <claw <at> kanga.nu>
> Subject: [Zabbix-users] zabbix-proxy: What am I doing wrong?
> To: zabbix-users <at> lists.sourceforge.net
> Message-ID: <52E1E654.5060504 <at> kanga.nu>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> What am I doing wrong in getting an active zabbix proxy to work?
>
> I have a host which is seemingly happy running the zabbix-server in
> AWS. I then have a number of other hosts running zabbix-agent, which
> register themselves on build with the zabbix-server by API call using
> pyzabbix ala:
>
> c = zapi.host.create ({
> "host": HOST_TAG,
> "interfaces": [
> {
> "type": 1,
> "main": 1,
> "useip": 1,
> "ip": HOST_IP,
> "dns": "",
> "port": "10050"
> },
> {
> "type": 2,
> "main": 1,
> "useip": 1,
> "ip": HOST_IP,
> "dns": "",
> "port": "161"
> }
> ],
> "templates": [
> {
> "templateid": "10050" # Zabbix agent
> },
> {
> "templateid": "10069" # SNMP Linux
> },
> {
> "templateid": "10094" # HTTP
> },
> {
> "templateid": "10095" # HTTPS
> },
> {
> "templateid": "10102" # SSH
> },
> {
> "templateid": "10104" # Ping
> },
> ],
> "groups": [{"groupid": GROUP_ID}],
> }
> )
>
> This works just fine. Nice pretty green lights, and graphs and all the
> good stuff. Life is good. I mention this to show that the various
> configurations seem to be setup correctly for the non proxy case.
>
> However I'm now getting ready to move all the agent boxes into VPCs, and
> I'll have a dozen or more VPCs that I'd like to monitor with a single
> external server which collects data from hosts in the VPCs via a proxy.
> So before I went whole hog with the VPCs, I deployed a host running
> zabbix proxy, and have the agent hosts register themselves with the
> zabbix server ala:
>
> c = zapi.host.create ({
> "host": HOST_TAG,
> "interfaces": [
> {
> "type": 1,
> "main": 1,
> "useip": 1,
> "ip": HOST_IP,
> "dns": "",
> "port": "10050"
> },
> {
> "type": 2,
> "main": 1,
> "useip": 1,
> "ip": HOST_IP,
> "dns": "",
> "port": "161"
> }
> ],
> "templates": [
> {
> "templateid": "10050" # Zabbix agent
> },
> {
> "templateid": "10069" # SNMP Linux
> },
> {
> "templateid": "10094" # HTTP
> },
> {
> "templateid": "10095" # HTTPS
> },
> {
> "templateid": "10102" # SSH
> },
> {
> "templateid": "10104" # Ping
> },
> ],
> "groups": [{"groupid": GROUP_ID}],
> "proxy_hostid": PROXY_ID, # <======== This is the only change
> }
> )
>
> The ID used for the proxy_hostid is taken from the Zabbix database as
> the ID of the proxy created under Administration/DM. The Zabbix proxy
> is configured as an active proxy. And this...almost works. Well,
> actually it doesn't work at all. No monitoring data gets through. Why?
>
> The hosts are registered with the Zabbix server just fine and show as
> being proxied by the right proxy host. The individual proxies report
> under Administration/DM as frequently sending information in the zabbix
> UI. But, there's no data and all the proxied hosts alert with all their
> monitors failing. There's no contact with the zabbix agent on the
> target hosts, nor SNMP, nor ICMP, etc.
>
> The zabbix server logs show:
>
> 1249:20140124:033726.303 cannot send list of active checks to
> [10.239.54.86]: host [prodBETA-mon-1] not found
> 1249:20140124:033733.249 cannot send list of active checks to
> [10.139.61.196]: host [prodBETA-lb-1] not found
> 1249:20140124:033738.341 cannot send list of active checks to
> [10.211.151.240]: host [prodBETA-web-2] not found
> 1249:20140124:033753.177 cannot send list of active checks to
> [10.239.142.80]: host [prodBETA-web-1] not found
>
> The zabbix proxy logs show:
>
> 16921:20140124:034025.473 cannot send list of active checks to
> [10.239.54.86]: host [prodBETA-mon-1] not found
> 16921:20140124:034033.473 cannot send list of active checks to
> [10.139.61.196]: host [prodBETA-lb-1] not found
> 16921:20140124:034037.165 cannot send list of active checks to
> [10.211.151.240]: host [prodBETA-web-2] not found
> 16921:20140124:034052.956 cannot send list of active checks to
> [10.239.142.80]: host [prodBETA-web-1] not found
>
> The zabbix agent logs show:
>
> 16091:20140124:034025.441 No active checks on server: host
> [prodBETA-mon-1] not found
> 16093:20140124:034025.473 No active checks on server: host
> [prodBETA-mon-1] not found
> 16092:20140124:034126.434 No active checks on server: host
> [prodBETA-mon-1] not found
> 16091:20140124:034225.452 No active checks on server: host
> [prodBETA-mon-1] not found
>
> DNS for those names above (eg prodBETA-web-1) is _NOT_ setup, but all
> monitoring is configured in terms of raw IP addresses, not DNS. Yes, the
> "name" of the proxy in Administration/DM is the same as the value of
> Hostname in zabbix_proxy.conf. I checked, and all the names line up
> perfectly. In addition the IP address of the proxy is listed in the
> values of Server and ServerActive in the agent config. Ports 80 (HTTP),
> 443 (HTTPS), 162 (SNMP), 10050 (Zabbix), 10051 (Zabbix), ICMP echo and
> request, and port 161 UDP (snmptrap) are open among the zabbix server,
> proxy and agent hosts -- and yet they all alert as failing.
>
> BTW this is all with Zabbix 2.2 from the Ubuntu packages.
>
> So, what am I missing?
>
> -- JCL
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 26 Jan 2014 06:12:47 -0200
> From: Lucho Lopez <luislopez72 <at> gmail.com>
> Subject: Re: [Zabbix-users] zabbix-proxy: What am I doing wrong?
> To: "zabbix-users <at> lists.sourceforge.net"
> <zabbix-users <at> lists.sourceforge.net>
> Message-ID:
> <CALjfk2BRCMmoqvu=b5AQRtVU94CLxmWQ6fCOYdCsT6giaApgrg <at> mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 2014-01-24 J C Lawrence <claw <at> kanga.nu>
> >
> > What am I doing wrong in getting an active zabbix proxy to work?
> >
> > I have a host which is seemingly happy running the zabbix-server in
> > AWS. I then have a number of other hosts running zabbix-agent, which
> > register themselves on build with the zabbix-server by API call using
> > pyzabbix ala:
> >
> > c = zapi.host.create ({
> > "host": HOST_TAG,
> > "interfaces": [
> > {
> > "type": 1,
> > "main": 1,
> > "useip": 1,
> > "ip": HOST_IP,
> > "dns": "",
> > "port": "10050"
> > },
> > {
> > "type": 2,
> > "main": 1,
> > "useip": 1,
> > "ip": HOST_IP,
> > "dns": "",
> > "port": "161"
> > }
> > ],
> > "templates": [
> > {
> > "templateid": "10050" # Zabbix agent
> > },
> > {
> > "templateid": "10069" # SNMP Linux
> > },
> > {
> > "templateid": "10094" # HTTP
> > },
> > {
> > "templateid": "10095" # HTTPS
> > },
> > {
> > "templateid": "10102" # SSH
> > },
> > {
> > "templateid": "10104" # Ping
> > },
> > ],
> > "groups": [{"groupid": GROUP_ID}],
> > }
> > )
> >
> > This works just fine. Nice pretty green lights, and graphs and all the
> > good stuff. Life is good. I mention this to show that the various
> > configurations seem to be setup correctly for the non proxy case.
> >
> > However I'm now getting ready to move all the agent boxes into VPCs, and
> > I'll have a dozen or more VPCs that I'd like to monitor with a single
> > external server which collects data from hosts in the VPCs via a proxy.
> > So before I went whole hog with the VPCs, I deployed a host running
> > zabbix proxy, and have the agent hosts register themselves with the
> > zabbix server ala:
> >
> > c = zapi.host.create ({
> > "host": HOST_TAG,
> > "interfaces": [
> > {
> > "type": 1,
> > "main": 1,
> > "useip": 1,
> > "ip": HOST_IP,
> > "dns": "",
> > "port": "10050"
> > },
> > {
> > "type": 2,
> > "main": 1,
> > "useip": 1,
> > "ip": HOST_IP,
> > "dns": "",
> > "port": "161"
> > }
> > ],
> > "templates": [
> > {
> > "templateid": "10050" # Zabbix agent
> > },
> > {
> > "templateid": "10069" # SNMP Linux
> > },
> > {
> > "templateid": "10094" # HTTP
> > },
> > {
> > "templateid": "10095" # HTTPS
> > },
> > {
> > "templateid": "10102" # SSH
> > },
> > {
> > "templateid": "10104" # Ping
> > },
> > ],
> > "groups": [{"groupid": GROUP_ID}],
> > "proxy_hostid": PROXY_ID, # <======== This is the only change
> > }
> > )
> >
> > The ID used for the proxy_hostid is taken from the Zabbix database as
> > the ID of the proxy created under Administration/DM. The Zabbix proxy
> > is configured as an active proxy. And this...almost works. Well,
> > actually it doesn't work at all. No monitoring data gets through. Why?
> >
>
> Are you sure that your "PROXY_ID" is the correct "proxy_hostid"?
>
> If EVERY host registered in zabbix server "ala" has its own "hostid", then
> the zabbix proxy has its own "hostid" too. Therefore, I think you are
> using the proxy's id to fill the proxy's HOSTID field...
>
> Please don't offense, I don't speak english and I'm trying to explain my
> idea :)
>
> --
> Luis from Uruguay <Lucho>
>
> >
> > The hosts are registered with the Zabbix server just fine and show as
> > being proxied by the right proxy host. The individual proxies report
> > under Administration/DM as frequently sending information in the zabbix
> > UI. But, there's no data and all the proxied hosts alert with all their
> > monitors failing. There's no contact with the zabbix agent on the
> > target hosts, nor SNMP, nor ICMP, etc.
> >
> > The zabbix server logs show:
> >
> > 1249:20140124:033726.303 cannot send list of active checks to
> > [10.239.54.86]: host [prodBETA-mon-1] not found
> > 1249:20140124:033733.249 cannot send list of active checks to
> > [10.139.61.196]: host [prodBETA-lb-1] not found
> > 1249:20140124:033738.341 cannot send list of active checks to
> > [10.211.151.240]: host [prodBETA-web-2] not found
> > 1249:20140124:033753.177 cannot send list of active checks to
> > [10.239.142.80]: host [prodBETA-web-1] not found
> >
> > The zabbix proxy logs show:
> >
> > 16921:20140124:034025.473 cannot send list of active checks to
> > [10.239.54.86]: host [prodBETA-mon-1] not found
> > 16921:20140124:034033.473 cannot send list of active checks to
> > [10.139.61.196]: host [prodBETA-lb-1] not found
> > 16921:20140124:034037.165 cannot send list of active checks to
> > [10.211.151.240]: host [prodBETA-web-2] not found
> > 16921:20140124:034052.956 cannot send list of active checks to
> > [10.239.142.80]: host [prodBETA-web-1] not found
> >
> > The zabbix agent logs show:
> >
> > 16091:20140124:034025.441 No active checks on server: host
> > [prodBETA-mon-1] not found
> > 16093:20140124:034025.473 No active checks on server: host
> > [prodBETA-mon-1] not found
> > 16092:20140124:034126.434 No active checks on server: host
> > [prodBETA-mon-1] not found
> > 16091:20140124:034225.452 No active checks on server: host
> > [prodBETA-mon-1] not found
> >
> > DNS for those names above (eg prodBETA-web-1) is _NOT_ setup, but all
> > monitoring is configured in terms of raw IP addresses, not DNS. Yes, the
> > "name" of the proxy in Administration/DM is the same as the value of
> > Hostname in zabbix_proxy.conf. I checked, and all the names line up
> > perfectly. In addition the IP address of the proxy is listed in the
> > values of Server and ServerActive in the agent config. Ports 80 (HTTP),
> > 443 (HTTPS), 162 (SNMP), 10050 (Zabbix), 10051 (Zabbix), ICMP echo and
> > request, and port 161 UDP (snmptrap) are open among the zabbix server,
> > proxy and agent hosts -- and yet they all alert as failing.
> >
> > BTW this is all with Zabbix 2.2 from the Ubuntu packages.
> >
> > So, what am I missing?
> >
> > -- JCL
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 4
> Date: Sun, 26 Jan 2014 06:36:30 -0200
> From: Lucho Lopez <luislopez72 <at> gmail.com>
> Subject: Re: [Zabbix-users] zabbix-proxy: What am I doing wrong?
> To: "zabbix-users <at> lists.sourceforge.net"
> <zabbix-users <at> lists.sourceforge.net>
> Message-ID:
> <CALjfk2AwNK5=CHVE-81936wpcR6p+pqKXCS_VErCt1J42YTEzw <at> mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> 2014-01-26 Lucho Lopez <luislopez72 <at> gmail.com>
> >
> > 2014-01-24 J C Lawrence <claw <at> kanga.nu>
> >
> > >
> > > What am I doing wrong in getting an active zabbix proxy to work?
> > >
> > > I have a host which is seemingly happy running the zabbix-server in
> > > AWS. I then have a number of other hosts running zabbix-agent, which
> > > register themselves on build with the zabbix-server by API call using
> > > pyzabbix ala:
> > >
> > > c = zapi.host.create ({
> > > "host": HOST_TAG,
> > > "interfaces": [
> > > {
> > > "type": 1,
> > > "main": 1,
> > > "useip": 1,
> > > "ip": HOST_IP,
> > > "dns": "",
> > > "port": "10050"
> > > },
> > > {
> > > "type": 2,
> > > "main": 1,
> > > "useip": 1,
> > > "ip": HOST_IP,
> > > "dns": "",
> > > "port": "161"
> > > }
> > > ],
> > > "templates": [
> > > {
> > > "templateid": "10050" # Zabbix agent
> > > },
> > > {
> > > "templateid": "10069" # SNMP Linux
> > > },
> > > {
> > > "templateid": "10094" # HTTP
> > > },
> > > {
> > > "templateid": "10095" # HTTPS
> > > },
> > > {
> > > "templateid": "10102" # SSH
> > > },
> > > {
> > > "templateid": "10104" # Ping
> > > },
> > > ],
> > > "groups": [{"groupid": GROUP_ID}],
> > > }
> > > )
> > >
> > > This works just fine. Nice pretty green lights, and graphs and all the
> > > good stuff. Life is good. I mention this to show that the various
> > > configurations seem to be setup correctly for the non proxy case.
> > >
> > > However I'm now getting ready to move all the agent boxes into VPCs, and
> > > I'll have a dozen or more VPCs that I'd like to monitor with a single
> > > external server which collects data from hosts in the VPCs via a proxy.
> > > So before I went whole hog with the VPCs, I deployed a host running
> > > zabbix proxy, and have the agent hosts register themselves with the
> > > zabbix server ala:
> > >
> > > c = zapi.host.create ({
> > > "host": HOST_TAG,
> > > "interfaces": [
> > > {
> > > "type": 1,
> > > "main": 1,
> > > "useip": 1,
> > > "ip": HOST_IP,
> > > "dns": "",
> > > "port": "10050"
> > > },
> > > {
> > > "type": 2,
> > > "main": 1,
> > > "useip": 1,
> > > "ip": HOST_IP,
> > > "dns": "",
> > > "port": "161"
> > > }
> > > ],
> > > "templates": [
> > > {
> > > "templateid": "10050" # Zabbix agent
> > > },
> > > {
> > > "templateid": "10069" # SNMP Linux
> > > },
> > > {
> > > "templateid": "10094" # HTTP
> > > },
> > > {
> > > "templateid": "10095" # HTTPS
> > > },
> > > {
> > > "templateid": "10102" # SSH
> > > },
> > > {
> > > "templateid": "10104" # Ping
> > > },
> > > ],
> > > "groups": [{"groupid": GROUP_ID}],
> > > "proxy_hostid": PROXY_ID, # <======== This is the only change
> > > }
> > > )
> > >
> > > The ID used for the proxy_hostid is taken from the Zabbix database as
> > > the ID of the proxy created under Administration/DM. The Zabbix proxy
> > > is configured as an active proxy. And this...almost works. Well,
> > > actually it doesn't work at all. No monitoring data gets through. Why?
> > >
> >
> > Are you sure that your "PROXY_ID" is the correct "proxy_hostid"?
> >
> > If EVERY host registered in zabbix server "ala" has its own "hostid",
> then the zabbix proxy has its own "hostid" too. Therefore, I think you are
> using the proxy's id to fill the proxy's HOSTID field...
> >
> > Please don't offense, I don't speak english and I'm trying to explain my
> idea :)
>
> I found this... the proxy_hostid must be a string.
> https://www.zabbix.com/documentation/2.2/manual/api/reference/host/object#host
>
> > --
> > Luis from Uruguay <Lucho>
> >
> > >
> > > The hosts are registered with the Zabbix server just fine and show as
> > > being proxied by the right proxy host. The individual proxies report
> > > under Administration/DM as frequently sending information in the zabbix
> > > UI. But, there's no data and all the proxied hosts alert with all their
> > > monitors failing. There's no contact with the zabbix agent on the
> > > target hosts, nor SNMP, nor ICMP, etc.
> > >
> > > The zabbix server logs show:
> > >
> > > 1249:20140124:033726.303 cannot send list of active checks to
> > > [10.239.54.86]: host [prodBETA-mon-1] not found
> > > 1249:20140124:033733.249 cannot send list of active checks to
> > > [10.139.61.196]: host [prodBETA-lb-1] not found
> > > 1249:20140124:033738.341 cannot send list of active checks to
> > > [10.211.151.240]: host [prodBETA-web-2] not found
> > > 1249:20140124:033753.177 cannot send list of active checks to
> > > [10.239.142.80]: host [prodBETA-web-1] not found
> > >
> > > The zabbix proxy logs show:
> > >
> > > 16921:20140124:034025.473 cannot send list of active checks to
> > > [10.239.54.86]: host [prodBETA-mon-1] not found
> > > 16921:20140124:034033.473 cannot send list of active checks to
> > > [10.139.61.196]: host [prodBETA-lb-1] not found
> > > 16921:20140124:034037.165 cannot send list of active checks to
> > > [10.211.151.240]: host [prodBETA-web-2] not found
> > > 16921:20140124:034052.956 cannot send list of active checks to
> > > [10.239.142.80]: host [prodBETA-web-1] not found
> > >
> > > The zabbix agent logs show:
> > >
> > > 16091:20140124:034025.441 No active checks on server: host
> > > [prodBETA-mon-1] not found
> > > 16093:20140124:034025.473 No active checks on server: host
> > > [prodBETA-mon-1] not found
> > > 16092:20140124:034126.434 No active checks on server: host
> > > [prodBETA-mon-1] not found
> > > 16091:20140124:034225.452 No active checks on server: host
> > > [prodBETA-mon-1] not found
> > >
> > > DNS for those names above (eg prodBETA-web-1) is _NOT_ setup, but all
> > > monitoring is configured in terms of raw IP addresses, not DNS. Yes, the
> > > "name" of the proxy in Administration/DM is the same as the value of
> > > Hostname in zabbix_proxy.conf. I checked, and all the names line up
> > > perfectly. In addition the IP address of the proxy is listed in the
> > > values of Server and ServerActive in the agent config. Ports 80 (HTTP),
> > > 443 (HTTPS), 162 (SNMP), 10050 (Zabbix), 10051 (Zabbix), ICMP echo and
> > > request, and port 161 UDP (snmptrap) are open among the zabbix server,
> > > proxy and agent hosts -- and yet they all alert as failing.
> > >
> > > BTW this is all with Zabbix 2.2 from the Ubuntu packages.
> > >
> > > So, what am I missing?
> > >
> > > -- JCL
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>
> ------------------------------
>
> _______________________________________________
> Zabbix-users mailing list
> Zabbix-users <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/zabbix-users
>
>
> End of Zabbix-users Digest, Vol 69, Issue 5
> *******************************************
>

Upcoming Events:

Puppet Fundamentals Training | http://www.open-future.be/puppet-fundamentals-training-4-till-6th-february

Puppet Introduction Course | http://www.open-future.be/puppet-introduction-course-7th-february

Zabbix Certified Training | http://www.open-future.be/zabbix-certified-training-10-till-12th-february

Zabbix for Large Environments Training | http://www.open-future.be/zabbix-large-environments-training-13-till-14th-february

Subscribe to our newsletter: http://eepurl.com/BUG8H



------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Zabbix-users mailing list
Zabbix-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zabbix-users

------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Zabbix-users mailing list
Zabbix-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zabbix-users

Gmane