https://bz.apache.org/bugzilla/show_bug.cgi?id=54519
--- Comment #4 from Luca Toscano <[email protected]> --- Thanks a lot for the tests, bz.apache.org/bugzilla/show_bug.cgi?id=60261 was a recent similar use case in which the same PID is re-used in Docker containers (so since it is the same PID it is safe to proceed). In the upcoming release (2.4.24) the code looks more or less like this: #Read the pid file and store the result in 'otherpid' rv = ap_read_pid(pconf, ap_pid_fname, &otherpid); if (otherpid != getpid() && kill(otherpid, 0) == 0) { # httpd already running } In this case, the new PID is different from the one used by the old httpd process (so otherpid != getpid()) but it is used by a completely different running process (so kill(otherpid, 0) == 0 is also true), that overlaps with the regular case in which httpd is already started and it is correct to end up in the "httpd already running" error case. Waiting for other feedback since I am not sure how to solve this issue simply looking at PIDs (something more might be needed). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
