<div dir="ltr"><div><div><div><div>Hello<br><br></div>As another tool to analyze the problem similar to strace but more powerful, I suggest you to try sysdig<br><br> <a href="http://www.sysdig.org/">http://www.sysdig.org/</a><br> <a href="https://www.google.com/search?client=ubuntu&channel=fs&q=sysdig&ie=utf-8&oe=utf-8">https://www.google.com/search?client=ubuntu&channel=fs&q=sysdig&ie=utf-8&oe=utf-8</a><br><br></div>You can do a trace of everything in your system.<br><br></div>Greetings,<br><br></div>Oscar<br><div><div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 19, 2014 at 9:50 PM, igorhmm <span dir="ltr"><<a href="mailto:nginx-forum@nginx.us" target="_blank">nginx-forum@nginx.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi BR,<br>
<br>
I don't known how to reproduce, not yet :-)<br>
<br>
I couldn't identify which worker was responding too, but I can see with<br>
strace warnings in the old wolker about EAGAIN (Resource temporarily<br>
unavailable). I can see that because old workers still running:<br>
<br>
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND<br>
nginx 6009 0.0 0.2 71020 18532 ? S Sep18 0:37 nginx:<br>
<span class="">worker process is shutting down<br>
</span>nginx 6010 0.0 0.2 71028 18496 ? S Sep18 0:12 nginx:<br>
<span class="">worker process is shutting down<br>
</span>nginx 6289 0.2 0.3 75672 23188 ? S 07:54 0:58 nginx:<br>
<span class="">worker process is shutting down<br>
</span>nginx 6290 0.0 0.2 71932 19248 ? S 07:54 0:15 nginx:<br>
<span class="">worker process is shutting down<br>
</span>nginx 9182 0.0 0.2 70872 18380 ? S 10:20 0:02 nginx:<br>
<span class="">worker process is shutting down<br>
</span>nginx 9295 0.0 0.2 70952 18380 ? S 10:26 0:02 nginx:<br>
<span class="">worker process is shutting down<br>
</span>nginx 9297 0.0 0.2 70368 17856 ? S 10:26 0:02 nginx:<br>
<span class="">worker process is shutting down<br>
</span>nginx 9302 0.0 0.2 70804 18296 ? S 10:26 0:01 nginx:<br>
<span class="">worker process is shutting down<br>
</span>nginx 10132 0.2 0.2 74776 22280 ? S 10:53 0:47 nginx:<br>
<span class="">worker process is shutting down<br>
</span>nginx 10133 0.0 0.2 71484 18972 ? S 10:53 0:09 nginx:<br>
<span class="">worker process is shutting down<br>
</span>nginx 13690 0.2 0.2 72876 20296 ? S 14:22 0:10 nginx:<br>
worker process<br>
nginx 13691 0.1 0.2 71492 19088 ? S 14:22 0:07 nginx:<br>
worker process<br>
nginx 13692 0.0 0.0 57292 3180 ? S 14:22 0:00 nginx:<br>
cache manager process<br>
root 29863 0.0 0.0 57292 4048 ? Ss Sep11 0:00 nginx:<br>
<span class="">master process /usr/sbin/nginx -c /etc/nginx/nginx.conf<br>
</span>nginx 30956 0.0 0.2 72924 20336 ? S Sep18 0:23 nginx:<br>
<span class="">worker process is shutting down<br>
</span>[/code]<br>
<br>
Looking for our user's usage, this workers will stay online for more few<br>
hours :)<br>
<br>
The difference between old and new configuration is just a "down" flag in<br>
one of our servers from our websockets pool (upstream). You can see a<br>
simplified version of config on: <a href="http://pastebin.com/02GQQ22r" target="_blank">http://pastebin.com/02GQQ22r</a><br>
<br>
Really thanks for your attention.<br>
<br>
Igor<br>
<br>
Posted at Nginx Forum: <a href="http://forum.nginx.org/read.php?2,221591,253431#msg-253431" target="_blank">http://forum.nginx.org/read.php?2,221591,253431#msg-253431</a><br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Oscar Fernandez Sierra<br><a href="mailto:oscaretu@gmail.com">oscaretu@gmail.com</a>
</div>