You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use the default logging config, which has a StreamHandler pointing at sys.stderr, and do not set --no-redirect-stdio, then when you send synapse a SIGHUP, it will stack overflow and abort.
The problem appears to be that when you SIGHUP it, the streamhandler gets repointed at the redirected stderr, which goes back into a logger: so as soon as anything is logged, we get an infinite loop.
The text was updated successfully, but these errors were encountered:
This issue has been migrated from #6550.
If you use the default logging config, which has a
StreamHandler
pointing at sys.stderr, and do not set--no-redirect-stdio
, then when you send synapse a SIGHUP, it will stack overflow and abort.The problem appears to be that when you SIGHUP it, the streamhandler gets repointed at the redirected stderr, which goes back into a logger: so as soon as anything is logged, we get an infinite loop.
The text was updated successfully, but these errors were encountered: