Gabriel Torres Posted March 26, 2014 Share Posted March 26, 2014 I see several deadlock errors on IPB's SQL error log. Example: Date: Wed, 29 Jan 2014 20:09:35 +0000 Error: 1213 - Deadlock found when trying to get lock; try restarting transaction IP Address: 108.162.212.90 - /topic/527921-como-abrir-arquivos-xls/ ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- mySQL query error: DELETE FROM skin_cache WHERE cache_type='css' AND cache_set_id=1 AND cache_value_1='ipb_mlist' Table skin_cache is already InnoDB. I don't know how serious this issue is, if I should worry about it, and if there is anything I could do. We run a MySQL 5.6.16 dedicated server with 32 GB of RAM, which is more than enough for our current needs. Link to comment Share on other sites More sharing options...
Taddei Jean-Baptiste Posted March 5, 2016 Share Posted March 5, 2016 Have you tried to tune your MySQL settings ? The defaults settings are not good enough for an heavy community. Link to comment Share on other sites More sharing options...
ASTRAPI Posted March 6, 2016 Share Posted March 6, 2016 You get a deadlock when two transactions are trying to lock two locks at opposite orders. connection 1: locks key(1), locks key(2); connection 2: locks key(2), locks key(1); You should check your queries and fix them but it is a complex task if that's your case. Link to comment Share on other sites More sharing options...
RevengeFNF Posted March 6, 2016 Share Posted March 6, 2016 This topic was from 2 years ago... Link to comment Share on other sites More sharing options...
Taddei Jean-Baptiste Posted March 6, 2016 Share Posted March 6, 2016 @RevengeFNF realised it afterwards... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.