Plugins potentially causing crash

faizanzahid

Our node bb is getting randomly crash due to following:

2018-03-06T02:05:08.813Z [27711] - [33mwarn[39m: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run ./nodebb reset -p PLUGINNAME to disable it.
[33m * [39mnodebb-plugin-composer-default

We are on latest version of node bb. It crashes once in a blue moon.
@fais3000

PitaJ

@faizanzahid that's a warning. It is not causing your NodeBB to crash. Are there any errors in your logs?

faizanzahid

@pitaj Many thanks for your quick response. currently we r running node bb on pm2 so that in case of crash it should restart automatically. but this time and few times before, it went down but it did not restart itself on its own. So i had to goto manually do pm2 restart nameofmyprocess

For your reference, I have attached the 2 pm2 log files, 1 is the pm2 error log output and other is the node bb console output.

The recent crash happened at 3:15 AM Ireland time, so you can see at 3:15 am and log lines after that time. I am not 100% sure what exactly caused the issue. Could it also be mongod getting out of RAM?

Our DO droplet is 16 GB memory, 320 GB drive and 6 CPU cores, so it should not be that issue i guess. Or could be mongod taking too much ram ?

PS: Please see the 2 logs attached. Oh wait, i can't attach the 2 log files, it gives me privilege errors here. let me paste the links.

Pm2 error log:
https://drive.google.com/file/d/1xGC5XXUDVuwvyhll35NYYGYnJEiYWrn6/view?usp=sharing

Pm2 node bb output log:
https://drive.google.com/file/d/1hvjJKcInydFCG_7TPahoZC5TetLyZS0i/view?usp=sharing

Please let me know if you are able to see both log files.

teh_g

@faizanzahid I'm no developer, but it looks like Mailgun is misconfigured and causing the crash?

julian

I'm seeing stack traces, but there's no indication of NodeBB starting up or stopping, so I don't know what's happening here. Could be memory exhaustion leading to the NodeBB process being killed?