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 Acce
Hello!
On Thu, Oct 30, 2014 at 10:54:38AM -0400, arulmarans wrote:
> Hi Maxim Dounin,
>
> I have gone through those steps, still i was not able to catch the backtrace
> in the gdb.
You may start with providing "nginx -V" output, as recommended at
http://wiki.nginx.org/Debugging#Asking_for_hel
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 [debug] 16259#0: *2 posix_memalign: 025B6980:4096
@16
2014/10/30 13:54:07 [debug] 16259#0: *2 add cleanup: 025BF6A0
2014/10/30 13:54:07 [debu
I have already gone through that link, still gdb was not catching core
dump...
Log snippet:
2014/10/30 13:54:07 [debug] 16259#0: *2 http static fd: 11
2014/10/30 13:54:07 [debug] 16259#0: *2 http set discard body
2014/10/30 13:54:07 [debug] 16259#0: *2 HTTP/1.1 200 OK^M
Server: nginx/1.7.6^M
Dat
Hello!
On Thu, Oct 30, 2014 at 08:17:41AM -0400, arulmarans wrote:
> 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,
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
