Skip to content
This repository has been archived by the owner on Jun 12, 2018. It is now read-only.

Upload stuck at 100% #466

Open
Phyks opened this issue Sep 20, 2016 · 4 comments
Open

Upload stuck at 100% #466

Phyks opened this issue Sep 20, 2016 · 4 comments
Labels

Comments

@Phyks
Copy link

Phyks commented Sep 20, 2016

Hi,

I have an upload stuck at 100%, never finishing. See screenshot:
capture d ecran 2016-09-20 a 10 45 32

The only way to end it is to refresh the page, and the uploaded file is not there. Uploading other files in this folder work.

I think it might be specific to this file. I cannot attach it to this issue, in case you need it for debugging (it is an apk of cozy app), but it is available at https://ufile.io/8d849.

Thanks

@clochix
Copy link
Contributor

clochix commented Sep 21, 2016

Well, I tried and uploaded this file into my server without any problem.
Could you have a look at the logs of file app on server side ? /usr/local/var/log/cozy/files*

@clochix clochix added the bug label Sep 21, 2016
@Phyks
Copy link
Author

Phyks commented Sep 21, 2016

Sorry, I forgot about the logs on server side. Here is what I have there

[Tue, 20 Sep 2016 14:45:22 GMT] - POST /files/ - - - - ms -  -
error - files | Error: unrecognized content-type: application/json
    at Form.parse (/usr/local/cozy/apps/files/node_modules/multiparty/index.js:152:21)
    at module.exports.create (/usr/local/cozy/apps/files/build/server/controllers/files.js:330:15)
    at Layer.handle [as handle_request] (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/layer.js:82:5)
    at next (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/route.js:110:13)
    at Route.dispatch (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/route.js:91:3)
    at Layer.handle [as handle_request] (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/layer.js:82:5)
    at /usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/index.js:267:22
    at Function.proto.process_params (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/index.js:321:12)
    at next (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/index.js:261:10)
    at logger (/usr/local/cozy/apps/files/node_modules/americano/node_modules/morgan/index.js:108:5)
error - files | Error: unrecognized content-type: application/json
    at Form.parse (/usr/local/cozy/apps/files/node_modules/multiparty/index.js:152:21)
    at module.exports.create (/usr/local/cozy/apps/files/build/server/controllers/files.js:330:15)
    at Layer.handle [as handle_request] (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/layer.js:82:5)
    at next (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/route.js:110:13)
    at Route.dispatch (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/route.js:91:3)
    at Layer.handle [as handle_request] (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/layer.js:82:5)
    at /usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/index.js:267:22
    at Function.proto.process_params (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/index.js:321:12)
    at next (/usr/local/cozy/apps/files/node_modules/americano/node_modules/express/lib/router/index.js:261:10)
    at logger (/usr/local/cozy/apps/files/node_modules/americano/node_modules/morgan/index.js:108:5)

[...]

error - file-model | Cannot destroy binary linked to document XXXXXXXXXXXXX

@nicofrand
Copy link
Contributor

Same error with a different file for me. I got an error with Firefox but when trying with Chrome, the progress just keeps stuck at 100% like in the screenshot above.

@clochix
Copy link
Contributor

clochix commented Mar 6, 2017

For the record, the Files application is being fully rewritten. We hope this issue will be gone in next version.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants