Ad Widget

Collapse

zabbix 2.0.1 serious memory leak

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ghillan
    Junior Member
    • Jan 2012
    • 20

    #1

    zabbix 2.0.1 serious memory leak

    I'm using zabbix 2.0 since the realease and also updated to the 2.0.1. AFor some time it happened that zabbix just stopped working without any reason, and i had to reboot it. after a while i decided to trace the zabbix server memory usage and thats what i discovered:

    During the tiem zabbix simply start to eat all available memomy ultil there is simply not enough memory left for mysql to work ( causing mysql crash). In attachment a weekly memory usage. As you can see the available momory drop down. Everytime the available memory goes up its because i stopped and restarted zabbix_server.

    My zabbix its on VM and i dont have swap space. If left zabbix working without periodical reboot it will eat all the memory until there is no memory for mysql and it cause DB to crash.

    This server have no other stuff running except zabbix and mysql, and anyway the peak of available memory happened then i stop and start the zabbix server. Its a while im monitorig this behaviour and did several tests to be sure it was the zabbix server reboot that caused the abailable memory coming back.

    For now, my workaround its to reboot it manually roughly every 2 weeks ( had to increase available memory from 4GB to 8GB just to be able to make zabbix last longer, but still will eat all the memory ).
    Attached Files
  • dougbee
    Member
    • Apr 2011
    • 68

    #2
    Perhaps related to this?

    Comment

    • ghillan
      Junior Member
      • Jan 2012
      • 20

      #3
      Originally posted by dougbee
      Tnx, for pointing me this. Its nice that the issue will be solved in the next incoming release. Haven't updated my 2.0.1 to the latest one ( 2.0.2) because there was no sign of this "fix" in che changelog.

      Comment

      • rrm74001
        Junior Member
        • Nov 2012
        • 9

        #4
        Almost a year later, and this is the exact problem I am having in version 2.0.8. Is this a general known issue?

        Comment

        Working...