You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2019/02/13 05:35:47 UTC

[Bug 63170] mod_proxy_http2 segmentation fault and out of memory condition

https://bz.apache.org/bugzilla/show_bug.cgi?id=63170

Warren D. Johnson <wa...@jtechgrp.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|                            |All

--- Comment #1 from Warren D. Johnson <wa...@jtechgrp.com> ---
Thought of some other details:

Both Web server and Reverse Proxy server are running CentOS 7.

All services are hosted on AWS (ec2 instances).

Reverse Proxy is a clean install of CentOS 7 onto an AWS ec2 instance.

Web server CentOS 7 is an OpenVZ container.

I built another reverse proxy server on CentOS 7 and instead of building Apache
from source, I installed it using repositories maintained by codeit.guru. 
Those packages experienced the same out of memory problems as my source code
build. In the case of codeit.guru build, we were using Protocol h2 in the SSL's
vhost.

I built another reverse proxy server (as a test) using Ubuntu 18 and installed
all necessary packages using apt-get.  That includes http2, mod_proxy,
mod_proxy_http2, mod_ssl etc.  We experienced the same memory leak issues.

If I use "Protocol HTTP/1.1" instead of "Protocol h2" in the vhost entry in the
ssl.conf file, I do not experience any problems.  It is something in the
interplay between h2 on the web server and h2 on the reverse proxy server.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org