Red Hat Bugzilla – Bug 157832
httpd segfault on logrotate
Last modified: 2007-11-30 17:07:07 EST
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):
Steps to Reproduce:
when receiving SIGHUP, httpd segfaults
server should restart
Created attachment 114418 [details]
customer provided core file from httpd crash
Created attachment 114419 [details]
patch to avoid dereferencing of NULL pointer
This isn't the most graceful solution, given the problem description, but it
seems reasonable, since it seems that re-writing httpd to be thread safe in its
cleanup handlers could be fairly invasive. It basically just checks for NULL
on calls to apr_file_close. My other thought would be to add fields to
registered cleanup handlers to mark them as being "run" so as to prevent double
execution, but this seemed more appropriate to me.
Thanks for the report, but there is too much analysis here and not enough
What version of the httpd package is being used? Do you have a precise repro
case for this issue? What configuration is being used, which triggers this?
Why are you talking about "threads"? (/usr/sbin/httpd does not use threads)
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.