I'm seeing a race condition in which the worker MPM logs the
"long lost child came home!" warning message. The test case
is:
- run "ab -c5" to create a steady load on the httpd
- while it's running, do a graceful restart.
This will sometimes yield the "long lost child" message.
I added a bit of diagnostic logging and found that the order
of events looks like this:
- child process for scoreboard slot X finishes its work and exits
- parent process forks a new child process and assigns it
to scoreboard slot X
- parent process notices that the first child process has
exited, looks for its pid in scoreboard, and doesn't find it
Is this a harmless (and expected) warning case, or cause for
alarm?
--Brian
