I do not have that installed but will definitely look into it as it may have a similar effect on what I found. The problem I found (well kind of) is that there is some unknown memory leak. Was looking at another thread where it stated if there is a memory leak in one of the modules and MaxConnectionsPerChild (mpm_event) is set to 0 then it will slowly climb and eat all your memory. Sure enough I changed that from 0 to 4000 (just a guess) and memory has been flat lined even since. In addition Apache CPU usage on my xymon graphs was just all over the place throughout the day and its flatlined now too. It could be the nature of the app behind this reverse proxy as it performs horribly and there are LOTs of items that just timeout and dont get responded to so we had to be aggressive on our timeouts in the first place.
On Fri, Jun 19, 2020 at 9:20 AM Yann Ylavic <ylavic....@gmail.com> wrote: > On Thu, Jun 18, 2020 at 8:03 PM Danny Mallory <dmal...@gmail.com> wrote: > > > > Anyone here know a good way to tell what Apache may be chewing up memory > on? > > Do you have MaxMemFree configured already > (https://httpd.apache.org/docs/2.4/mod/mpm_common.html#maxmemfree)? > If not, does "MaxMemFree 2048" (for instance) help? > > Regards; > Yann. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
