Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enable VERBOSE crashes the parse-server #1777

Closed
benishak opened this issue May 13, 2016 · 8 comments
Closed

enable VERBOSE crashes the parse-server #1777

benishak opened this issue May 13, 2016 · 8 comments

Comments

@benishak
Copy link
Contributor

benishak commented May 13, 2016

Env

  • ParseServer 2.2.9 (runs with PM2)
  • AWS EC2 (CentOS+NGINX)
  • iOS App

Problem

I enabled VERBOSE=1 but when I interact with the App, Parse through logs in the console but it crashes after that

verbose: GET /classes/XXXX { connection: 'upgrade',
  host: 'api-dev',
  'content-length': '1082',
  'x-parse-client-version': 'i1.12.0',
  accept: '*/*',
  'x-parse-session-token': 'r:XXXX',
  'x-parse-application-id': 'XXX',
  'x-parse-client-key': 'XXX',
  'x-parse-installation-id': 'XXX',
  'x-parse-os-version': '9.3 (15E65)',
  'accept-language': 'en-us',
  'accept-encoding': 'gzip, deflate',
  'content-type': 'application/json; charset=utf-8',
  'user-agent': 'xxxx/1 CFNetwork/758.3.15 Darwin/15.4.0',
  'x-parse-app-build-version': '1',
  'x-parse-app-display-version': '2.2.18' } {
  "where": {
    "$or": [
      {
          .....
       }
  },
  "include": ".....",
  "order": "-createdAt",
  "limit": "1000"
}
parse-server running on port 8082. <----- the server restart
@bohemima
Copy link
Contributor

Most likely related to Unitech/pm2#2152

@benishak
Copy link
Contributor Author

Can be right because it also crashes with "info"

@drew-gross
Copy link
Contributor

I see you've removed some parts of your request. Could you include those parts? It might be that you are includeing massive amounts of data or doing a very complex query and causing your server to run out of memory. Also can you watch the memory usage of your server while you do this?

@benishak
Copy link
Contributor Author

It is dev env ,I just open the App and it through that error, cpu and ram usage are fine, max load 0.05 and max ram usage 40%

@drew-gross
Copy link
Contributor

And there is no other errors output? If there is an error in the request, there will be more logging output. Currently I don't have enough info to debug this.

@bohemima
Copy link
Contributor

bohemima commented May 13, 2016

Check "pm2 logs" - I'm pretty sure the server is restarted because of the log file changing.

@flovilmart
Copy link
Contributor

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)

@guidesanti
Copy link

guidesanti commented Aug 3, 2016

If the watch feature is enabled you must ensure that the log folder is added to watch ignore list, otherwise every time a log occurs the process will be restarted by the pm2.
See the example of an ecosystem.json file to configure the process:

{
"apps" : [{
"script" : "worker.js",
"watch" : true,
"ignore_watch" : ["node_modules", "logs"]
}]
}

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

No branches or pull requests

5 participants