3.14.0: Call to process.exit() timed out, aborting.

Description:

While a co-admin was configuring API parameters and looking at the user and room lists on a staging server (13 users total), R.C 3.14.0 crashed for no apparent reason. (This looks very similar to #14821, which mentions restarting, but my colleague says they didn't do anything to restart the software.)

Steps to reproduce:

1. (Unclear)
2. Server dies with the following log entries:

May 17 18:13:14 my.stage.server.example rocketchat[1329]: Call to process.exit() timed out, aborting.
May 17 18:13:14 my.stage.server.example rocketchat[1329]:  1: 0xa093f0 node::Abort() [/usr/local/bin/node]
May 17 18:13:14 my.stage.server.example rocketchat[1329]:  2: 0xa7d9c9  [/usr/local/bin/node]
May 17 18:13:14 my.stage.server.example rocketchat[1329]:  3: 0xbf02a9  [/usr/local/bin/node]
May 17 18:13:14 my.stage.server.example rocketchat[1329]:  4: 0xbf2097 v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [/usr/local/bin/node]
May 17 18:13:14 my.stage.server.example rocketchat[1329]:  5: 0x13cf199  [/usr/local/bin/node]
May 17 18:13:14 my.stage.server.example systemd[1]: rocketchat.service: Main process exited, code=killed, status=6/ABRT
May 17 18:13:14 my.stage.server.example systemd[1]: rocketchat.service: Unit entered failed state.
May 17 18:13:14 my.stage.server.example systemd[1]: rocketchat.service: Failed with result 'signal'.

3. We had to manually restart R.C via systemctl restart rocketchat.service

Expected behavior:

Don't crash, please. 😉

Actual behavior:

systemd service exited (see logs above). (This is the first time it crashed on us in about a year, so thanks! 🍪 )

Server Setup Information:

• Version of Rocket.Chat Server: 3.14.0 (Commit Hash: 1255c8f0ca, Commit Branch: HEAD)
• Operating System: Debian GNU/Linux 9.13 (stretch)
• Deployment Method: rocketchatctl
• Number of Running Instances: 2 (one on this staging VM, one on a separate production VM)
• DB Replicaset Oplog: I don't know what that is, but the startup log says "Enabled"
• NodeJS Version: 12.18.4 - x64
• MongoDB Version: 4.0.19 (mmapv1)

Client Setup Information

• Desktop App or Browser Version: Firefox 88
• Operating System: Ubuntu 16.04

Additional context

–

Relevant logs:

The system ran with loglevel 0, so the above logs are all we have.

Start with the provided systemd and Node.js logs, the Rocket.Chat 3.14.0 environment details, and related issue #14821. Investigate what initiated the timed-out process.exit() and whether the failure can be reproduced; done means identifying a cause and preventing the service from aborting or documenting the required fix.