Ad Widget

Collapse

Delayed or even blocked activity via Zabbix Proxy

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dl4mea
    Junior Member
    • Dec 2019
    • 1

    #1

    Delayed or even blocked activity via Zabbix Proxy

    Hi all,

    this is my first question to the community, so please excuse if I'm not using correct wording or phrases.

    I do have a large number of ARM based embedded devices that are monitored with Zabbix. I'm monitoring them with the standard OS Linux template, but also some properitary parameters that I can read via JSON and the preprocessing from our own written software.
    About half of the clients is directly accessible from the server, the rest sits behind a firewall. On that firewall we're running Zabbix proxy. After I got used to the delay of configuration changes I can say everything works fine with those clients that are directly reachable.

    My problem is that frequently a connection to a client behind the Zabbix proxy is not established, and after that it looks as if that connection is not restored after a timeout or a retry time.
    2nd I see that changes in queries are not applied to a client behind the zabbix proxy neither after some nor after long time.
    It somehow looks as if only if we start the proxy and it works at the very first moment it will work forever, but will not accept changes or failures???
    Sorry, I cannot describe it better.

    We have done some logging, and it seems that the problem is already between server and proxy.

    Our proxy is the prebuilt docker container and version 4.2
    Zabbix agent on the clients is quite differnt, Mostly some 3.x version, and hard to update since widespread distributed
    Zabbix server is 4.2.6 running on Ubuntu 18.04.3 LTS

    Thanks for any ideas how to get that solved!

    Cheers, Guenter
Working...