Closed erlandl4g closed 4 months ago
This could be changed to try and keep going with logging disabled but many users run supervisord
as a daemon. With no stdout
and no logfile, supervisord
wouldn't have a way to notify the user that anything is wrong. The problem may go unnoticed until sometime later when the user looks in the logfile and finds it is mysteriously out of date.
Crashing as it does now seems like a better behavior to me ("fail early"). supervisord
can't fulfill the requested configuration and doesn't have a way of communicating this to the user since logging doesn't work, so it just dies. The user is forced to fix the permissions mistake right away.
When Supervisor is started with non root user, but log file remains to be owned by root - supervisor crashes upon restart.