Hi people, @BR: I not found anything on logs related to this problem, but I still investigating and trying to reproduce. @oscaretu: this looks a nice tool, thanks for recommendation @dewanggaba: I'm using the reload command. We can't use restart because this will kill all established connections Thanks for allby igorhmm - Nginx Mailing List - English
Hi BR, I don't known how to reproduce, not yet :-) I couldn't identify which worker was responding too, but I can see with strace warnings in the old wolker about EAGAIN (Resource temporarily unavailable). I can see that because old workers still running: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND nginx 6009 0.0 0.2 71020 18532 ? S Sep18 0by igorhmm - Nginx Mailing List - English
Hi BR, This helps a lot, but I can't find a explanation for my (temporary) problem. About a hour ago one of our developers can't access port 80, but everything goes fine with https. My nginx is listening http and https in the same server, With help of tcpdump, we could see packets coming in, but nothing getting out. In my newbie understanding, the new worker are ready and got the posby igorhmm - Nginx Mailing List - English
Hi, Did you solved that problem? I'm with the same issue using nginx/1.4.3. Could be related with websockets that are still connected? Some browsers can't connect until that worker be killed? This happens for you too? Thanksby igorhmm - Nginx Mailing List - English