In my h2 test suite, I do a setup where I use proxy configs against the server itself. We seem to have a problem performing a clean child exit with that. Test in 2.4.48 and trunk:
- run tests with several graceful restarts
- no proxied request, clean exit
- with proxied requests
AH00045: child process 53682 still did not exit, sending a SIGTERM
AH00045: child process 53682 still did not exit, sending a SIGTERM
[often stops here, sometimes]
...
AH00046: child process 53682 still did not exit, sending a SIGKILL
Question:
- is such a test setup doomed to fail in general?
- are we sure that we cannot encounter such states in "normal" setups?
If someone wants at log at whatever LogLevels, let me know. It's seems highly reproducible.
- Stefan
- run tests with several graceful restarts
- no proxied request, clean exit
- with proxied requests
AH00045: child process 53682 still did not exit, sending a SIGTERM
AH00045: child process 53682 still did not exit, sending a SIGTERM
[often stops here, sometimes]
...
AH00046: child process 53682 still did not exit, sending a SIGKILL
Question:
- is such a test setup doomed to fail in general?
- are we sure that we cannot encounter such states in "normal" setups?
If someone wants at log at whatever LogLevels, let me know. It's seems highly reproducible.
- Stefan