Bug 1233109

Summary: Backtrace when DocumentRoot is symlink
Product: Red Hat Enterprise Linux 6 Reporter: Martin Frodl <mfrodl>
Component: httpdAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Petr Šplíchal <psplicha>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7CC: dkutalek, jkaluza, ohudlick, psplicha, public_neo
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: httpd-2.2.15-48.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 21:36:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Backtrace none

Description Martin Frodl 2015-06-18 08:59:23 UTC
Created attachment 1040378 [details]
Backtrace

Description of problem:

When DocumentRoot is a symlink and httpd is executed in the foreground, this glibc error message appears when Ctrl-C is hit, followed by backtrace:

*** glibc detected *** httpd: free(): invalid pointer: 0x00007fc823583ed8 ***

Version-Release number of selected component (if applicable):
httpd-2.2.15-45.el6.x86_64

How reproducible:
Give it several tries.

Steps to Reproduce (starting from default Apache configuration):
# cd /var/www
# mv html foo
# ln -s foo html
# httpd -DFOREGROUND
httpd: Could not reliably determine the server's fully qualified domain name, using qeos-28.lab.eng.rdu2.redhat.com for ServerName
^C*** glibc detected *** httpd: free(): invalid pointer: 0x00007fc823583ed8 ***
======= Backtrace: =========
(see attachment)

Comment 2 Jan Kaluža 2015-06-18 10:29:06 UTC
This looks more like the Bug 1131006 appearing in RHEL6.

Comment 9 errata-xmlrpc 2016-05-10 21:36:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0841.html