Segfaults on Ubuntu 14.04 #1380
Comments
|
The only thing I found : nodejs/node-v0.x-archive#2376 |
|
This may happen while using PM2 but I honestly think it has nothing to do with PM2 :) |
|
Give it a try with |
|
Different symptoms, currently it just crashes all node apps, and it does say |
|
|
|
Published @0.14.2 ;) |
|
Hello. |
|
I am also seeing this issue on Ubuntu 14.04 w/nodejs 0.12.6 and PM2 0.14.3, and it is not due to the hung-task kernel issue that has been referenced previously. This is the only thing that shows up in our kernel log: [ 8023.396041] PM2 v0.14.3: Go[29558]: segfault at 8090000404c ip 00000000009037f8 sp 00007fff7e3d9a80 error 4 in nodejs[400000+b61000] I have to do '/etc/init.d/pm2-init.sh start' to get things running again. If this is a nodejs bug, I am happy to file a bug with them, I just want to help fix the issue however I can. If PM2 doesn't have any native code then it is definitely a nodejs bug. |
We'll have to move back to upstart. Pity. Good luck. |
|
Is there any error in |
|
I don't see any errors on Yesterday I reinstalled node.js from the source code ( Did anyone with this problem try with node.js installed from the source code? |
|
There is nothing in my pm2.log at the time of the segfault. Anything else I can look at? What is the best way to start pm2 with gdb? |
|
pm2.log: |
|
Lot of restarts there ^^. This isn't good: |
|
@suprMax According to the first post, the segfault happenned |
|
@jhansen-tt Last time I had to debug a segfault I used https://github.com/ddopson/node-segfault-handler. I don't know if it's possible with gdb. @jshkurti indeed. |
|
@soyuka I don't get the RangeError, or anything in my pm2.log when it happens. Just the segfault notification in the kernel log. Right now I have to use crontab to see if the PID in ~/.pm2/pm2.pid is still running, and if not, then I run /etc/init.d/pm2 restart... |
|
Any chance newer versions of Node could fix this ? (perhaps Node v0.12.6) |
|
@jshkurti I am already on 0.12.6 and I see it. |
|
@jhansen-tt would be nice to have a way to reproduce or a better stack trace :/. I'm using node 0.12.3 with pm2 0.14.1 with a 20D+ uptime (debian 7). +1 @jshkurti or |
|
@soyuka I am just running an express server and a couple of python scripts with PM2... Nothing fancy. |
|
Same here @jhansen-tt but with fancy things and I've absolutely no issue. On another server I've pm2 |
|
i ran into a segfault today, but I can't get my processes to launch now... |
|
running produced no output in logs and just hangs when I called I got the following in ~/.pm2/pm2.log |
|
looks like my issue is related to #1204 , bah... |
|
I think this issue needs to be broken out into two:
|
|
PM2 stop frequently and stop the app #1433 |
|
No, the problem is not solved in v0.14.3. |
|
Can you try using the development branch ? |
|
@jorge-d I will try when I have some free time, I hope this weekend. Thank you for the work. |
|
I'm waiting with bated breath too - this is causing me a lot of headaches. |
|
After 2 days, no crashes with the development branch... |
|
I updated several servers that had segfaults on fri night, I can also report no crashes yet.. |
|
@klinquist @membrive Still working? We'll publish it soon, we just need some more confirmations! |
|
Yes still working! Not a single segfault on the 4 servers I updated. |
|
AWESOME :) merging to master and publishing |
|
I'm not running the development PM2 in production (with load), but I'm running it in four virtual machines (without load), and there is no segfaults in 4 days! I think that this feedback is not decisive but just for your information. |
|
PM2 0.14.4 with GC force removed published! Please upgrade via (it keep your current process list): |
|
im getting the same problem. pm2.log |
|
That's because you're using PM2 v0.14.2. |
|
@jshkurti already updated thanks |
Hi!
We used to use upstart to run our Node apps and decided to try to move to pm2 instead. Unfortunately on our production machine it crashes at least once a day.
kern.log:
Jun 22 15:06:02 Ubuntu-1404-trusty-64-minimal kernel: [569531.959543] PM2 v0.14.1: Go[19539]: segfault at 3fffffffa0 ip 0000000000902e38 sp 00007fff99f29290 error 4 in nodejs[400000+b60000]We tried to add upstart to call
pm2 resurrectin case pm2 dies, but apparently that doesn't work too. Couldn't really check that one though.We have node v0.12.4.
Is anyone else experiencing the same issue? It's really a shame, I loved keymetrics interface, but I can't use it without pm2 on the server.
The text was updated successfully, but these errors were encountered: