[ZBX-4271] Memory leaks when an deadlock Created: 2011 Oct 25  Updated: 2017 May 30  Resolved: 2011 Oct 25

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: 1.8.9, 1.9.7 (beta)
Fix Version/s: 1.8.9, 1.9.7 (beta)

Type: Incident report Priority: Blocker
Reporter: Alexey Pustovalov Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Gentoo, rev22632, MySQL 5.5 Percona, zabbix server, web and database installed on separate hosts


Issue Links:
Duplicate

 Description   

when zabbix process update triggers table "update triggers set error='Zabbix server was restarted...'"
if query recieves deadlock zabbix-server begins eat memory! Every deadlock eating 5-10MB.



 Comments   
Comment by Aleksandrs Saveljevs [ 2011 Oct 25 ]

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-4271 .

The bug was introduced in pre-1.8.9 under ZBX-4158, so this is a blocker for 1.8.9rc1, which was planned to be released tomorrow (http://twitter.com/#!/zabbix/status/124100757766160384). Thanks, Alexey!

Comment by dimir [ 2011 Oct 25 ]

Successfully tested! Please review my small changes in r22642

Comment by Alexey Pustovalov [ 2011 Oct 25 ]

not working patch for me... i have these errors in logs after applying patch rev22641:
nd hostid between 000000000000000 and 099999999999999]
11509:20111025:175205.107 [Z3005] query failed: [2006] MySQL server has gone away [select i.itemid,i.key_,h.host,i.type,i.history,i****]
11587:20111025:175205.157 Sending configuration data to proxy '**-proxy'. Datalen 496212
11634:20111025:175206.923 [Z3005] query failed: [2006] MySQL server has gone away [begin;]
11650:20111025:175206.941 [Z3005] query failed: [2006] MySQL server has gone away [begin;]

Comment by Aleksandrs Saveljevs [ 2011 Oct 25 ]

Fixed in pre-1.8.9 in r22649.

Comment by Aleksandrs Saveljevs [ 2011 Oct 25 ]

Alexey, the patch does not affect MySQL connectivity in any way. If you still have those errors with the latest trunk (the memory leak fix has already been merged), please provide a longer excerpt from the log file.

Comment by Alexey Pustovalov [ 2011 Oct 25 ]

Sorry, Aleksandrs, my mistake... I found bug in MySQL config file:) Patch working excellent

Generated at Fri Apr 19 01:03:54 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.