You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys. I'm facing with a issue, I'm running a single nginx reverse proxy (4 core CPU and 8GB RAM) and I have around 20 backend sites in production env.
I often change the rule and add new site, so whenever I try to using nginx -s reload, it take a long time, after that the CPU and RAM increase too much. Sometimes it will crash my nginx services because 100% cpu and I need to take restart the nginx service using systemctl instead of nginx -s reload. It's not a good way to restart nginx by using systemctl whenever I have change in modsec config or add new rule.
Whether any advices for this problem? I also remove some REQ and RESP rules in CRS for reduce the workload, but not good enough.
This is my error log in nginx when I reload.
This is RAM and CPU usage when I reload the nginx
Server (please complete the following information):
Modsecurity: v3/master for Linux with nginx-connector v1.0.3
WebServer: nginx-1.18.0
CRS: owasp-crs 4.11.0-dev
OS: Ubuntu 20.04
When compile modsecurity I'm not use --with-pcre2.
The text was updated successfully, but these errors were encountered:
Hi guys. I'm facing with a issue, I'm running a single nginx reverse proxy (4 core CPU and 8GB RAM) and I have around 20 backend sites in production env.
I often change the rule and add new site, so whenever I try to using nginx -s reload, it take a long time, after that the CPU and RAM increase too much. Sometimes it will crash my nginx services because 100% cpu and I need to take restart the nginx service using systemctl instead of nginx -s reload. It's not a good way to restart nginx by using systemctl whenever I have change in modsec config or add new rule.
Whether any advices for this problem? I also remove some REQ and RESP rules in CRS for reduce the workload, but not good enough.
This is RAM and CPU usage when I reload the nginx

Server (please complete the following information):
The text was updated successfully, but these errors were encountered: