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

Huge memory leak in zabbix_server's housekeeper

    XMLWordPrintable

    Details

    • Type: Incident report
    • Status: Closed
    • Priority: Major
    • Resolution: Won't fix
    • Affects Version/s: 2.2.2, 2.2.3
    • Fix Version/s: None
    • Component/s: Server (S)
    • Labels:
    • Environment:
      CentOS 6.5, KVM, 4GB RAM, 2 cores, kernel: 2.6.32-431.17.1.el6.x86_64 #1 SMP Wed May 7 23:32:49 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

      Description

      I'm experiencing a strange memory leak zabbix running from packages installed from http://repo.zabbix.com/zabbix/2.2/rhel/6/ . Right after start of the zabbix-server service, one of the processes – housekeeper – starts taking memory at a decent pace till OOM kicks in. It takes ~2mins to consume all the memory, all of the checks in zabbix have been stopped.

      Output from top:

       4457 zabbix    20   0 2175m 2.0g  616 S  3.0 52.6   0:04.29 zabbix_server                                                                 
      

      Process stats:

      [[email protected] ~]# ps axwww|grep 4457
       4457 ?        S      0:05 zabbix_server: housekeeper [removing old history and trends]
      

      Zabbix mysql table is pretty small:

      [[email protected] ~]# du -hs /var/lib/mysql/*
      1011M	/var/lib/mysql/ibdata1
      5.0M	/var/lib/mysql/ib_logfile0
      5.0M	/var/lib/mysql/ib_logfile1
      988K	/var/lib/mysql/mysql
      0	/var/lib/mysql/mysql.sock
      4.0K	/var/lib/mysql/test
      1.4M	/var/lib/mysql/zabbix
      

      Not sure how to debug this issue, any hints?

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            ilja Ilja Livenson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: