Defer SIGHUP handlers to reactor. (#8817)

We can get a SIGHUP at any point, including times where we are not in a
sane state. By deferring calling the handlers until the next reactor
tick we ensure that we don't get unexpected conflicts, e.g. trying to
flush logs from the signal handler while the code was in the process of
writing a log entry.

Fixes #8769.

1 files changed, 1 insertions, 0 deletions

diff --git a/changelog.d/8817.bugfix b/changelog.d/8817.bugfix
new file mode 100644
index 0000000000..e45dbd2ba4
--- /dev/null
+++ b/changelog.d/8817.bugfix
@@ -0,0 +1 @@
+Fix bug where logging could break after a call to SIGHUP.