EOSERV Bug Tracker > Bug #352: Lock wait timeout exceeded in timed save - server crash

Bug #352: Lock wait timeout exceeded in timed save - server crash

Lock wait timeout exceeded in timed save - server crash
ID #352
Submitter Sausage
Product EOSERV
Severity Critical
Status CLOSED, FIXED
Submitted 3rd Aug 2015
Updated 8th Apr 2016
Related SVN Revisions
Rev# Date Description
r522 08 Apr 2016 08:05:58 UTC Try mitigate a crash in the case of lock wait timeout errors (bug #352)
Sausage Submitter
Developer
1 year, 47 weeks ago

MySQL may fail a statement in a transaction with a "Lock wait timeout exceeded" error. This currently causes EOSERV to crash. The crash should be mitigated and preferably code added to rollback and re-attempt a transaction in response to this error.

The final lines in the server log were:

[ERR] Timer callback caused an exception

[ERR] Database_QueryFailed: Lock wait timeout exceeded; try restarting transaction

  • Error in `./eoserv': double free or corruption (fasttop): 0x09e60358 ***

Comments

Apollo 1 year, 46 weeks ago

By no means a fix, but a work around should anyone else be experiencing this would be to either remove account updating features from WebCP or set the timed save feature to 30-50 seconds. These are not optimal but might prevent a crash should you encounter this bug prior to an official fix.

Sausage Submitter
Developer
1 year, 11 weeks ago

Added some code in r522 which stops this particular problem in practice, but the double free crash caused by the query failure probably needs more investigation.

Updated Status to CLOSED, FIXED

Add Comment

Please don't post unless you have something relevant to the bug to say.
Do not comment to say "thanks" or "fix this please".

Please log in to add comments. EOSERV Bug Tracker > Bug #352: Lock wait timeout exceeded in timed save - server crash