Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 157933 - httpd segfault on logrotate
httpd segfault on logrotate
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: apr (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
Depends On:
Blocks: 156322
  Show dependency treegraph
Reported: 2005-05-17 05:35 EDT by Joe Orton
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version: RHBA-2005-622
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-10-05 11:37:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2005:622 qe-ready SHIPPED_LIVE httpd bug fix update 2005-10-05 00:00:00 EDT

  None (edit)
Description Joe Orton 2005-05-17 05:35:58 EDT
+++ 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 11:37:52 EDT
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.