Am 11-02-2014 18:56, schrieb Valentin V. Bartenev:
On Tuesday 11 February 2014 16:44:57 Aleksandar Lazic wrote:
Am 11-02-2014 16:28, schrieb Valentin V. Bartenev:
> On Tuesday 11 February 2014 19:06:37 Maxim Dounin wrote:
>> Hello!
>>
>> On Tue, Feb 11, 2014 at 06:16:48PM +0400, Valentin V. B
On Tuesday 11 February 2014 16:44:57 Aleksandar Lazic wrote:
>
> Am 11-02-2014 16:28, schrieb Valentin V. Bartenev:
> > On Tuesday 11 February 2014 19:06:37 Maxim Dounin wrote:
> >> Hello!
> >>
> >> On Tue, Feb 11, 2014 at 06:16:48PM +0400, Valentin V. Bartenev wrote:
> >>
> >> > On Tuesday 11 F
On Tuesday 11 February 2014 20:29:25 Maxim Dounin wrote:
> Hello!
>
> On Tue, Feb 11, 2014 at 07:28:43PM +0400, Valentin V. Bartenev wrote:
>
> > On Tuesday 11 February 2014 19:06:37 Maxim Dounin wrote:
> > > Hello!
> > >
> > > On Tue, Feb 11, 2014 at 06:16:48PM +0400, Valentin V. Bartenev wrote
Hello!
On Tue, Feb 11, 2014 at 07:28:43PM +0400, Valentin V. Bartenev wrote:
> On Tuesday 11 February 2014 19:06:37 Maxim Dounin wrote:
> > Hello!
> >
> > On Tue, Feb 11, 2014 at 06:16:48PM +0400, Valentin V. Bartenev wrote:
> >
> > > On Tuesday 11 February 2014 18:06:38 Maxim Dounin wrote:
> >
Am 11-02-2014 16:28, schrieb Valentin V. Bartenev:
On Tuesday 11 February 2014 19:06:37 Maxim Dounin wrote:
Hello!
On Tue, Feb 11, 2014 at 06:16:48PM +0400, Valentin V. Bartenev wrote:
> On Tuesday 11 February 2014 18:06:38 Maxim Dounin wrote:
> [..]
> > > >(As for backlog size, I usually set
On Tuesday 11 February 2014 19:06:37 Maxim Dounin wrote:
> Hello!
>
> On Tue, Feb 11, 2014 at 06:16:48PM +0400, Valentin V. Bartenev wrote:
>
> > On Tuesday 11 February 2014 18:06:38 Maxim Dounin wrote:
> > [..]
> > > > >(As for backlog size, I usually set it to something big enough to
> > > > >a
Hello!
On Tue, Feb 11, 2014 at 06:16:48PM +0400, Valentin V. Bartenev wrote:
> On Tuesday 11 February 2014 18:06:38 Maxim Dounin wrote:
> [..]
> > > >(As for backlog size, I usually set it to something big enough to
> > > >accomodate about 1 or 2 seconds of expected peek connection rate.
> > > >T
On Tuesday 11 February 2014 18:06:38 Maxim Dounin wrote:
[..]
> > >(As for backlog size, I usually set it to something big enough to
> > >accomodate about 1 or 2 seconds of expected peek connection rate.
> > >That is, 1024 is good enough for about 500 connections per second.
> > >But with deferred
Hello!
On Tue, Feb 11, 2014 at 02:14:14PM +0100, Aleksandar Lazic wrote:
> Hi.
>
> Am 11-02-2014 13:28, schrieb Maxim Dounin:
> >Hello!
> >
> >On Tue, Feb 11, 2014 at 01:10:59PM +0100, Aleksandar Lazic wrote:
> >
> >>
> >>Am 11-02-2014 12:48, schrieb Maxim Dounin:
> >>>Hello!
> >>>
> >>>On Tue,
Hi.
Am 11-02-2014 13:28, schrieb Maxim Dounin:
Hello!
On Tue, Feb 11, 2014 at 01:10:59PM +0100, Aleksandar Lazic wrote:
Am 11-02-2014 12:48, schrieb Maxim Dounin:
>Hello!
>
>On Tue, Feb 11, 2014 at 12:34:59PM +0100, Aleksandar Lazic wrote:
>
[snipp]
>>>You haven't shown your server level c
Hello!
On Tue, Feb 11, 2014 at 01:10:59PM +0100, Aleksandar Lazic wrote:
>
> Am 11-02-2014 12:48, schrieb Maxim Dounin:
> >Hello!
> >
> >On Tue, Feb 11, 2014 at 12:34:59PM +0100, Aleksandar Lazic wrote:
> >
>
> [snipp]
>
> >>>You haven't shown your server level configuration.
> >>>Do you use d
Am 11-02-2014 12:48, schrieb Maxim Dounin:
Hello!
On Tue, Feb 11, 2014 at 12:34:59PM +0100, Aleksandar Lazic wrote:
[snipp]
>You haven't shown your server level configuration.
>Do you use deferred accept?
yes
listen :80 deferred default_server;
Try switching it off, there could b
Am 11-02-2014 12:45, schrieb Valentin V. Bartenev:
On Tuesday 11 February 2014 12:34:59 Aleksandar Lazic wrote:
[..]
>
> You haven't shown your server level configuration.
> Do you use deferred accept?
yes
listen :80 deferred default_server;
Ok. Two other guesses: you have tcp_sync
Hello!
On Tue, Feb 11, 2014 at 12:34:59PM +0100, Aleksandar Lazic wrote:
>
>
> Am 11-02-2014 12:14, schrieb Valentin V. Bartenev:
> >On Monday 10 February 2014 17:41:47 Aleksandar Lazic wrote:
>
> [snipp]
>
> >>Every time when I have more then ~400 r/s we get no data from the
> >>status-reque
On Tuesday 11 February 2014 12:34:59 Aleksandar Lazic wrote:
[..]
> >
> > You haven't shown your server level configuration.
> > Do you use deferred accept?
>
> yes
>
> listen :80 deferred default_server;
>
Ok. Two other guesses: you have tcp_syncookies disabled,
and tcp_abort_on_overfl
Am 11-02-2014 12:15, schrieb Maxim Dounin:
Hello!
On Mon, Feb 10, 2014 at 05:41:47PM +0100, Aleksandar Lazic wrote:
[...]
Every time when I have more then ~400 r/s we get no data from the
status-request, this request rate means ~20k Packets/Second.
I use netfilter with fail2ban, but not the
Am 11-02-2014 12:14, schrieb Valentin V. Bartenev:
On Monday 10 February 2014 17:41:47 Aleksandar Lazic wrote:
[snipp]
Every time when I have more then ~400 r/s we get no data from the
status-request, this request rate means ~20k Packets/Second.
I use netfilter with fail2ban, but not the co
On Monday 10 February 2014 17:41:47 Aleksandar Lazic wrote:
> Hi Jonathan.
>
> Sorry to be unclear, thanks for answer and question.
>
> Am 10-02-2014 16:37, schrieb Jonathan Matthews:
> > On 10 February 2014 12:06, Aleksandar Lazic wrote:
> >> Thanks for help.
> >
> > Aleksandar - I can't work
Hello!
On Mon, Feb 10, 2014 at 05:41:47PM +0100, Aleksandar Lazic wrote:
[...]
> Every time when I have more then ~400 r/s we get no data from the
> status-request, this request rate means ~20k Packets/Second.
> I use netfilter with fail2ban, but not the connection tracking module!
>
> I have n
Hi Jonathan.
Sorry to be unclear, thanks for answer and question.
Am 10-02-2014 16:37, schrieb Jonathan Matthews:
On 10 February 2014 12:06, Aleksandar Lazic wrote:
Thanks for help.
Aleksandar - I can't work out what you need help with. There aren't
any questions (or question marks!) in you
On 10 February 2014 12:06, Aleksandar Lazic wrote:
> Thanks for help.
Aleksandar - I can't work out what you need help with. There aren't
any questions (or question marks!) in your email :-)
I can't see your problem at first or second glance; I'm sure others
will, but I'm quite slow. Could you s
Dear list member.
currently we have a huge traffic come up.
~500 r/s
http://download.none.at/nginx_request-day.png
~3.5K active connections
http://download.none.at/port_www-day.png
http://download.none.at/nginx_combined.png
The Peaks are the raw values from module status.
~1.1g b/s traffic
ht
22 matches
Mail list logo
