-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
PM2 Daemon is dead #3266
Comments
We were seeing this in our ECS container logs, and it turned out to be a hard memory limit in the task definition killing the container and If you don't have any health or monitoring on the container server, this probably isn't the issue. |
@johnwebbcole Thanks for reply |
Hi, I have the same issue but I can't find log. @johnwebbcole , can you provide us more information? Thanks. |
@rahulkulmi no, this was strictly an issue with our cloud formation health check killing the container on a hard memory limit. The If you don’t have anything monitoring your process, then this most likely isn’t the issue. |
@johnwebbcole Sorry I am not getting your point properly but thanks for reply. |
@rahulkulmi He said that this log was printed because something send a Closing since not related to PM2 |
I've seen this error on various web apps, on one staging server (Ubuntu) and on AWS Linux. Last night I also encountered it on a Debian system with a pm2-docker container with 2 simple javascripts that execute simple jobs. No indication at all why it was killed. The process uses about 2% of 10GB RAM so there is no memory problem. Even /var/log/daemon.log showed no indication why docker should have killed it. |
From the code of here, its looks like the PM2 Daemon took more than 4.5 seconds to repond so the CLI so it assumed that it crashed. Could you checkout in |
@vmarchaud I can reproduce this issue every time. From my container
Nothing in My Dockerfile
And I run it with |
We're encountering this issue too, any updates on this? |
This is happening to me too. Turning off With this config
it crashes every time
here's the 2017-12-12 23:43:21: ===============================================================================
2017-12-12 23:43:21: --- New PM2 Daemon started ----------------------------------------------------
2017-12-12 23:43:21: Time : Tue Dec 12 2017 23:43:21 GMT+0000 (UTC)
2017-12-12 23:43:21: PM2 version : 2.8.0
2017-12-12 23:43:21: Node.js version : 8.9.1
2017-12-12 23:43:21: Current arch : x64
2017-12-12 23:43:21: PM2 home : /home/app/.pm2
2017-12-12 23:43:21: PM2 PID file : /home/app/.pm2/pm2.pid
2017-12-12 23:43:21: RPC socket file : /home/app/.pm2/rpc.sock
2017-12-12 23:43:21: BUS socket file : /home/app/.pm2/pub.sock
2017-12-12 23:43:21: Application log path : /home/app/.pm2/logs
2017-12-12 23:43:21: Process dump file : /home/app/.pm2/dump.pm2
2017-12-12 23:43:21: Concurrent actions : 2
2017-12-12 23:43:21: SIGTERM timeout : 1600
2017-12-12 23:43:21: ===============================================================================
2017-12-12 23:43:21: [Watch] Start watching tmp-node-8-final
2017-12-12 23:43:21: Starting execution sequence in -cluster mode- for app name:tmp-node-8-final id:0
2017-12-12 23:43:21: App name:tmp-node-8-final id:0 online
2017-12-12 23:43:21: (node:48) [DEP0007] DeprecationWarning: worker.suicide is deprecated. Please use worker.exitedAfterDisconnect.
2017-12-12 23:43:26: CONFIG: missing version file /home/app/tmp-node-8-final/src/config/version.json
2017-12-12 23:43:26: CONFIG: missing environment secret file /home/app/tmp-node-8-final/src/config/secret/development.json
2017-12-12 23:43:29: Server is now running on http://localhost:3000 when I change |
same issue here. Downgrading to 2.6.1 solves for me |
Fixed with new pm2-runtime:
|
@Unitech When do you think this fix will be merge on master branch. I'm not going to release a development version of pm2 in production. |
PM2 2.10.1 has been release:
|
I am using pm2 as a "pm2-docker" inside the docker container but it will stop response after some time and the last message i got from pm2 is "PM2 Daemon is dead" inside my log file.
When i am using pm2 2.6.1 that time i am not getting this problem so please tell me what is the issue and how i can fix this issue.
This pm2 issue is related to ec2 server memory or some thing else. please reply me ASAP
The text was updated successfully, but these errors were encountered: