Nodejs app that previously ran fine under pm2 will no longer start, even though same app with same args and user works about pm2 HOT 5 CLOSED

Nearly forgot: Running Ubuntu 23.10 and Node v21.6.2

from pm2.

Unless someone comes up with a surprise solution to this one in the next couple of days, I think I'm going to reinstall the entire OS and everything from scratch, possibly while performing the lesser banishing ritual of the pentagram of Earth, while waving chicken bones at it, then hoping the problem doesn't re-appear - then I'll try to forget it happened.

I figure this is either something ridiculously simple and silly that I did, or it's some darn thing stuck in an arcane location that is messed up, and not fixed by standard purging and reinstalling.

from pm2.

I mean, other than that, my thoughts on pm2 are basically "where have you been all my life? Where were you when I was still working?"

: )

I feel like the problem is likely not with PM2 per se, I'm figuring either I'm missing something, or something got corrupted somewhere, and the problem shows up with PM2, but other launch methods don't trigger whatever it is for some reason. I don't know. It's weird.

from pm2.

Okay, this one was dumb. Apparently, while doing some debugging, I got the error.log file for that server stun-locked. When it would try to write a warning message, it would apparently hit the log and die, instead of writing to it or failing politely.

A victory for science. Not ghosts.

from pm2.

And it wasn't PM2's fault, there was a file path generating a warning, that was only happening with that server.

from pm2.