https://issues.apache.org/bugzilla/show_bug.cgi?id=56351
--- Comment #14 from Eric Covener <[email protected]> --- (In reply to Michael van Rooyen from comment #13) > We're not using mod_auth_form, but are getting a SEGV in the same location, > only for us it's on graceful restart after log rotate: > > (gdb) bt > #0 0x00a72410 in __kernel_vsyscall () > #1 0x00d37b8b in read () from /lib/libpthread.so.0 > #2 0x08095884 in ap_mpm_podx_check (pod=0x9b79208) at mpm_unix.c:535 > #3 0x080a5cbe in child_main (child_num_arg=3) at worker.c:1341 > #4 0x080a6acb in make_child (s=0x9b64ee8, slot=3) at worker.c:1427 > #5 0x080a6b97 in startup_children (number_to_start=4) at worker.c:1452 > #6 0x080a744a in server_main_loop (_pconf=0x9b400a8, plog=0x9b669b0, > s=0x9b64ee8) at worker.c:1752 > > Prior to that, the httpd runs fine. We've just upgraded to 2.4.9 from 2.2.x > and started getting this after the first log rotation. > > Is it possible that the impact of this could be wider, and if so, will the > anticipated 2.4.10 change fix it, and are there any workarounds? > > Apart from standard Apache modules, we do use an in-house developed module > that's designed to be thread safe, and has run in 2.x servers for 10+ years > without any issues. Thanks! Open a new bug and get a backtrace of the thread that crashed, not the first thread. -- 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]
