Transaction errors

Next topic

Author	Message
David Eriksson	Friday 26 August 2005 12:55:56 am Searching the forums, most people seems to have gotten these during installation. But for me, they just started to crop up everywhere a few days ago. Looking through the logs: [ Aug 26 2005 09:41:07 ] [129.16.159.174] Query error: Lock wait timeout exceeded; try restarting transaction. Query: DELETE FROM eznode_assignment WHERE contentobject_id=367 AND contentobject_version=1 [ Aug 26 2005 09:41:07 ] [129.16.159.174] Transaction in progress failed due to DB error, transaction was rollbacked. Transaction ID is TRANSID-d3c329b901a6ef0716ecf6c020e8fc29. /David
David Eriksson	Friday 26 August 2005 2:02:41 am Ok, rebooting mysql seem to have fixed the problem. We're thinking it may have to do with PreviewCache. We turned it on last week, and we believe users might have pressed publish buttons multiple times, which might have left stuff. Also, all cache doesn't seem to have time to generate in the 60 seconds we have set as timeout. So we're turning that off again now, to see if that will prevent further mishappenings. Just a tip to eventual others with the same problems. :) /David

Author

Message

Friday 26 August 2005 12:55:56 am

Searching the forums, most people seems to have gotten these during installation. But for me, they just started to crop up everywhere a few days ago.

Looking through the logs:

[ Aug 26 2005 09:41:07 ] [129.16.159.174] Query error: Lock wait timeout exceeded; try restarting transaction. Query: DELETE FROM eznode_assignment
                         WHERE contentobject_id=367 AND contentobject_version=1
[ Aug 26 2005 09:41:07 ] [129.16.159.174] Transaction in progress failed due to DB error, transaction was rollbacked. Transaction ID is TRANSID-d3c329b901a6ef0716ecf6c020e8fc29.

/David

David Eriksson

Friday 26 August 2005 2:02:41 am

Ok, rebooting mysql seem to have fixed the problem.

We're thinking it may have to do with PreviewCache. We turned it on last week, and we believe users might have pressed publish buttons multiple times, which might have left stuff. Also, all cache doesn't seem to have time to generate in the 60 seconds we have set as timeout. So we're turning that off again now, to see if that will prevent further mishappenings.

Just a tip to eventual others with the same problems. :)

/David