Last modified: 2014-11-20 13:36:20 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 T45967, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 43967 - Internal error: Could not determine if the copy succeeded.
Internal error: Could not determine if the copy succeeded.
Status: NEW
Product: MediaWiki
Classification: Unclassified
Uploading (Other open bugs)
1.22.0
All All
: High major with 1 vote (vote)
: ---
Assigned To: Gilles Dubuc
: hhvm
: 48647 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-14 20:29 UTC by Raimond Spekking
Modified: 2014-11-20 13:36 UTC (History)
13 users (show)

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


Attachments

Description Raimond Spekking 2013-01-14 20:29:19 UTC
Since a few days I get reports, incl. from myself as Wikimedia Commons uploader, like "Internal error: Could not determine if the copy succeeded." after click to submit the descriptions.

Clicking on "Retry failed uploads" I get 
"[api-error-internal_api_error_UploadStashFileNotFoundException]"

For my uploads the file uploads were completed anyway but I hear about half done uploads (file page without file).
Comment 2 Mark Holmquist 2013-01-18 20:20:13 UTC
Reproduced on James_F's laptop, but the files actually completed.
Comment 3 Nischay Nahata 2013-03-02 20:17:02 UTC
Not sure if this is a dupe of https://bugzilla.wikimedia.org/show_bug.cgi?id=36587
Comment 4 Nischay Nahata 2013-05-19 07:02:39 UTC
Is this fixed now? Or are there any steps to reproduce this?
Comment 5 Nischay Nahata 2013-06-13 13:41:37 UTC
*** Bug 48647 has been marked as a duplicate of this bug. ***
Comment 6 Bawolff (Brian Wolff) 2013-08-22 22:19:43 UTC
looks like chunked upload issue
Comment 7 Nemo 2013-10-11 08:51:01 UTC
Recent report of the problem (with not much more information and in Russian, though): https://commons.wikimedia.org/w/index.php?title=Commons:Upload_Wizard_feedback&oldid=106815121#Fehlermeldung
Comment 8 Gilles Dubuc 2014-01-13 13:11:14 UTC
For the record, since I had to grep the feedback page for it, the Russian comment dating September 24th 2013 just states that they've encountered the error, nothing more.
Comment 9 Gilles Dubuc 2014-01-13 13:59:11 UTC
I confirm that this is probably coming from chunked upload-specific APIs. More specifically "checkStatus", which allows to check when an upload has been reassembled when the chunk API keeps replying "Poll".

It seems like something almost identical is also exposed to API consumers through "statuskey", but UploadWizard doesn't seem to make use of it.

The failure is due to the session entry for the requested filekey being missing. I will investigate further once I have shell access approved to access logs. Something I'm particularly interested in finding out is whether all the session data is missing or just the entry for the particular file we're interested in.
Comment 10 Nemo 2014-10-03 14:48:53 UTC
Just got this on https://commons.wikimedia.org/wiki/File:Practica_D._magistri_V00241_00000004.tif

Error console says the following, dunno if related:

2 Validation error against schema UploadWizardFlowEvent: Unrecognized property: quantity
8 Failed to load resource: the server responded with a status of 503 (Service Unavailable) https://commons.wikimedia.org/wiki/Special:UploadStash/thumb/12mniz1s4dlw.l7rnkh.4135183.tif/lossy-page1-78px-12mniz1s4dlw.l7rnkh.4135183.tif.jpg
Comment 11 Bawolff (Brian Wolff) 2014-10-03 16:22:14 UTC
(In reply to Gilles Dubuc from comment #9)
> I confirm that this is probably coming from chunked upload-specific APIs.
> More specifically "checkStatus", which allows to check when an upload has
> been reassembled when the chunk API keeps replying "Poll".
> 
> It seems like something almost identical is also exposed to API consumers
> through "statuskey", but UploadWizard doesn't seem to make use of it.
> 
> The failure is due to the session entry for the requested filekey being
> missing. I will investigate further once I have shell access approved to
> access logs. Something I'm particularly interested in finding out is whether
> all the session data is missing or just the entry for the particular file
> we're interested in.

Is this a sudden increase? If so, maybe hhvm related? chunked upload does some scary stuff with sessions, it wouldn't shock me if hhvm interfered with that somehow.
Comment 12 Jonatan Svensson Glad (Josve05a) 2014-10-22 14:28:09 UTC
I'm adding HHVM to the keywords, just in case.

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


Navigation
Links