Worker processes not shutting down

[B.R.]

Are you able to reproduce the problem? Could you provide steps to do so?

Based on what you said, I would suspect a conflict between new and old
workers. I do not see in your report where the problem could come from. I
suppose it is related, then.

Do you know which worker was receiving data?
Why did the problem solve itself? Did that happen at the same time as the
old workers finally died?

What is the difference between handling HTTP and HTTPS in your
configuration? Is there any difference on that particular point between old
and new configuration?
---
*B. R.*

On Fri, Sep 19, 2014 at 7:27 PM, igorhmm <nginx-forum at nginx.us> wrote:

> 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 position,
> the old worker is waiting all sockets to be closed to quit. That's it?
>
> But why this user still without response from http for a long period (more
> then 20 minutes)? After that, everything come back to work fine.
>
> Thanks again
>
> Igor
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,221591,253428#msg-253428
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140919/db88728d/attachment-0001.html>