Solved
Local Dispatcher quits when terminal resizes due to SIGWINCH
SIGWINCH is a known signal that Apache2 interprets as a signal to do a graceful shutdown:
- https://itecnote.com/tecnote/apache-in-apache-2-a-caught-sigwinch-error/
- https://bz.apache.org/bugzilla/show_bug.cgi?id=50669
This means that when following the set up of a local Dispatcher, after running the "docker_run.sh ..." command, any resize / update / movement of the terminal will generate:
[Tue Sep 06 17:10:46.525423 2022] [core:notice] [pid 1:tid 281473502321736] AH00094: Command line: 'httpd -d /etc/httpd -f /etc/httpd/conf/httpd.conf -D FOREGROUND -D ENVIRONMENT_DEV'
[Tue Sep 06 17:15:31.209544 2022] [mpm_worker:notice] [pid 1:tid 281473502321736] AH00296: caught SIGWINCH, shutting down gracefully
[Tue Sep 06 17:15:34.601264 2022] [core:warn] [pid 1:tid 281473502321736] AH00045: child process 188 still did not exit, sending a SIGTERM
[Tue Sep 06 17:15:34.601441 2022] [core:warn] [pid 1:tid 281473502321736] AH00045: child process 189 still did not exit, sending a SIGTERM
[Tue Sep 06 17:15:34.601489 2022] [core:warn] [pid 1:tid 281473502321736] AH00045: child process 190 still did not exit, sending a SIGTERM
which is totally bizarre! I can reproduce this on demand. Even if I minimize the terminal window, the signal is always sent.
Has anyone else experienced this? Has anyone got a workaround? This has made local Dispatcher browsing/testing basically impossible, as the service and the docker instance shut down.
Thanks in advance!