filesController sporadically missing in FilesRouter

[benishak]

Env

• ParseServer 2.2.9
• AWS EC2 (Centos+Nginx)
• Self-hosted MongoDB on AWS

Problem

error: Uncaught internal server error. [TypeError: Cannot read property 'getFileData' of undefined] TypeError: Cannot read property 'getFileData' of undefined
    at getHandler (/home/centos/apps/parse-server-dev/source/node_modules/parse-server/lib/Routers/FilesRouter.js:69:22)
    at Layer.handle [as handle_request] (/home/centos/apps/parse-server-dev/source/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5)
    at next (/home/centos/apps/parse-server-dev/source/node_modules/parse-server/node_modules/express/lib/router/route.js:131:13)
    at Route.dispatch (/home/centos/apps/parse-server-dev/source/node_modules/parse-server/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/home/centos/apps/parse-server-dev/source/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5)
    at /home/centos/apps/parse-server-dev/source/node_modules/parse-server/node_modules/express/lib/router/index.js:277:22
    at param (/home/centos/apps/parse-server-dev/source/node_modules/parse-server/node_modules/express/lib/router/index.js:349:14)
    at param (/home/centos/apps/parse-server-dev/source/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14)
    at param (/home/centos/apps/parse-server-dev/source/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14)
    at Function.process_params (/home/centos/apps/parse-server-dev/source/node_modules/parse-server/node_modules/express/lib/router/index.js:410:3)

This error appears randomly in the console and it makes the ParseServer crash, I still can't able to reproduce it

https://github.com/ParsePlatform/parse-server/blob/master/src/Routers/FilesRouter.js#L39

[drew-gross]

I don't see how this could happen. Please let me know if you are ever able to reproduce this, I haven't been able to reproduce it either.

[benishak]

reproduce

As fair as I tested it could be reproduced in this way but not all the time

• point the app to api.parse.com
• login to the app
• switch the app to self-hosted-parse-server
• open the app
• the error appears in the console only that time

[flovilmart]

Closing due to lack of activity, please update to latest parse-server version and reopen if the issue persist.

Don't forget to include your current:

• node version
• npm version
• parse-server version
• any relevant logs (VERBOSE=1 will enable verbose logging)

[lowgator]

I have had the same issue along with the exact error message. benishak are you still having this issue as well?

[themoonlitknight]

I have the same identical issue and I'm able to reproduce it. I'm using the parse-server-fs-adapter to store files. While storing succeeds, when I try to retrieve a file Parse crashes with that error log. I posted this issue here weeks ago parse-community/parse-server-fs-adapter#3.
This does not happen with the default GridStoreAdapter.

My configuration:
• node: v4.4.6
• npm: 2.15.5
• parse-server: dev version

[agordeev]

I'm getting the same error on migrated app. I uploaded a file through Parse Dasboard and now trying to access it, but getting this in error log:

 error: Uncaught internal server error. TypeError: Cannot read property 'getFileData' of undefined
 at getHandler (/usr/lib/node_modules/parse-server/lib/Routers/FilesRouter.js:69:22)
 at Layer.handle [as handle_request] (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5)
 at next (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/route.js:131:13)
 at Route.dispatch (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/route.js:112:3)
 at Layer.handle [as handle_request] (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5)
 at /usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:277:22
 at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:349:14)
 at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14)
 at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14)
 at Function.process_params (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:410:3) TypeError: Cannot read property 'getFileData' of undefined
 at getHandler (/usr/lib/node_modules/parse-server/lib/Routers/FilesRouter.js:69:22)
 at Layer.handle [as handle_request] (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5)
 at next (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/route.js:131:13)
 at Route.dispatch (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/route.js:112:3)
 at Layer.handle [as handle_request] (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5)
 at /usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:277:22
 at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:349:14)
 at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14)
 at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14)
 at Function.process_params (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:410:3)

The dashboard shows this:

{"code":1,"message":"Internal server error."}

Parse Server version is 2.2.15.
Parse Dashboard version is 1.0.15

This error is persistent.

[agordeev]

@flovilmart Can you please reopen this issue, as I wouldn't like to open a new one?

[flovilmart]

Please update to latest version and reopen the issue if it persists

[venkataramanab]

I'm using parse server version 2.2.25
Problem still exists
error: Uncaught internal server error. [TypeError: Cannot read property 'getFileData' of undefined] TypeError: Cannot read property 'getFileData' of undefined at getHandler (/usr/lib/node_modules/parse-server/lib/Routers/FilesRouter.js:81:24) at Layer.handle [as handle_request] (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5) at next (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/route.js:131:13) at Route.dispatch (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/route.js:112:3) at Layer.handle [as handle_request] (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5) at /usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:277:22 at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:349:14) at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14) at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14) at Function.process_params (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:410:3) TypeError: Cannot read property 'getFileData' of undefined at getHandler (/usr/lib/node_modules/parse-server/lib/Routers/FilesRouter.js:81:24) at Layer.handle [as handle_request] (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5) at next (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/route.js:131:13) at Route.dispatch (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/route.js:112:3) at Layer.handle [as handle_request] (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/layer.js:95:5) at /usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:277:22 at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:349:14) at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14) at param (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:365:14) at Function.process_params (/usr/lib/node_modules/parse-server/node_modules/express/lib/router/index.js:410:3)

[flovilmart]

Can you provide the logs when running with VERBOSE=1 when this occurs?

[venkataramanab]

sure!, please give me a moment.