Bug 1500217

Summary:	PerlIOApache_flush: flush can't be called before the response phase
Product:	[Fedora] Fedora EPEL	Reporter:	Matti Linnanvuori <matti.linnanvuori>
Component:	mod_perl	Assignee:	Andrew Bauer <zonexpertconsulting>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	jkaluza, jorton, perl-devel, ppisar
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:		Environment:
Last Closed:	2024-07-09 02:12:42 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:

Description Matti Linnanvuori 2017-10-10 08:34:35 UTC

Description of problem:

Handling a request fails with error message PerlIOApache_flush: flush can't be called before the response phase

Version-Release number of selected component (if applicable):

mod_perl-2.0.10-2.el7.x86_64

How reproducible:

Occasionally

Steps to Reproduce:
1. Execute Perl function system in mod_perl

Actual results:

Error PerlIOApache_flush: flush can't be called before the response phase
and no correct HTTP response

Expected results:

No error but successful HTTP response

Additional info:

httpd-2.4.6-67.el7_4.2.x86_64
perl-libs-5.16.3-292.el7.x86_64

Comment 1 Petr Pisar 2017-11-01 12:48:26 UTC

Upstream knows about similar failures related to Apache httpd 2.4 <https://marc.info/?l=apache-modperl&m=145261045030169&w=2> but they turned out to be caused by a thread-unsafe Perl code like <https://rt.cpan.org/Public/Bug/Display.html?id=118899>.

Can you provide a reproducer?

Comment 2 Fedora Admin user for bugzilla script actions 2022-02-05 05:02:23 UTC

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 3 Troy Dawson 2024-07-09 02:12:42 UTC

EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n As a result we are closing this bug.