crowdsec-nginx-bouncer memory leak?
On a debian bookworm system with nginx (version 1.22.1-9+deb12u2) I try to install and run crowdsec-nginx-bouncer. As soon as the crowdsec-nginx-bouncer is configured, nginx gets regularly killed by oom.
The crowdsec lapi is running on a different machine.
As an example a "nginx -t" only takes 2 seconds to complete without crowdsec-nginx-bouncer and with installed/configured/enabled crowdsec-nginx-bouncer the command "nginx -t" takes at least 1 minute.
A "nginx -s reload" acts quickly (under 3 seconds) without crowdsec-nginx-bouncer and with installed/configured/enabled crowdsec-nginx-bouncer the nginx service gets killed by "out of memory".
Normally, the nginx process takes about 1 gigabyte of ram on this machine. The machine has 6 gigabytes of memory. With crowdsec-nginx-bouncer and reloading nginx with "nginx -s reload" it quickly jumps up to 4 gigabytes and then gets oomed.
Does anybody have the same problem? How do I debug this? Where could be the error? Thank you for your help.
The crowdsec lapi is running on a different machine.
As an example a "nginx -t" only takes 2 seconds to complete without crowdsec-nginx-bouncer and with installed/configured/enabled crowdsec-nginx-bouncer the command "nginx -t" takes at least 1 minute.
A "nginx -s reload" acts quickly (under 3 seconds) without crowdsec-nginx-bouncer and with installed/configured/enabled crowdsec-nginx-bouncer the nginx service gets killed by "out of memory".
Normally, the nginx process takes about 1 gigabyte of ram on this machine. The machine has 6 gigabytes of memory. With crowdsec-nginx-bouncer and reloading nginx with "nginx -s reload" it quickly jumps up to 4 gigabytes and then gets oomed.
Does anybody have the same problem? How do I debug this? Where could be the error? Thank you for your help.
