Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-9084

Zabbix Proxy allocates more memory that necessary when it starts

XMLWordPrintable

    • Sprint 58 (Nov 2019), Sprint 59 (Dec 2019)
    • 0.5

      When zabbix_proxy starts without database and create it, that's ok. It only allocate the memory to procced with the collect data.

      On the other hand, if database exists and have, for example, 100M, zabbix_proxy allocate about 100M for each process. In a host with 2GB of RAM, with, for example, 40 pollers, the zabbix_proxy is dead by "out of memory" killer because it has allocated a lot of memory.

      If database is removed and zabbix_proxy is restarted, the daemon starts normally and allocate much less memory. A new restart on the process cause out of memory again.

        1. last_ps_with_database.log
          11 kB
        2. last_ps_without_database.log
          27 kB
        3. smap.txt
          164 kB
        4. smaps_vmware.txt
          111 kB
        5. valgrind_proxy_new.log
          291 kB
        6. valgrind_proxy_with.log
          825 kB
        7. zabbix_proxy_configure_options_james_cook
          0.3 kB
        8. zabbix_proxy_debug_log_james_cook.txt
          40 kB
        9. zabbix_proxy_process_listing_james_cook
          32 kB
        10. zabbix_proxy_smaps_james_cook.tar.gz
          1.43 MB
        11. zabbix_proxy.log
          6 kB
        12. Zabbix Proxy Cache Utilisation James Cook.JPG
          Zabbix Proxy Cache Utilisation James Cook.JPG
          127 kB
        13. ZBX-9084-test.patch
          1 kB

            vso Vladislavs Sokurenko
            alisson Alisson Ramos de Oliveira
            Team A
            Votes:
            11 Vote for this issue
            Watchers:
            23 Start watching this issue

              Created:
              Updated:
              Resolved: