-
Type:
Incident report
-
Resolution: Won't fix
-
Priority:
Critical
-
None
-
Affects Version/s: 2.2.6
-
Environment:Zabbix proxy (10.41.107.86):
[root@tomsk-proxy ~]# uname -a
Linux tomsk-proxy 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/Linux (RHEL 6.4)
Zabbix agent app-er (10.41.107.73):
[tunnel@app-er ~]$ uname -a
Linux app-er 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux (CentOS 6.5)
Zabbix proxy (10.41.107.86): [ root@tomsk-proxy ~]# uname -a Linux tomsk-proxy 2.6.32-358.el6.x86_64 #1 SMP Tue Jan 29 11:47:41 EST 2013 x86_64 x86_64 x86_64 GNU/Linux (RHEL 6.4) Zabbix agent app-er (10.41.107.73): [ tunnel@app-er ~]$ uname -a Linux app-er 2.6.32-431.29.2.el6.x86_64 #1 SMP Tue Sep 9 21:36:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux (CentOS 6.5)
Hello.
I have some server-proxy-agent environment. Zabbix Agent (2.2.6) on server 10.41.107.73 (with Hostname=app-er2 in config file) with some active items configured on zabbix server (2.2.6), connected through zabbix proxy 2.2.6 (tomsk-proxy, 10.41.107.86). But in web-console of Zabbix Server that item's differ from the expected values??. For example, item with key net.tcp.port[127.0.0.1,10050] (active or passive, no matter) have value 0. It's not possible, because port 10050 used by Zabbix Agent itself.
Furthermore, seen that different query results of the same key from the proxy and the agent:
[root@tomsk-proxy ~]# /usr/bin/zabbix_get -s 10.41.107.73 -k net.tcp.port[127.0.0.1,10050] 0 [root@tomsk-proxy ~]# /usr/bin/zabbix_get -s 10.41.107.73 -k net.tcp.port[127.0.0.1,10051] 1
[tunnel@app-er ~]$ zabbix_agentd -c /etc/zabbix/zabbix_agentd.conf -t net.tcp.port[127.0.0.1,10051] net.tcp.port[127.0.0.1,10051] [u|1] [tunnel@app-er ~]$ zabbix_agentd -c /etc/zabbix/zabbix_agentd.conf -t net.tcp.port[127.0.0.1,10050] net.tcp.port[127.0.0.1,10050] [u|1]
How can this be possible? Why is the data from the agent and proxy differs from the expected and obvious?
