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
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
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
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
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:
Can you figure out when the error appears? Maybe it appears when the file is
downloaded
from backend and written to cache (if you have one) or when serving from cache
etc.
On 19 Sep 2014, at 14:46, shahzaib shahzaib wrote:
> Nope, it doesn't !!
>
> On Fri, Sep 19, 2014 at 3:42 PM, Roman Arut
On Friday 19 September 2014 15:20:02 Rob Stradling wrote:
> On 19/09/14 14:14, shm...@riseup.net wrote:
> > hi rob,
> >
> > Rob Stradling wrote:
> >> On 17/09/14 16:17, shm...@riseup.net wrote:
> >>> it works with postfix
> >>> i guess not in nginx
> >>> feature request ?
> >>
> >> Hi. You could t
On 19/09/14 14:14, shm...@riseup.net wrote:
hi rob,
Rob Stradling wrote:
On 17/09/14 16:17, shm...@riseup.net wrote:
it works with postfix
i guess not in nginx
feature request ?
Hi. You could try this patch:
http://forum.nginx.org/read.php?29,243797,244306#msg-244306
many thanks
sorry bu
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
hi rob,
Rob Stradling wrote:
> On 17/09/14 16:17, shm...@riseup.net wrote:
>> it works with postfix
>> i guess not in nginx
>> feature request ?
>
> Hi. You could try this patch:
>
> http://forum.nginx.org/read.php?29,243797,244306#msg-244306
many thanks
sorry but am i missing something ?
i ca
Nope, it doesn't !!
On Fri, Sep 19, 2014 at 3:42 PM, Roman Arutyunyan wrote:
> Will this error appear if you try this request again?
>
> On 17 Sep 2014, at 16:29, shahzaib shahzaib wrote:
>
> > Well, i again received the same error but its much improvement in time
> frame. If the error was occu
Will this error appear if you try this request again?
On 17 Sep 2014, at 16:29, shahzaib shahzaib wrote:
> Well, i again received the same error but its much improvement in time frame.
> If the error was occurring after each 5min, now the same error is occurring
> after 30~50min.
>
> The conc
Hello!
On Thu, Sep 18, 2014 at 08:45:32PM -0400, idabic wrote:
> I have bounced around quite a lot through forums and documentation to
> demistique whether the OPTIONS request method is honoured/allowed by nginx
> when it's configured as reverse proxy cache system or not.
> I used a test box with
13 matches
Mail list logo
