Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1705574
Summary: | Segfaults in Apache after updating packages (using mod_cluster and mod_ssl) | |||
---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Patrick Dung <patdung100+redhat> | |
Component: | mod_cluster | Assignee: | Michal Karm Babacek <mbabacek> | |
Status: | CLOSED EOL | QA Contact: | Michal Karm Babacek <mbabacek> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 29 | CC: | anon.amish, bperkins, csutherl, jkaluza, jorton, lef, luhliari, mbabacek, pahan, puntogil | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1708248 (view as bug list) | Environment: | ||
Last Closed: | 2019-11-27 22:45:33 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1708248 |
Description
Patrick Dung
2019-05-02 13:46:30 UTC
I tried to disable loading of mod_ssl and the Apache instance does not have segfaults. So changing the component from mod_cluster to httpd (mod_ssl). If the backtrace is correct this is dumping core on the line: SSLConnRec *sslconn = myConnConfig(r->connection); this is almost certainly caused by mod_cluster's "fake" conn_rec/request_rec not being set up properly. Please kindly note my configuration files were used since 2018 and did not change. Only packages update ub today and the problem occurs. Fedora 30: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7813edd5a2 Fedora 29: https://bodhi.fedoraproject.org/updates/FEDORA-2019-17556e2ad6 Fedora 28: https://bodhi.fedoraproject.org/updates/FEDORA-2019-3877efca99 I had installed the updated rpm in FC29 from Bodhi and it should be ok now. BTW, I am just a end user and not suitable for the QA process or task. I would reset QA Contact to default. Thank you Patrick. This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |