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

eZ debug

Timing:	Jan 31 2025 03:41:47
Script start
Timing:	Jan 31 2025 03:41:47
Module start 'layout'
Timing:	Jan 31 2025 03:41:47
Module start 'content'
Timing:	Jan 31 2025 03:41:47
Module end 'content'
Timing:	Jan 31 2025 03:41:47
Script end

Main resources:

Total runtime	0.0198 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0043	588.0078	151.1953
Module start 'layout'	0.0043	0.0032	739.2031	220.6563
Module start 'content'	0.0075	0.0109	959.8594	997.6641
Module end 'content'	0.0184	0.0014	1,957.5234	29.9922
Script end	0.0197		1,987.5156

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	12.0911	14	0.0002
Check MTime	0.0010	5.1912	14	0.0001
Mysql Total
Database connection	0.0006	3.1326	1	0.0006
Mysqli_queries	0.0020	10.3148	3	0.0007
Looping result	0.0000	0.0507	1	0.0000
Template Total	0.0010	5.3	1	0.0010
Template load	0.0008	4.1703	1	0.0008
Template processing	0.0002	1.1041	1	0.0002
Override
Cache load	0.0006	2.9045	1	0.0006
General
dbfile	0.0008	4.1305	8	0.0001
String conversion	0.0000	0.0314	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs