keep getting Database error in vBulletin 5.0.5 every day !!

[alnadabi]

Hi there,

recently, I and after upgrading from 5.0.4 to 5.0.5 ... I am receiving the following email almost every day :


=================================================================

[Showing truncated query, original length: 60656]
[First 500 chars]
Invalid SQL:
/** saveDbCache */REPLACE INTO mjbb_cacheevent (cacheid, event) values
('vB_ChannelTreeRaw_0','vB_ ChannelStructure_chg'),
('vB_ChannelTreeRaw_0','perms_changed'),
('vB_ChannelTreeRaw_0','userPerms_0'),
('node_7_lvl1data','nodeChg_7'),
('node_8_lvl1data','nodeChg_8'),
('node_10_lvl1data','nodeChg_10'),
('node_12_lvl1data','nodeChg_12'),
('node_91_lvl1data','nodeChg_91'),
('node_92_lvl1data','nodeChg_92'),
('node_102_lvl1data','nodeChg_102'),
('node_1249966_lvl1data','nodeChg_124996
[Last 500 chars]
g_1336272'),
('node_1336283_lvl1data','nodeChg_1336283'),
('node_1336685_lvl1data','nodeChg_1336685'),
('node_1338127_lvl1data','nodeChg_1338127'),
('node_1339104_lvl1data','nodeChg_1339104'),
('node_1339202_lvl1data','nodeChg_1339202'),
('node_1339315_lvl1data','nodeChg_1339315'),
('node_1339792_lvl1data','nodeChg_1339792'),
('node_1340353_lvl1data','nodeChg_1340353'),
('vB_ChTreeWithLast','vB_ChannelStructure_chg'),
('vBPage_d90d146d42364d6ef84d6834a9038137_1',''),
('vbPre_channel41.26.2','');

MySQL Error : Deadlock found when trying to get lock; try restarting transaction
Error Number : 1213
Request Date : Wednesday, October 23rd 2013 @ 07:11:45 AM
Error Date : Wednesday, October 23rd 2013 @ 07:11:46 AM
Script : http:///forum
Referrer :
IP Address : 180.76.5.21
Username : Guest
Classname : vB_Database_MySQL
MySQL Version :


=================================================================



any idea what is the reason of this email ?? how to solve it ??



Thanks
AlNadabi

[alnadabi]

http://stackoverflow.com/questions/2596005/working-around-mysql-error-deadlock-found-when-trying-to-get-lock-try-restarti

I have seen the above topic , and they said that to solve this is we need to :

add below line to my.cnf file innodb_locks_unsafe_for_binlog = 1

I need more recommendation from you guys

Thanks

[Wayne Luke]

This is a known issue from the switch to transactions in 5.0.4. It is something the developers are working on fixing.

You can try the above line to reduce the errors.