Bug 1303572 - httpd-2.2.15-47.el6_7.1 is breaking old mod_cluster setup
Summary: httpd-2.2.15-47.el6_7.1 is breaking old mod_cluster setup
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: httpd
Version: 6.7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Luboš Uhliarik
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1374441
TreeView+ depends on / blocked
 
Reported: 2016-02-01 10:51 UTC by Patrick
Modified: 2020-09-10 09:31 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-18 12:02:53 UTC
Target Upstream Version:

Attachments (Terms of Use)
coredump (5.62 MB, application/zip)
2016-02-01 10:51 UTC, Patrick 		no flags Details
issued sosreport (11.06 MB, application/x-xz)
2016-02-01 10:53 UTC, Patrick 		no flags Details
sosreport after downgrade (11.22 MB, application/x-xz)
2016-02-03 13:42 UTC, Patrick 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Patrick 2016-02-01 10:51:14 UTC 
Created attachment 1120063 [details]
coredump

Description of problem:

Customer has 3 Apaches on RHEL 6.7 Server with mod_cluster (1 active and 2 passives) and 6 JBoss Server (EAP 5.1.2 - Windows 2008 R2).

This got broken after updating to the following packages:
Updating:
 httpd                           x86_64                     2.2.15-47.el6_7.1                          rhel-x86_64-server-6                     830 k
Updating for dependencies:
 httpd-tools                     x86_64                     2.2.15-47.el6_7.1                          rhel-x86_64-server-6                      77 k
 mod_ssl                         x86_64                     1:2.2.15-47.el6_7.1                        rhel-x86_64-server-6                      95 k

Customer had to do a yum history to rollback to the pervious stable setup.
I will attach the sosreport  captured during the issue (upgrade done)
and i'm waiting for an other one captured after downgrade.

attaching also the coredump, and other relevant logs,

So far we were not successful on finding the root cause, till we suggest a downgrade.





Additional info:
Comment 1 Patrick 2016-02-01 10:53:05 UTC 
Created attachment 1120064 [details]
issued sosreport
Comment 4 Patrick 2016-02-03 13:42:23 UTC 
Created attachment 1120788 [details]
sosreport after downgrade
Comment 19 RHEL Program Management 2017-07-18 12:02:53 UTC 
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.