Ad Widget

Collapse

ICMP Ping works fine on the Server but builds up queue once moved to proxy!

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • DRXEON
    Junior Member
    • Nov 2019
    • 5
    #1

    ICMP Ping works fine on the Server but builds up queue once moved to proxy!

    Hello Guys,

    Thanks for contributing and your help in advance.
    I have a Zabbix Server has 5k nodes pinging every 30s and the NVPS is 173 everything works fine and smooth.
    I already added the pollers and pingers and minimal db optimization as you see everywhere.
    I have a zabbix proxy with the same specs as my server, the same conf file tuning and db tuning, but when I move like 10 hosts to proxy, it builds up the queue right away!
    As soon as I move the hosts back to server everything goes back to normal! fping works fine on the proxy, hosts are pingable from the proxy box itself, server proxy ports are ok in firewall

    Also another weird thing is I am using zabbix agent on my proxy so that I can monitor the proxy box in Zabbix, I applied the proxy template to it, the number of NVPS (Proxy Performance) graph is exactly the same as the server 173 ! but there is only 10 hosts on the proxy!
    Tags: None
    • DRXEON
      Junior Member
      • Nov 2019
      • 5
      #2
      Guys !!!! looks like it requires me to restart the proxy service every time I add hosts! I now moved 2000 hosts over and every time I move hosts (1000 at a time) I just do systemctl restart zabbix-proxy and it fixed the issue!

      What does it have to do with it ?!?! its weird !

        Comment

        • dimir
          Zabbix developer
          • Apr 2011
          • 1080
          #3
          Proxy does not know of the configuration changes (attach/detach proxy to/from host) you make immediately.

          First thing, server must pick those from the database and does it by default once per minute (CacheUpdateFrequency parameter in zabbix_server.conf) .

          Secondly, if your proxy is passive, by default server would send it updated configuration once per hour (ProxyConfigFrequency parameter in zabbix_server.conf) . Active proxy requests updated configuration from server the same way by default, once per hour (ConfigFrequency parameter in zabbix_proxy.conf).

          So if using defaults it takes up to 1 hour and 1 minute for the proxy to become aware of the changes you make in the Frontend.

          More details:

          https://www.zabbix.com/documentation.../zabbix_server
          https://www.zabbix.com/documentation...g/zabbix_proxy

            Comment

            • DRXEON
              #3.1
              DRXEON commented
              21-11-2019, 08:52
              Editing a comment
              Thank you Dimir,

              I will go and update the intervals then, do you have any suggestions? can I reduce it down to 5s ?

              Also would you believe that so many other people have the same issue and they are wasting time around fping! I could not find the answer you gave to this issue anywhere in google and really appreciate your info!
            • DRXEON
              Junior Member
              • Nov 2019
              • 5
              #4
              Thank you Dimir,

              I will go and update the intervals then, do you have any suggestions? can I reduce it down to 5s ?

              Also would you believe that so many other people have the same issue and they are wasting time around fping! I could not find the answer you gave to this issue anywhere in google and really appreciate your info!

                Comment

                • dimir
                  Zabbix developer
                  • Apr 2011
                  • 1080
                  #5
                  This is related to anything you configure in the Frontend, not specific to icmpping* items (that use fping). It's sad that you haven't found the info, it's documented. I guess this is one reason to consider Zabbix training/support services.
                  As to the limits, it depends on many things: the size of configuration (server/proxy), how important it is to be aware of the changes immediately, etc. Normally I think the defaults are OK. For server, once per minute is fine IMO, for proxy you could reduce to once per 5 minutes, but it depends, it can be lower. 5s however I think is risky. If your proxy configuration is not small (and you mentioned 5k nodes) there's a risk that proxy will be synchronizing it's configuration forever and not much load will be left on doing the real job.
                  One more thing, you can force Zabbix server to reload configuration from the database and force active Agent to request configuration from Zabbix server by using option -R:
                  Code:
                  zabbix_server -Rconfig_cache_reload
zabbix_proxy -Rconfig_cache_reload
                  But you can't force reloading of Passive proxy configuration. More info:
                  https://www.zabbix.com/documentation/current/manual/concepts/server
                  https://www.zabbix.com/documentation/current/manual/concepts/proxy

                    Comment

                    • DRXEON
                      #5.1
                      DRXEON commented
                      21-11-2019, 17:40
                      Editing a comment
                      THANK YOU VERY MUCH for your information

                      I appreciate your support and help.
                    Previous template Next
                    Working...