server: Use wtfnode to log reasons why node isn't exiting

ether · Jan 30, 2021 · 877f0c5 · 877f0c5
1 parent ba81ead
commit 877f0c5
Show file tree

Hide file tree

Showing 4 changed files with 19 additions and 2 deletions.
diff --git a/package-lock.json b/package-lock.json
diff --git a/src/node/server.js b/src/node/server.js
@@ -27,6 +27,10 @@
 const log4js = require('log4js');
 log4js.replaceConsole();
 
+// wtfnode should be loaded after log4js.replaceConsole() so that it uses log4js for logging, and it
+// should be above everything else so that it can hook in before resources are used.
+const wtfnode = require('wtfnode');
+
 /*
  * early check for version compatibility before calling
  * any modules that require newer versions of NodeJS
@@ -211,6 +215,7 @@ exports.exit = async (err = null) => {
   setTimeout(() => {
     console.error('Something that should have been cleaned up during the shutdown hook (such as ' +
                   'a timer, worker thread, or open connection) is preventing Node.js from exiting');
+    wtfnode.dump();
     console.error('Forcing an unclean exit...');
     process.exit(1);
   }, 5000).unref();

diff --git a/src/package-lock.json b/src/package-lock.json
diff --git a/src/package.json b/src/package.json
@@ -72,7 +72,8 @@
     "tinycon": "0.0.1",
     "ueberdb2": "^1.2.5",
     "underscore": "1.8.3",
-    "unorm": "1.4.1"
+    "unorm": "1.4.1",
+    "wtfnode": "^0.8.4"
   },
   "bin": {
     "etherpad-lite": "node/server.js"