Re: Worker processes not shutting down

2014-09-23 Thread Yichun Zhang (agentzh)
Hello! On Fri, Sep 19, 2014 at 12:50 PM, igorhmm wrote: > 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 worker

Re: Worker processes not shutting down

2014-09-23 Thread igorhmm
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

Re: Worker processes not shutting down

2014-09-20 Thread Dewangga
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Which one do you use to reloading the config? `restart` or `reload` command? On 9/20/2014 02:50, igorhmm wrote: > Hi BR, > > I don't known how to reproduce, not yet :-) > > I couldn't identify which worker was responding too, but I can see > wi

Re: Worker processes not shutting down

2014-09-20 Thread oscaretu .
Hello As another tool to analyze the problem similar to strace but more powerful, I suggest you to try sysdig http://www.sysdig.org/ https://www.google.com/search?client=ubuntu&channel=fs&q=sysdig&ie=utf-8&oe=utf-8 You can do a trace of everything in your system. Greetings, Oscar On Fri

Re: Worker processes not shutting down

2014-09-19 Thread B.R.
Any hanging/error should be available in your log files. Cross-check access and error logs and you will probably find unusual entries you seek for. --- *B. R.* On Fri, Sep 19, 2014 at 9:50 PM, igorhmm wrote: > Hi BR, > > I don't known how to reproduce, not yet :-) > > I couldn't identify which

Re: Worker processes not shutting down

2014-09-19 Thread igorhmm
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 %MEMVSZ RSS TT

Re: Worker processes not shutting down

2014-09-19 Thread 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 d

Re: Worker processes not shutting down

2014-09-19 Thread igorhmm
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, b

Re: Worker processes not shutting down

2014-09-19 Thread B.R.
Hello, You should read the end of the 1st paragraph of the following section to find your answer: http://nginx.org/en/docs/control.html#reconfiguration If you do not wish to reach all the workers' 'graceful shutdown' conditions, look at the list of signals they handle to find out how to force it:

Re: Worker processes not shutting down

2014-09-19 Thread igorhmm
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? Thanks Posted at Nginx Forum: http://forum.nginx.org/read.php?2,221591,2534