PM2 Issue with treekill: false and startup.

What's going wrong?

In my ecosystem.config.js file, I set treekill to false. The first time killing pm2 doesn't kill the child process I spawned before. After rebooting the server and trying it again treekill is ignored and the child process is killed too when I kill pm2.

How could we reproduce this issue?

treekill:false in ecosystem.config.js

pm2 save
pm2 startup

Spawning child process:

const run = spawn("sh", ["restart.sh"], {
      cwd: projectPath,
      detached: true,
      stdio: ["ignore", out, err],
    }).unref();

Restart.sh:

pm2 kill
pkill -9 PM2
<code>
reboot

After Server reboot: treekill:false doesn't work anymore.

Running Restart.sh after reboot:

pm2 kill <-- child process gets killed here too
pkill -9 PM2
<code>
reboot

Start with the ecosystem.config.js setting for treekill and the restart.sh sequence using pm2 kill, pkill -9 PM2, and reboot. Reproduce the behavior before and after pm2 save and pm2 startup, then determine why treekill:false is not preserved after reboot and verify that the child process remains alive.