Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 157933 - httpd segfault on logrotate
Summary: httpd segfault on logrotate
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: apr
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Joe Orton
QA Contact:
Depends On:
Blocks: 156322
TreeView+ depends on / blocked
Reported: 2005-05-17 09:35 UTC by Joe Orton
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: RHBA-2005-622
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-10-05 15:37:52 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:622 qe-ready SHIPPED_LIVE httpd bug fix update 2005-10-05 04:00:00 UTC

Description Joe Orton 2005-05-17 09:35:58 UTC
+++ This bug was initially created as a clone of Bug #157832 +++

Description of problem:
httpd appears to have race problems in its cleanup handlers, in that it appears
those cleanup handlers can be run from multiple threads in the httpd process.

Version-Release number of selected component (if applicable):

How reproducible:
not sure

Steps to Reproduce:
Actual results:
when receiving SIGHUP, httpd segfaults

Expected results:
server should restart

Additional info:
There were two parts to this bug: the segfaults are caused by missing error
checking in APR.

Comment 5 Red Hat Bugzilla 2005-10-05 15:37:52 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.