https://bz.apache.org/bugzilla/show_bug.cgi?id=62044
--- Comment #8 from Eric Covener <[email protected]> --- (In reply to mark from comment #7) > give that man a teddy bear. pid 13310 was born at 03:40:12 with a SIGHUP at > 03:47:58 and then permanently exiting at 03:48:11. > > [Thu Jan 25 03:40:22.300797 2018] [mpm_event:notice] [pid 13310:tid > 140455729428224] AH00489: Apache/2.4.29 (Unix) OpenSSL/1.0.2n > mod_fcgid/2.3.9 mod_auth_kerb/5.4 mod_qos/11.43 mod_jk/1.2.42 configured -- > resuming normal operations > [Thu Jan 25 03:40:22.300851 2018] [core:notice] [pid 13310:tid > 140455729428224] AH00094: Command line: '/apache24/bin/httpd -f > /apache24/conf/dynamic/apache24/httpd.conf -D XXXXX' > [Thu Jan 25 03:47:58.097848 2018] [mpm_event:notice] [pid 13310:tid > 140455729428224] AH00494: SIGHUP received. Attempting to restart > [Thu Jan 25 03:48:11.467544 2018] [core:notice] [pid 13310:tid > 140455729428224] AH00060: seg fault or similar nasty error detected in the > parent process > > so, the diagnosis probably remains roughly the same, some SHM keys are not > getting removed or not removed quickly enough and are still in place the > next time the same configuration starts up. If this is the case maybe we could bake the generation name into the filename. -- 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]
