Bug 61376 - httpd segfault after receiving graceful/restart signals
Summary: httpd segfault after receiving graceful/restart signals
Status: NEW
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: All (show other bugs)
Version: 2.4.27
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-02 19:34 UTC by zhaojz518
Modified: 2017-08-03 18:54 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description zhaojz518 2017-08-02 19:34:40 UTC 
httpd segfault after every graceful/restart. Compiled with solaris studio 12.3 on a solaris 10 x86 server. No problem with httpd-2.4.25. This bug is only present for 2.4.26 and 2.4.27.

Core file analysis output (solaris 11.3 x86):
......
threading model: native threads
status: process terminated by SIGSEGV (Segmentation Fault), pid=4359 uid=1000
                
                
                ** Thread stack($c) **
                ----------------------
0x59ac0e0(80f5cf0, 811c9c0, 81259f0)
ap_run_pre_config+0x57(80f5cf0, 811c9c0, 81259f0)
main+0xb2c(6, feffeb40, feffeb5c, feffeafc)
_start+0x67(6, feffec26, feffec3e, feffec41, feffec5b, feffec5e)

......
Comment 1 Eric Covener 2017-08-02 21:32:03 UTC 
(In reply to zhaojz518 from comment #0)
> httpd segfault after every graceful/restart. Compiled with solaris studio
> 12.3 on a solaris 10 x86 server. No problem with httpd-2.4.25. This bug is
> only present for 2.4.26 and 2.4.27.
> 
> Core file analysis output (solaris 11.3 x86):
> ......
> threading model: native threads
> status: process terminated by SIGSEGV (Segmentation Fault), pid=4359 uid=1000
>                 
>                 
>                 ** Thread stack($c) **
>                 ----------------------
> 0x59ac0e0(80f5cf0, 811c9c0, 81259f0)
> ap_run_pre_config+0x57(80f5cf0, 811c9c0, 81259f0)
> main+0xb2c(6, feffeb40, feffeb5c, feffeafc)
> _start+0x67(6, feffec26, feffec3e, feffec41, feffec5b, feffec5e)
> 
> ......

Do you load mod_auth_digest? Does it fail w/o it?
Comment 2 zhaojz518 2017-08-02 22:14:00 UTC 
We use mod_auth_digest, but it still segfault without it. I also tried not loading mod_info and mod_status, same results.
Comment 3 Eric Covener 2017-08-02 22:42:34 UTC 
Do you use a loadable MPM? I am thinking PR60487 somehow.

reverting the changes from:
http://svn.apache.org/viewvc?view=revision&revision=1797368
would be another good test.
Comment 4 zhaojz518 2017-08-03 17:58:23 UTC 
Yes. We use loadable mpms. But same results after I compiled static prefork and event mpms for 2.4.27. How do I roll back just revision 1797368 from the 2.4.27 release? I am not familiar with the apache repository. Can you provide a tarball for it if it is not too much trouble?
Comment 5 zhaojz518 2017-08-03 18:54:34 UTC 
On the 2.4.27 tree, I reverted all six files from revision 1797368 to 2.4.25 version. I recompiled with static event mpm, but still same results - segfault at ap_run_pre_config?