Thanks for the explanation. On Tue, 31 May 2022, 18:38 Maxim Dounin, <mdounin@mdounin.ru> wrote: > Hello! > > On Tue, May 31, 2022 at 06:01:01PM +0200, evald ibrahimi wrote: > > > Just encounter this issue on the latest version of nginx 1.22.0. > > Basically i added the "proxy_read_timeout 600s;" in a server directive > and > > run "nginx -sby Evald80 - Nginx Mailing List - English
hello, Just encounter this issue on the latest version of nginx 1.22.0. Basically i added the "proxy_read_timeout 600s;" in a server directive and run "nginx -s reload". I was getting still "upstream timed out (110: Connection timed out) while reading response header from upstream, client: " after 60 seconds which is the default value. Than i said, let's restart theby Evald80 - Nginx Mailing List - English
Seems the problem is with the modsec module. After disabling it, the problem disappeared... Also nginx -t command is very slow with modsec module enabled. Pretty strange that nobody has encountered this issue. Mos probably people are not running modsec and websites on the same installation of nginx.by Evald80 - Nginx Mailing List - English
Problem appeared again. Well i have to disable the last module which is mod_sec and see again. If the issue appears again, can we say that we have a memory leak on nginx? I have noticed that Currrent config is the following. # nginx -V nginx version: nginx/1.19.1 built by gcc 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC) built with OpenSSL 1.0.2k-fips 26 Jan 2017 TLS SNI support enabledby Evald80 - Nginx Mailing List - English
Hi, The issue appeared again. I checked the memory and it is the same as previously. Something(within the nginx process) is eating the whole memory on the server or the nginx itself(who knows). In order to troubleshoot. The strategy will be to remove all the modules and leave only ModSec and wait for at least one week. I saw that in less than a week, usually it appears...ModSec module is buby Evald80 - Nginx Mailing List - English
Hi, this is a vm created from the cloud provider. Than i just added the repo of nginx, the official one. Than did regular upgrades. Today also i run the yum update and got the 1.19.1 version of nginx. # nginx -V nginx version: nginx/1.19.1 built by gcc 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC) built with OpenSSL 1.0.2k-fips 26 Jan 2017 TLS SNI support enabled configure arguments: --prefixby Evald80 - Nginx Mailing List - English
The problem appeared again and at the time of writing is still present and i did not reboot the machine which will fix it. The following are the commands i executed in order to get some info: Basically this seems a problem with nginx and not a library issue: first of all: is it running nginx? # systemctl status nginx ● nginx.service - nginx - high performance web server Loaded: loadby Evald80 - Nginx Mailing List - English
hello, There is not too much 1GB. No, i did not disabled mode_sec. The list of loaded modules: load_module modules/ngx_http_brotli_filter_module.so; load_module modules/ngx_http_brotli_static_module.so; load_module modules/ngx_http_modsecurity_module.so; load_module modules/ngx_http_geoip2_module.so; this is an issue that suddenly started to come out. There always has been this configby Evald80 - Nginx Mailing List - English
hi, it happened again and i see that nginx is eating all the memory of the server. Somebody could help me how to troubleshoot? Mos probably there is a memory leak but don't know if on nginx or ModSec. There are 10websites on this server and they are not popular at all. Some clicks a day, so no superbusy website. thank youby Evald80 - Nginx Mailing List - English
hello everybody, I'm using nginx 1.19.0 with ModSec on Centos 7. The other day it happened twice that nginx was stopped. No idea what could cause the issue but i found on the error.log the following: So it seems the server was running out of memory and it stopped nginx? Thank you 2020/06/29 17:23:39 1890#1890: sendmsg() failed (9: Bad file descriptor) 2020/06/29 17:23:39 1890#1890: sendmsg()by Evald80 - Nginx Mailing List - English
+1 It would b great to have precompressed dynamic responsesby Evald80 - How to...