Forum

Error during update
 
Notifications
Retirer tout

Error during update

2 Posts
2 Utilisateurs
0 Reactions
3,164 Vu
Martin
(@el-wallos)
Posts: 220
Active Member
Début du sujet
 
[#2861]

Hi

I had a problem on ProjeQtOr, it seems to be a wait lock at DB level.

I attach the log

2016-01-06 14:29:55.836 ** ERROR ** Exception-[HY000] SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction
2016-01-06 14:29:55.837 ** ERROR ** For query : update planningelement set assignedWork='0.5' , leftWork='0.5' , plannedWork='0.5' where id=802
2016-01-06 14:29:55.837 ** ERROR ** Strack trace :
2016-01-06 14:29:55.837 ** ERROR ** #0 Sql->query called at [/var/www/html/projeqtor/model/persistence/SqlElement.php:893]
2016-01-06 14:29:55.837 ** ERROR ** #1 SqlElement->updateSqlElement called at [/var/www/html/projeqtor/model/persistence/SqlElement.php:559]
2016-01-06 14:29:55.837 ** ERROR ** #2 SqlElement->saveSqlElement called at [/var/www/html/projeqtor/model/persistence/SqlElement.php:454]
2016-01-06 14:29:55.837 ** ERROR ** #3 SqlElement->save called at [/var/www/html/projeqtor/model/PlanningElement.php:381]
2016-01-06 14:29:55.837 ** ERROR ** #4 PlanningElement->save called at [/var/www/html/projeqtor/model/ActivityPlanningElementMain.php:176]
2016-01-06 14:29:55.837 ** ERROR ** #5 ActivityPlanningElementMain->save called at [/var/www/html/projeqtor/model/PlanningElement.php:712]
2016-01-06 14:29:55.837 ** ERROR ** #6 PlanningElement->updateSynthesisObj called at [/var/www/html/projeqtor/model/PlanningElement.php:737]
2016-01-06 14:29:55.838 ** ERROR ** #7 PlanningElement->updateSynthesis called at [/var/www/html/projeqtor/model/Assignment.php:181]
2016-01-06 14:29:55.838 ** ERROR ** #8 Assignment->save called at [/var/www/html/projeqtor/tool/saveAssignment.php:139]
2016-01-06 14:31:11.912 ** ERROR ** Exception-[HY000] SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction
2016-01-06 14:31:11.912 ** ERROR ** For query : insert into planningelement ( idProject , refType , refId , refName , validatedWork , wbs , priority , idPlanningMode , wbsSortable , topId , topRefType , topRefId , idle , elementary , done , cancelled , validatedCalculated ) values ('163', 'Activity', '437', 'Upgrade VM Hardware « Cluster Lame Production PAREL » (22 VM)', '0.5', '21.7.3.6', '500', '1', '021.007.003.006', '753', 'Project', '163', '0', '1', '0', '0', '0')
2016-01-06 14:31:11.912 ** ERROR ** Strack trace :
2016-01-06 14:31:11.912 ** ERROR ** #0 Sql->query called at [/var/www/html/projeqtor/model/persistence/SqlElement.php:752]
2016-01-06 14:31:11.912 ** ERROR ** #1 SqlElement->insertSqlElement called at [/var/www/html/projeqtor/model/persistence/SqlElement.php:565]
2016-01-06 14:31:11.912 ** ERROR ** #2 SqlElement->saveSqlElement called at [/var/www/html/projeqtor/model/persistence/SqlElement.php:454]
2016-01-06 14:31:11.912 ** ERROR ** #3 SqlElement->save called at [/var/www/html/projeqtor/model/PlanningElement.php:381]
2016-01-06 14:31:11.912 ** ERROR ** #4 PlanningElement->save called at [/var/www/html/projeqtor/model/ActivityPlanningElementMain.php:176]
2016-01-06 14:31:11.912 ** ERROR ** #5 ActivityPlanningElementMain->save called at [/var/www/html/projeqtor/model/persistence/SqlElement.php:972]
2016-01-06 14:31:11.913 ** ERROR ** #6 SqlElement->saveDependantObjects called at [/var/www/html/projeqtor/model/persistence/SqlElement.php:765]
2016-01-06 14:31:11.913 ** ERROR ** #7 SqlElement->insertSqlElement called at [/var/www/html/projeqtor/model/persistence/SqlElement.php:565]
2016-01-06 14:31:11.913 ** ERROR ** #8 SqlElement->saveSqlElement called at [/var/www/html/projeqtor/model/persistence/SqlElement.php:454]
2016-01-06 14:31:11.913 ** ERROR ** #9 SqlElement->save called at [/var/www/html/projeqtor/model/ActivityMain.php:280]
2016-01-06 14:31:11.913 ** ERROR ** #10 ActivityMain->save called at [/var/www/html/projeqtor/tool/saveObject.php:85]

Is it possible to avoid this behavior?


 
Posté : 6 Jan PM 19:011
(@babynus)
Posts: 14952
Membre Admin
 

http://stackoverflow.com/questions/6000336/how-to-debug-lock-wait-timeout-exceeded
=> You should consider increasing the lock wait timeout value for InnoDB by setting the innodb_lock_wait_timeout, default is 50 sec


 
Posté : 7 Jan PM 12:011
Share:
Retour en haut