Could the exit (aka return aka result) code from a process be logged, maybe only if nonzero, after Exited?
Not all components (run directly or indirectly by a Procfile) log the reason they're exiting. For example, I spent quite awhile tracking down what turned out to be a case of ~/.nvm/nvm.sh returning exit code 3 with no other explanation — but even finding that took awhile, because the output of Overmind didn't make clear to me why it decided to shut down (Interrupting...) all the processes.
Seeing several processes simply logged as Exited, followed by Interrupting... of a process, can be confusing — especially if the interrupted process throws a semi-random error, as a result of being interrupted, such as a stack trace.
Envek
commented
3 months ago
Could the exit (aka return aka result) code from a process be logged, maybe only if nonzero, after
Exited?Not all components (run directly or indirectly by a
Procfile) log the reason they're exiting. For example, I spent quite awhile tracking down what turned out to be a case of~/.nvm/nvm.shreturning exit code3with no other explanation — but even finding that took awhile, because the output of Overmind didn't make clear to me why it decided to shut down (Interrupting...) all the processes.Seeing several processes simply logged as
Exited, followed byInterrupting...of a process, can be confusing — especially if the interrupted process throws a semi-random error, as a result of being interrupted, such as a stack trace.