PM2 startup on macOS Catalina
What's probably happening is that pm2 isn't generating the correct script because your PATH variable contains spaces (most likely &quot;VMWare Fusion&quot; in your case).
Run echo $PATH, clean it up by escaping the space character using a backslash (\), then manually paste the resulting PATH variable in pm2's generated startup script.
So basically instead of running a generated pm2 script like this:
sudo env PATH=$PATH:/usr/local/bin /usr/local/lib/node_modules/pm2/bin/pm2 startup launchd -u &lt;user&gt; --hp &lt;user_folder&gt;

run something like this:
sudo env PATH=&lt;your `echo $PATH` output with escaped spaces&gt;:/usr/local/bin /usr/local/lib/node_modules/pm2/bin/pm2 startup launchd -u &lt;user&gt; --hp &lt;user_folder&gt;