We changed CGI stderr handling in the latest update so it's probably related & a regression.

Anything non-standard in the config, anything interesting in /var/log/httpd/error_log?

The config is fairly standard:

<VirtualHost *:80>
	ServerName git.infradead.org
	DocumentRoot /var/www/git
	Alias /robots.txt /var/www/git/static/robots.txt
        <Directory /var/www/git>
                Options +ExecCGI
                AddHandler cgi-script cgi

                DirectoryIndex gitweb.cgi

                RewriteEngine On
                RewriteCond %{REQUEST_FILENAME} !-f
                RewriteCond %{REQUEST_FILENAME} !-d
                RewriteRule ^.* /gitweb.cgi/$0 [L,PT]
        </Directory>
</VirtualHost>


I see these in logs (along with lots of other things that don't seem abnormal, and some that do but are correlated with my 'killall gitweb.cgi'. Will try to get something correlated with a specific event and misbehaving child.

[Wed Oct 02 01:21:39.911249 2019] [cgid:warn] [pid 11096:tid 140026738374400] [client 111.202.100.85:47553] AH01220: Timeout waiting for output from CGI script /var/www/git/gitweb.cgi
[Wed Oct 02 01:21:39.911331 2019] [core:error] [pid 11096:tid 140026738374400] (70007)The timeout specified has expired: [client 111.202.100.85:47553] AH00574: ap_content_length_filter: apr_bucket_read() failed
[Wed Oct 02 01:23:49.276596 2019] [cgid:warn] [pid 11096:tid 140026662840064] [client 111.202.100.85:34962] AH01220: Timeout waiting for output from CGI script /var/www/git/gitweb.cgi
[Wed Oct 02 01:23:49.326259 2019] [cgid:error] [pid 11096:tid 140026662840064] [client 111.202.100.85:34962] Script timed out before returning headers: gitweb.cgi
[Wed Oct 02 01:24:49.375809 2019] [cgid:warn] [pid 11096:tid 140026662840064] [client 111.202.100.85:34962] AH01220: Timeout waiting for output from CGI script /var/www/git/gitweb.cgi
[Wed Oct 02 01:26:00.853221 2019] [cgid:warn] [pid 30783:tid 140026327328512] [client 111.202.100.85:62428] AH01220: Timeout waiting for output from CGI script /var/www/git/gitweb.cgi
[Wed Oct 02 01:26:00.853300 2019] [core:error] [pid 30783:tid 140026327328512] (70007)The timeout specified has expired: [client 111.202.100.85:62428] AH00574: ap_content_length_filter: apr_bucket_read() failed

*** Bug 1757196 has been marked as a duplicate of this bug. ***

If i may:

it started exactly with 2.4.41, reverting to 2.39.3 stopped it.

There were no helpful messages inside error_log. PHP just gets stuck in write(). I know, not helpfull, but thats what happening.

"We" used PHP via AddHandler and a cgiwrapper ( user based privilege seperation and chroot ) and noticed, that it only happens,
when large chunks of data should be read from the cgi script. In our case, we generated PDF files with >500k. All other, smaller php outputs, like Wordpress html pages, worked as expected.

It's reliable stucking, should be easy to find. More infos in Bug 1757196 if needed.

Commit: https://src.fedoraproject.org/rpms/httpd/c/5b6bedca6c8618b5f40c887c01399f5592d154e0

Package: httpd-2.4.41-4.fc32

A bit speculative this fixes the problem, but the above removes one difference between mod_cgi and mod_cgid using the new stderr handling.  I'm building for f30.

Package: httpd-2.4.41-4.fc30

f30 build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1393459

would be useful to test but I haven't reproduced this so not confirmed the fix yet.

if you build a F29 version, i can check it.

Package: httpd-2.4.41-4.fc29

*FIX CONFIRMED*

FEDORA-2019-d0255b7710 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d0255b7710

FEDORA-2019-c39b063554 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c39b063554

Seems fixed here with the koji build from comment #9.

Thanks a lot folks for testing this!

httpd-2.4.41-5.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d0255b7710

httpd-2.4.41-5.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c39b063554

httpd-2.4.41-5.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-8df80552fc

httpd-2.4.41-5.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

httpd-2.4.41-5.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

httpd-2.4.41-5.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.