Thanks a lot Maxim,you identified the issue (Monitd is the issue), after stopping the monit i have not faced the issue. Thanks for the prompt and trust on the Nginx... I have used following configurations: server { listen 8090; server_name uwsgi; add_header Access-Control-Allow-Origin "*"; add_header Access-Control-Allow-Methods "by arulmarans - Nginx Mailing List - English
I have already gone through that link, still gdb was not catching core dump... Log snippet: 2014/10/30 13:54:07 16259#0: *2 http static fd: 11 2014/10/30 13:54:07 16259#0: *2 http set discard body 2014/10/30 13:54:07 16259#0: *2 HTTP/1.1 200 OK^M Server: nginx/1.7.6^M Date: Thu, 30 Oct 2014 08:24:07 GMT^M Content-Type: text/html^M Content-Length: 1249^M Last-Modified: Thu, 28 Augby arulmarans - Nginx Mailing List - English
Hi Maxim Dounin, I have gone through those steps, still i was not able to catch the backtrace in the gdb. log snippet: 014/10/30 13:54:07 16259#0: *2 posix_memalign: 00000000025B6980:4096 @16 2014/10/30 13:54:07 16259#0: *2 add cleanup: 00000000025BF6A0 2014/10/30 13:54:07 16259#0: *2 http static fd: 11 2014/10/30 13:54:07 16259#0: *2 http set discard body 2014/10/30 13:54:07 16by arulmarans - Nginx Mailing List - English
In my setup, i have nginx proxy in different machine, nginx server and uwsgi service. Once Nginx server receives the request from the proxy, it invokes the uwsgi call to using uwsgi socket, uwsgi module replies the request, after receiving the response from the uwsgi service nginx server forwards the response to the proxy, after transaction completes, nginx trying to close the socket connection aby arulmarans - Nginx Mailing List - English