Skip to content

memory leak? #118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
ghost opened this issue Jun 27, 2018 · 1 comment
Closed

memory leak? #118

ghost opened this issue Jun 27, 2018 · 1 comment
Assignees

Comments

@ghost
Copy link

ghost commented Jun 27, 2018

I have a small PHP farm of nginx servers and php-fpm with ModSecv3 installed. Over the past several days, I noticed that Nginx worker processes are consuming 3GB of memory per worker (work is auto and thus is using 4 for me) and thus running out of memory and OOM killer kills the worker and the process starts over. I disable ModSecurity (ie modsecurity off) and memory usage doesnt increase. I've only been running in detection only mode for these servers. I suspect that its a memory leak because of the growing memory requirement and this issue only started since installing modsecurity with this Nginx/PHP farm. Nginx normally stays below 1GB memory usage.

"ps aux --sort -rss" is how i'm viewing memory using.

@victorhora victorhora self-assigned this Jun 27, 2018
@victorhora
Copy link
Contributor

@BP9906 make sure you're using the latest codebase from master for both ModSecurity-nginx and ModSecurity. There's a number of recent improvements in case you're running libModSecurity 3.0.0, 3.0.1 or 3.0.2.

I'm marking this as duplicate as memory management issues are already being discussed here: #73 / #79, #115. Please follow up your observations on these issues. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant