New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
General error: 1205 Lock wait timeout exceeded -> system check diagnostic for innodb_lock_wait_timeout #10125
Comments
Can you show us the output of What's the value of your There's a similar issue here #8010 but it was not tackled. |
|
It will be interesting to see the output of processlist. Feel free to email us to hello at piwik.org in case it is a problem to paste it here. Just leave a comment here so we can check the spam folder if needed. Are you using regular JavaScript tracking method? Which MySQL version are you using? |
My MYSQL version is 5.5.19 and yes i am using the regular JavaScript tracking method. |
Thx for letting us know. The output of process list would be really helpful to investigate further. |
ShowProcess.txt |
Thx for this! Can you check whether the table is using InnoDB engine? |
SHOWTableStatus.xlsx |
Thank you, that looks all good. I would recommend you have eg a read here http://stackoverflow.com/questions/13234290/lots-of-query-end-states-in-mysql-all-connections-used-in-a-matter-of-minutes This seems more like a server issue to me than an issue in Piwik. I would maybe also recommend to try asking the same in our forums https://forum.piwik.org/ as some more people will see it there and they maybe had similar problems. |
If you get this error while importing server logs, reducing the |
Should not be a Piwik issue |
Hi team,
We are getting the below mentioned error on regular basis :
[error] [client 172.28.14.138] Error in Piwik (tracker): Error query: SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction In query:
When this happens, it impacts the application which the Piwik is monitoring and business of our clients gets affected. Our application fails to loads as Piwik continuously tries to throw this error. We have to restart Piwik and our applications to get it back up.
We are using piwik 2.16.0 version. Our application send around 25,000 requests to Piwik on a daily basis and we have around 200gb of space alloted to Piwik Database.
Could you please suggest why this issue occurs and if this known issue with piwik could you let me know the version in which this would be fixed.
The text was updated successfully, but these errors were encountered: