Summary: | Apache2 loops in child Segfaults | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Roy <roy> |
Component: | Core | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | NEEDINFO --- | ||
Severity: | critical | ||
Priority: | P2 | ||
Version: | 2.4.4 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
Roy
2013-04-29 14:30:17 UTC
The error log looks something like this: [Mon Apr 29 16:33:01.153356 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18240 exit signal Segmentation fault (11) [Mon Apr 29 16:33:02.334155 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18242 exit signal Segmentation fault (11) [Mon Apr 29 16:33:02.335361 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18264 exit signal Segmentation fault (11) [Mon Apr 29 16:33:02.335485 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18326 exit signal Segmentation fault (11) [Mon Apr 29 16:33:02.335662 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18327 exit signal Segmentation fault (11) [Mon Apr 29 16:33:02.335806 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18329 exit signal Segmentation fault (11) [Mon Apr 29 16:33:02.335883 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18384 exit signal Segmentation fault (11) [Mon Apr 29 16:33:02.335943 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18411 exit signal Segmentation fault (11) [Mon Apr 29 16:33:02.336000 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18412 exit signal Segmentation fault (11) [Mon Apr 29 16:33:02.336056 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18447 exit signal Segmentation fault (11) [Mon Apr 29 16:33:02.336112 2013] [core:notice] [pid 1885:tid 139898956883712] AH00052: child pid 18524 exit signal Segmentation fault (11) and goes on and on... Sounds to me like a platform bug. Which Linux distribution is it exactly? Can you check with your distributor? apr_thread_exit() simply calls pthread_exit(NULL). IMHO nothing to fix here. Could it be a low memory situation on the system, so that it kills the processes? Regards, Rainer Doing 'bt full' for the thread that crashes could give further hints if there is a problem in httpd. If there is a package with debug symbols for libc, installing that beforehand may be a good idea, too. For example, on Debian, this is called libc6-dbg. Is there anything else interesting in the error log? Try "grep -v AH00052 ..." |