mods enabled: access_compat.load authz_groupfile.load dir.load mpm_event.conf proxy.load ssl.conf alias.conf authz_host.load env.load mpm_event.load remoteip.load ssl.load alias.load authz_user.load filter.load negotiation.conf reqtimeout.conf status.conf auth_basic.load autoindex.conf headers.load negotiation.load reqtimeout.load status.load authn_core.load autoindex.load ldap.conf proxy_ajp.load rewrite.load vhost_alias.load authn_file.load deflate.conf ldap.load proxy.conf setenvif.conf authnz_ldap.load deflate.load mime.conf proxy_connect.load setenvif.load authz_core.load dir.conf mime.load proxy_http.load socache_shmcb.load
We did find a LOT of ldap connections not being closed also (when Apache was hung we saw over 300 established LDAP connections). While it didnt fix the overall memory leak we fixed those number of connections hung by forcing the ldap connection and pool to timeout after 60s. LDAP seems suspect for the memory leak but not sure. On Fri, Jun 19, 2020 at 9:28 AM Yann Ylavic <ylavic....@gmail.com> wrote: > On Fri, Jun 19, 2020 at 4:20 PM 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? > > Nevermind, MaxMemFree 2048 is already the default so it's likely not the > issue. > > Which modules do you load? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org > For additional commands, e-mail: users-h...@httpd.apache.org > >
