[SRU] apache2 mpm-worker segmentation fault.

Bug #235294 reported by Chuck Short
6
Affects Status Importance Assigned to Milestone
Apache2 Web Server
Fix Released
Critical
apache2 (Debian)
Fix Released
Unknown
apache2 (Ubuntu)
Fix Released
Undecided
Unassigned
Hardy
Fix Released
Undecided
Unassigned
Intrepid
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: apache2

When torture testing an apache2-mpm-worker I get numerous segmentation faults and sigbus errors:

[Tue May 27 14:16:40 2008] [notice] child pid 8848 exit signal Segmentation fault (11)
[Tue May 27 14:18:35 2008] [notice] child pid 9075 exit signal Segmentation fault (11)
[Tue May 27 14:19:37 2008] [notice] child pid 9159 exit signal Segmentation fault (11)
[Tue May 27 14:19:37 2008] [notice] child pid 9215 exit signal Segmentation fault (11)
[Tue May 27 14:20:19 2008] [notice] child pid 9495 exit signal Segmentation fault (11)
[Tue May 27 14:22:52 2008] [notice] child pid 9523 exit signal Segmentation fault (11)

Fix is commited in the apache cvs and will backport it.

chuck

Revision history for this message
Chuck Short (zulcss) wrote :

Under heavy loads apache2-mpm-worker will segfault, upstream has fixed this for apache-2.2.9 however it is not fixed for 2.2.8. I have backported this patch to 2.2.8. There should be no regressions when this patch has been introduced. I have attached the patch which fixes this.

TEST CASE:

1. Install apache2-mpm-worker in a KVM environment.
2. tail -f the apache error log file
3. Fun the following command: for i in `seq 1 100`; do ab -n 100000 -c 20 http://<ip address/ ; done

Changed in apache2:
status: New → Confirmed
Revision history for this message
Chuck Short (zulcss) wrote :
Revision history for this message
Martin Pitt (pitti) wrote :

Accepted into -proposed, please test and give feedback here

Changed in apache2:
status: New → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Can you please forward this to Debian and get it fixed there/in intrepid?

Revision history for this message
Dustin Kirkland  (kirkland) wrote : Re: [Bug 235294] Re: [SRU] apache2 mpm-worker segmentation fault.

On Thu, May 29, 2008 at 3:33 AM, Martin Pitt <email address hidden> wrote:
> Can you please forward this to Debian and get it fixed there/in
> intrepid?

This fix is upstream in Apache2.

We should ask for a Debian Unstable sync to an updated Apache2, and
merge that into Intrepid. (Perhaps that's what you're suggesting,
Martin).

:-Dustin

Changed in apache2:
status: Unknown → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

Dustin, I didn't see anything relevant in the current Sid apache changelog (we have the same version in intrepid). Can you please check this, and if it is fixed, close the intrepid task?

I tested the hardy-proposed package, and it does not crash with the test case given above. I also functions normally.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Patch ported forward to the version in Intrepid. Debdiff attached.

I still need to open a Debian bug for this and ensure that the same patch is either applied to Debian unstable's Apache2, or that they sync up with a later release from apache.org soon.

:-Dustin

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apache2 - 2.2.8-4ubuntu1

---------------
apache2 (2.2.8-4ubuntu1) intrepid; urgency=low

  * debian/patches/100_mpm_wokers_crash.dpatch
    - Fix for segmentation fault with mpm-worker is under load.
      Backported from http://svn.apache.org/viewvc?view=rev&revision=631362.
      (LP: #235294)
  * Modify Maintainer value to match the DebianMaintainerField
    specification.

 -- Dustin Kirkland <email address hidden> Thu, 05 Jun 2008 15:23:03 -0500

Changed in apache2:
status: Confirmed → Fix Released
Changed in apache2:
status: Unknown → New
Revision history for this message
Martin Pitt (pitti) wrote :

Copied to hardy-updates.

Changed in apache2:
status: Fix Committed → Fix Released
Changed in apache2:
status: New → Fix Released
Changed in apache2:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.