zabbix-tooling / k8s-zabbix

Kubernetes autodiscovery monitoring
GNU General Public License v2.0
18 stars 9 forks source link

Zabbix Sender - Name does not resolve or Host is unreachable #10

Closed aribalduzzi closed 2 years ago

aribalduzzi commented 3 years ago

When I configured the Zabbix Server with port I get the "Name does not resolve", then I tried without port and the error changed to "Host is unreachable". The Zabbix server is reacheable from my pod.

zabbix_server = 'xxx.xxx.xxx.xxx:YYYYY':

2021-07-27 03:36:18,091 - Thread-2 : {/app/k8s_zabbix_base/daemon_thread.py:484} : ERROR : CheckKubernetesDaemon - [Errno -2] Name does not resolve 2021-07-27 03:36:18,091 - Thread-2 : {/app/k8s_zabbix_base/daemon_thread.py:470} : ERROR : CheckKubernetesDaemon - failed to send heartbeat to zabbix

zabbix_server = 'xxx.xxx.xxx.xxx': (it's OK to fail because the zabbix server listens in a particular port.

2021-07-28 17:36:52,280 - Thread-22 : {/app/k8s_zabbix_base/daemon_thread.py:484} : ERROR : CheckKubernetesDaemon - [Errno 113] Host is unreachable 2021-07-28 17:36:52,280 - Thread-22 : {/app/k8s_zabbix_base/daemon_thread.py:541} : ERROR : CheckKubernetesDaemon - failed to sent 1 zabbix items, processed 0 items [deployments: metrics]

Is OK to configure the zabbix server env with port in that way?

Thanks in advance!!

aribalduzzi commented 3 years ago

I seems to use 10051 as default Zabbix port. Is there some way to configure it with env?

aribalduzzi commented 3 years ago

Log example:

2021-07-28 20:55:20,220 - Thread-2 : {/usr/local/lib/python3.7/site-packages/pyzabbix/sender.py:388} : DEBUG : pyzabbix.sender - Sending data to ('10.1.10.10:45000', 10051)

I configured the env value with ip and port, but it not recognize the parameter.

I tried to use an ENV called ZABBIX_PORT (used at sender.py), but it never passed that parameter to that script.

scoopex commented 2 years ago

This is obsolete or outdated.