pm2 crash

[will123195]

Unexpectedly my website was not responding so I checked pm2 status and I saw this:

┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬────────┬──────────┐
│ App name │ id │ mode │ pid │ status │ restart │ uptime │ memory │ watching │
└──────────┴────┴──────┴─────┴────────┴─────────┴────────┴────────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app

So I ran pm2 resurrect which fixed it.

The server was never rebooted. Also prior to this incident I had tested rebooting the machine and all the processes correctly started on boot.

I don't see anything helpful in the logs and I have no idea why all my processes disappeared unexpectedly. Here's the current state of the system:

root@node:~/.pm2# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.2 LTS
Release:    14.04
Codename:   trusty
root@node:~/.pm2# node -v
v0.12.7
root@node:~/.pm2# pm2 -v
0.14.3
root@node:~/.pm2# cat pm2.log
2015-09-12 00:19:27: Stopping app:g id:3
2015-09-12 00:19:27: App name:g id:3 disconnected
2015-09-12 00:19:27: App name:g id:3 exited with code SIGTERM
2015-09-12 00:19:27: Process with pid 23674 killed
2015-09-12 00:19:27: Starting execution sequence in -cluster mode- for app name:g id:3
2015-09-12 00:19:27: App name:g id:3 online
2015-09-12 22:59:27: [PM2][WORKER] Started with refreshing interval: 30000
2015-09-12 22:59:27: [[[[ PM2/God daemon launched ]]]]
2015-09-12 22:59:27: BUS system [READY] on port /root/.pm2/pub.sock
2015-09-12 22:59:27: RPC interface [READY] on port /root/.pm2/rpc.sock
2015-09-12 22:59:37: Starting execution sequence in -fork mode- for app name:a id:0
2015-09-12 22:59:37: App name:a id:0 online
2015-09-12 22:59:37: Starting execution sequence in -cluster mode- for app name:b id:1
2015-09-12 22:59:38: App name:b id:1 online
2015-09-12 22:59:38: Starting execution sequence in -cluster mode- for app name:c id:2
2015-09-12 22:59:38: App name:c id:2 online
2015-09-12 22:59:38: Starting execution sequence in -cluster mode- for app name:g id:3
2015-09-12 22:59:38: App name:g id:3 online
2015-09-12 22:59:38: Starting execution sequence in -cluster mode- for app name:d id:4
2015-09-12 22:59:39: App name:d id:4 online
root@node:~/.pm2# pm2 status
┌─────────────────┬────┬─────────┬───────┬────────┬─────────┬────────┬──────────────┬──────────┐
│ App name        │ id │ mode    │ pid   │ status │ restart │ uptime │ memory       │ watching │
├─────────────────┼────┼─────────┼───────┼────────┼─────────┼────────┼──────────────┼──────────┤
│ a               │ 0  │ fork    │ 13750 │ online │ 0       │ 40h    │ 278.336 MB   │ disabled │
│ b               │ 1  │ cluster │ 13751 │ online │ 0       │ 40h    │ 123.914 MB   │ disabled │
│ c               │ 2  │ cluster │ 13752 │ online │ 0       │ 40h    │ 79.836 MB    │ disabled │
│ g               │ 3  │ cluster │ 13777 │ online │ 0       │ 40h    │ 73.332 MB    │ disabled │
│ d               │ 4  │ cluster │ 13798 │ online │ 0       │ 40h    │ 76.973 MB    │ disabled │
└─────────────────┴────┴─────────┴───────┴────────┴─────────┴────────┴──────────────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app

Any idea what could have happened that required me to run pm2 resurrect?

[jontelm]

ubuntu@ip:/s$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
ubuntu@ip-172-31-14-210:/s$ node -v
v0.12.0
ubuntu@ip-172-31-14-210:~/s$ pm2 -v
0.14.3

pm2 resurrect worked for me to.

Sep 15 08:05:12 ip-172-31-14-210 kernel: [16845103.292831] PM2 v0.14.3: Go[8782]: segfault at 2ffffffa0 ip 00000000009a0808 sp 00007fffed5f7270 error 4 in node[400000+fd1000]

Looks like it's connected to #1380

[will123195]

Ah, I just upgraded to [email protected] so I expect this is no longer an issue.