Last modified: 2014-08-12 12:42:00 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T65818, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63818 - GWtoolset throws database error "1205 Lock wait timeout exceeded"
GWtoolset throws database error "1205 Lock wait timeout exceeded"
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
GWToolset (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: dan
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-11 13:29 UTC by Jean-Fred
Modified: 2014-08-12 12:42 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jean-Fred 2014-04-11 13:29:29 UTC
Tounoki encountered the following error when using the GWToolset on Wikimedia Commons:

----
Erreur de la base de données

Une erreur de requête de base de données s'est produite. Cela peut provenir d'un bogue dans le logiciel.

    Fonction : LinksUpdate::updateLinksTimestamp
    Erreur : 1205 Lock wait timeout exceeded; try restarting transaction (10.64.16.29)
----

Thoughts?
Comment 1 Bawolff (Brian Wolff) 2014-04-11 14:17:07 UTC
Which step did this happen? (I would assume on the upload first ten files for preview)?
Comment 2 dan 2014-04-12 09:59:15 UTC
is a stack trace available?
GWToolset doesn’t call LinksUpdate::updateLinksTimestamp directly. 

searching through the core code it looks like this is called when a deferred 
update is run, so is this:

• a deferred update issue?
• a coincidental db issue at the moment this use of GWToolset ran?

LinksUpdate::updateLinksTimestamp
LinksUpdate::doIncrementalUpdate
LinksUpdate::doUpdate

also an instance of LinksUpdate seems to be created and a doUpdate run for:
ParserOutput::getSecondaryDataUpdates
WikiPage::doCascadeProtectionUpdates
Comment 3 tounoki 2014-04-12 21:59:16 UTC
(In reply to Bawolff (Brian Wolff) from comment #1)
> Which step did this happen? (I would assume on the upload first ten files
> for preview)?

yes, i confirm
Comment 4 tounoki 2014-04-12 22:03:17 UTC
Using the GWtoolset, I experiment different kind of timeout error.

As I can remember, 3 kinds of timeout happened.
- the first is described below
- the second is a blank screen with a black line. Error 504 [...] something gateway [...] timeout
- the last kind is the upload icon that turn again and again.

I will try to keep screenshot next time I try to use the tool.
Comment 5 Bawolff (Brian Wolff) 2014-04-12 22:40:06 UTC
How often would you say these various types of errors occur?

The second (and possibly third) may be correlated with how big the files uploaded during the preview stage are.
Comment 6 dan 2014-04-13 02:57:48 UTC
• is this related to bug 63864?
• if related, this may have to do with the mediafile file size.
• fyi: the default preview should only upload the first 3 items
  in the metadata file.
Comment 7 Bawolff (Brian Wolff) 2014-04-13 04:18:02 UTC
(In reply to dan from comment #6)
> • is this related to bug 63864?
at first glance i would say no, or at least not enough evidence to draw a conclusion. (Unless the job also is failing for a db lock timeout. Alas i dont have access to logs so have no idea why the jobs didnt go).

> • if related, this may have to do with the mediafile file size.

Bigger files do have a tendency to expose bugs that are sometimes not shown on small files

> • fyi: the default preview should only upload the first 3 items
>   in the metadata file.
Comment 8 tounoki 2014-04-13 11:24:43 UTC
(In reply to dan from comment #6)
> • is this related to bug 63864?

When I don't have the bug 63818 (timeout pb) and when I obtain finally the 4th (and last) step of the upload process, I get the bug 63864.

> • if related, this may have to do with the mediafile file size.
> • fyi: the default preview should only upload the first 3 items
>   in the metadata file.
Comment 9 tounoki 2014-04-13 11:30:33 UTC
(In reply to Bawolff (Brian Wolff) from comment #5)
> How often would you say these various types of errors occur?
> 

4 or 5 times before I obtain the bug 63864.
And I'm patient.

> The second (and possibly third) may be correlated with how big the files
> uploaded during the preview stage are.

I did'nt think, there could be pbs with the size of the files.
So I made a lot of tests for the datamapping and remote upload with jpg a. But I did'nt with the tif files on the beta cluster :\ Sorry
Comment 10 tounoki 2014-04-15 07:47:46 UTC
A new test this morning :

For the logs, the same bug at about 9:20 am (Paris)
    Fonction : LinksUpdate::incrTableUpdate
    Erreur : 1205 Lock wait timeout exceeded; try restarting transaction (10.64.16.29)

Reload the page a second time : same result.

And at the third time, I complete the step 3, and obtain previsualisation of 3 pictures (2 of this was uploaded before)

No problem to go to the step 4 but nothing happened like described in the bug 63864
Comment 11 dan 2014-06-13 17:29:38 UTC
has this patch resolved the issue https://gerrit.wikimedia.org/r/127839 ?
Comment 12 dan 2014-06-26 07:46:01 UTC
the patch has been deployed to production. are you okay with closing this bug now?
Comment 13 dan 2014-08-11 07:17:07 UTC
assuming that this is no longer an issue with https://gerrit.wikimedia.org/r/#/c/127839/ applied ...
Comment 14 Jean-Fred 2014-08-12 12:42:00 UTC
(In reply to dan from comment #13)
> assuming that this is no longer an issue with
> https://gerrit.wikimedia.org/r/#/c/127839/ applied ...

Thanks Dan. I could not test if the problem is still there, but no worries − we'll reopen if needed ;-)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links