Jump to content
  • 0

Help With This Error !i Will Pay !


Question

Posted (edited)

post-130967-0-96448900-1406833715_thumb.pngpost-130967-0-68871400-1406833735_thumb.pngpost-130967-0-87109900-1406833747_thumb.pngI have this problem ,and started when i open the server ,i had it online for few months and i didn t had this problem ! IM RUNNING with protection OFF now if i activate it in few minutes server will be stuck........ if i let like this the errors will start in 6-7 hours....

 

 

Edited by Evo Owner

Recommended Posts

  • 0
Posted

It seems you use big queries which haven't enough time to be processed, reaching the default transactions maximum.

 

You can up the default value innodb_lock_wait_timeout on your mySQL server, but it's only a temporary fix. You will normally always end with that issue, no matter how big is the number, if I'm correct. The solution ? Find and fix the query which deadlocks your server.

  • 0
Posted

It seems you use big queries which haven't enough time to be processed, reaching the default transactions maximum.

 

You can up the default value innodb_lock_wait_timeout on your mySQL server, but it's only a temporary fix. You will normally always end with that issue, no matter how big is the number, if I'm correct. The solution ? Find and fix the query which deadlocks your server.

so this is from mysql ....not from my server ?...

  • 0
Posted

do you know how to fix it ?

Tk already told you. Increase the value. And its caused by some crappy code.
  • 0
Posted

As I said, it's one of the query of your GAMESERVER which is the problem. You can temporary fix it editing properties of your mySQL server, but if I'm write about first statement, then it should come back few times later (you will only save some times before it deadlocks again).

 

So the problem is normally the GAMESERVER. Whatever you added as customs, I suggest you to test and read all mySQL queries you added, one is probably particularly heavy to process.

 

PS : I see it's on a restart process. Does the problem occur in regular running state or only during restart ?

  • 0
Posted

As I said, it's one of the query of your GAMESERVER which is the problem. You can temporary fix it editing properties of your mySQL server, but if I'm write about first statement, then it should come back few times later (you will only save some times before it deadlocks again).

 

So the problem is normally the GAMESERVER. Whatever you added as customs, I suggest you to test and read all mySQL queries you added, one is probably particularly heavy to process.

 

PS : I see it's on a restart process. Does the problem occur in regular running state or only during restart ?

yes  also in running state...but i think is fixed ....also i find a config about deadlock in gameserver...

Guest
This topic is now closed to further replies.


×
×
  • Create New...