Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1450298

Summary: when ProxyErrorOverride is On, modcluster return 503 status code on subsequent requests (2)
Product: Red Hat Enterprise Linux 6 Reporter: Patrick <pbajenez>
Component: httpdAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Maryna Nalbandian <mnalband>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.8CC: aogburn, bgollahe, bnater, cww, deesharm, jorton, luhliari, pbajenez, thozza
Target Milestone: rcKeywords: Patch, Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: httpd-2.2.15-68.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-19 05:16:59 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: 1494483    

Description Patrick 2017-05-12 08:11:01 UTC 
Description of problem:

Hello,

I'm re-opening the bug 1310582

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


How reproducible:

I'm attaching the same reproducer as for the bu 1310582

Steps to Reproduce:


1. setup mod_cluster and deploy the sample app
2. run the test script, which curl to the sample app. 
3. Observe access and error log

Actual results:
we see around 10 calls after the error, getting 503 while, they should go through

Expected results:

After the broken call, all subsequent unbroken calls should return 200 status
Actual results:

127.0.0.2 - - [12/May/2017:09:59:05 +0200] "GET /cluster_test_bis/ HTTP/1.1" 200 611
127.0.0.2 - - [12/May/2017:09:59:34 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 200 611
127.0.0.2 - - [12/May/2017:09:59:34 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 200 611
127.0.0.2 - - [12/May/2017:09:59:34 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 200 611
127.0.0.2 - - [12/May/2017:09:59:34 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 200 611
127.0.0.2 - - [12/May/2017:09:59:34 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 200 611
127.0.0.2 - - [12/May/2017:09:59:34 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 200 611
127.0.0.2 - - [12/May/2017:09:59:34 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 200 611
127.0.0.2 - - [12/May/2017:09:59:34 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 200 611
127.0.0.2 - - [12/May/2017:09:59:34 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 200 611
127.0.0.2 - - [12/May/2017:09:59:34 +0200] "GET /cluster_test_bis/indexbug.jsp HTTP/1.1" 500 10
127.0.0.2 - - [12/May/2017:09:59:35 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 503 10
127.0.0.2 - - [12/May/2017:09:59:35 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 503 10
127.0.0.2 - - [12/May/2017:09:59:35 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 503 10
127.0.0.2 - - [12/May/2017:09:59:35 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 503 10
127.0.0.2 - - [12/May/2017:09:59:35 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 503 10
127.0.0.2 - - [12/May/2017:09:59:35 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 503 10
127.0.0.2 - - [12/May/2017:09:59:35 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 503 10
127.0.0.2 - - [12/May/2017:09:59:35 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 503 10
127.0.0.2 - - [12/May/2017:09:59:35 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 503 10
127.0.0.2 - - [12/May/2017:09:59:35 +0200] "GET /cluster_test_bis/index.jsp HTTP/1.1" 503 10

Expected results:


Additional info:
Comment 6 Chris Williams 2017-08-16 16:05:17 UTC 

*** This bug has been marked as a duplicate of bug 1310582 ***
Comment 19 errata-xmlrpc 2018-06-19 05:16:59 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://access.redhat.com/errata/RHBA-2018:1891