Properly detect PM2 manager process instead of using a hardcoded ID

2022-10-30 23:16:03 -05:00 · 2022-10-30 23:16:03 -05:00 · c3b97c121e
commit c3b97c121e
parent 341f89cda5
2 changed files with 56 additions and 42 deletions
--- a/utils/misc.js
+++ b/utils/misc.js
@ -98,15 +98,22 @@ export function getServers(bot) {
        };
        pm2Bus.on("process:msg", listener);
      });
-      pm2.sendDataToProcessId(0, {
-        id: 0,
-        type: "process:msg",
-        data: {
-          type: "getCount"
-        },
-        topic: true
-      }, (err) => {
-        if (err) reject(err);
+      pm2.list((err, list) => {
+        if (err) {
+          reject(err);
+          return;
+        }
+        const managerProc = list.filter((v) => v.name === "esmBot-manager")[0];
+        pm2.sendDataToProcessId(managerProc.pm_id, {
+          id: managerProc.pm_id,
+          type: "process:msg",
+          data: {
+            type: "getCount"
+          },
+          topic: true
+        }, (err) => {
+          if (err) reject(err);
+        });
      });
    } else {
      resolve(bot.guilds.size);