Yes,we found that it was caused by a 3rd party module named "nginx_upstream_check_module". I want to know the use of connections in cache manager process. And if there are no free connections of cache manager process,any thing bad would happend?by zhijianpeng - Nginx Mailing List - English
I am using proxy_cache as a cache server, about 20-30k requests /s. It sometimes gets slow,and I find lots of such messages: 2014/11/05 17:01:32 22169#0: 512 worker_connections are not enough 2014/11/05 17:01:32 22169#0: 512 worker_connections are not enough 2014/11/05 17:04:12 22169#0: 512 worker_connections are not enough 2014/11/05 17:04:12 22169#0: 512 worker_connections are not enouby zhijianpeng - Nginx Mailing List - English
Sorry,I forgot about that my friend patch 0.8.47 for me. Let's forget about it, and 0.8.49 is clean here is my conf: #user nobody; worker_processes 1; #daemon off; #master_process off; #error_log logs/error.log; #error_log logs/error.log notice; error_log logs/error.log debug; #pid logs/nginx.pid; events { worker_connections 1024; } http {by zhijianpeng - Nginx Mailing List - English
Maxim Dounin Wrote: ------------------------------------------------------- > Hello! > > On Wed, Sep 01, 2010 at 07:59:54AM -0400, > zhijianpeng wrote: > > > url may cause nginx work process crash > > the code in > src/http/ngx_http_request.c:ngx_http_free_request > > r->upstream may be a NULL pointer > > > > > > #0 0x00000by zhijianpeng - Nginx Mailing List - English
And in 0.8.49 Core was generated by `sbin/nginx -c conf/nginx.conf'. Program terminated with signal 11, Segmentation fault. #0 ngx_http_terminate_request (r=0x180dac00, rc=400) at src/http/ngx_http_request.c:2073 2073 cln = cln->next; (gdb) n The program is not being run. (gdb) n The program is not being run. (gdb) n The program is not being run. (gdb) bt #0 ngx_httby zhijianpeng - Nginx Mailing List - English
url may cause nginx work process crash the code in src/http/ngx_http_request.c:ngx_http_free_request r->upstream may be a NULL pointer #0 0x000000000042b368 in ngx_http_free_request (r=0x13b60c20, rc=0) at src/http/ngx_http_request.c:2951 2951 switch (r->upstream->cache_status) { (gdb) bt #0 0x000000000042b368 in ngx_http_free_request (r=0x13b60c20, rc=0) at src/http/ngby zhijianpeng - Nginx Mailing List - English
I found that : #define NGX_LISTEN_BACKLOG 511 and use it as the backlog of listen() ls.backlog = NGX_LISTEN_BACKLOG; if (listen(s, ls.backlog) == -1) { Does it mean that only 511 connection could be accept at the same time ? May I modify it to 1024 or higher( I am sure use it less than SOMAXCONN )by zhijianpeng - Nginx Mailing List - English
thanks,we will update to the lastest version as soon as possibleby zhijianpeng - Nginx Mailing List - English
Does the VU#180065 relate with merge_slashes directive? what is the meanings of merge_slashes directive? http://sysoev.ru/nginx/patch.180065.txtby zhijianpeng - Nginx Mailing List - English
Igor Sysoev Wrote: ------------------------------------------------------- > On Mon, Apr 27, 2009 at 09:50:27AM -0400, > zhijianpeng wrote: > > > ========my nginx.conf=========== > > server { > > > > listen > 10.1.1.1:80; > > server_name > www.test1.com; > > roby zhijianpeng - Nginx Mailing List - English
========my nginx.conf=========== server { listen 10.1.1.1:80; server_name www.test1.com; root /opt/test1; } server { listen 80; server_name www.test2.com; root /opt/test2; } ========my nginx.conf=========== I found thby zhijianpeng - Nginx Mailing List - English