benoitc
Update arbiter.py - log SIGTERM as info level message
I recently started to record gunicorn error messages and everytime I reloaded gunicorn, I received error log messages from every worker. SIGTERM should not generate an error log message. Info level is more appropriate since it is a graceful exit.
please don't break behavior that exist since years. We bneed to check if first the behavior changed here and also how errors are configured at user level. We sometimes uses stderr to not go through the stdout which would be the case with info level.
How about ignoring the SIGTERM signal then? Because this signal is thrown internally to gracefully shutdown workers. This should NOT generate a error message (introduced by PR #2419)
+1
We recently upgraded gunicorn to the latest version, and this has been a pain point for us. Whenever our containers are taken down for deployment, it emits this error log line even though we exit gracefully. Graceful shutdowns should never result in an error log. This issue is polluting our alarming.
