Last modified: 2009-05-25 04:54:25 UTC
All I get is "Database error" whenever I try to submit a new revision. "A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was: (SQL query hidden) from within function "RecentChange::save". MySQL returned error "1205: Lock wait timeout exceeded; Try restarting transaction (10.0.6.22)"." The page loads for a little while, and then times out (as stated in the error).
Re-opening with an appropriate bug summary and updating components, etc. This is not FIXED.
*** Bug 18868 has been marked as a duplicate of this bug. ***
$ zgrep -c 'timeout exceeded' dberror.log-200905*.gz dberror.log-20090501.gz:153 dberror.log-20090502.gz:63 dberror.log-20090503.gz:76 dberror.log-20090504.gz:112 dberror.log-20090505.gz:85 dberror.log-20090506.gz:114 dberror.log-20090507.gz:110 dberror.log-20090508.gz:261 dberror.log-20090509.gz:107 dberror.log-20090510.gz:130 dberror.log-20090511.gz:125 dberror.log-20090512.gz:112 dberror.log-20090513.gz:142 dberror.log-20090514.gz:238 dberror.log-20090515.gz:363 dberror.log-20090516.gz:2210 dberror.log-20090517.gz:4021 dberror.log-20090518.gz:1564 dberror.log-20090519.gz:1500 dberror.log-20090520.gz:3790 dberror.log-20090521.gz:6728 dberror.log-20090522.gz:301 dberror.log-20090523.gz:154 dberror.log-20090524.gz:261 $ grep -c 'timeout exceeded' dberror.log 252 This will happen occasionally, there's not much we can do about that. We've fixed the issue that was causing 2000-6000 errors per day, now we seem to be back down to the normal background. As such, I'm marking this fixed.
For clarification, according to Tim, the issue was the master switch. "db12 was broken."
