Hello Mathew,
On Sat, Apr 02, 2016 at 03:16:59PM +0200, Michael Brunnbauer wrote:
> > # watch -n 0.1 'cat /proc/net/udp | grep ":0035 : "'
>
> I can see the error count on the lo interface growing when the queue is at
>
> :00040200
I should have guessed that restarting bin
t.ipv4.tcp_fin_timeout = 30
> net.ipv4.tcp_tw_recycle = 1
>
> Mike Mitchell
>
>
> From: bind-users-boun...@lists.isc.org on
> behalf of Michael Brunnbauer
> Sent: Friday, April 1, 2016 12:29 PM
> To: Mathew Ian Eis
> Cc: d..
Hello Mathew,
On Sat, Apr 02, 2016 at 12:02:38AM +, Mathew Ian Eis wrote:
> * You can check for dropped packets on the receive path with # netstat -u -s
> High numbers on "packet receive errors??? can indicate an overflow in the
> receive buffer - this is fixable by network stack tuning as M
@nau.edu
(928) 523-2960
-Original Message-
From: Michael Brunnbauer
Date: Friday, April 1, 2016 at 9:29 AM
To: Mathew Eis
Cc: "bind-users@lists.isc.org" ,
Subject: Re: Recursive bind becomes unresponsive with high load
>
>Hello Mathew,
>
>On Fri, Apr 01, 2016 at
On Fri, Apr 01, 2016 at 09:48:01PM +, Mike Mitchell wrote:
> Have you checked the Kernel's connection tracking statistics?
> Here's a link:
> https://kb.isc.org/article/AA-01183/0/Linux-connection-tracking-and-DNS.html
>
> I've had to increase some network parameters on our busy
> nameservers
Mike Mitchell
From: bind-users-boun...@lists.isc.org on
behalf of Michael Brunnbauer
Sent: Friday, April 1, 2016 12:29 PM
To: Mathew Ian Eis
Cc: d...@dotat.at; bind-users@lists.isc.org
Subject: Re: Recursive bind becomes unresponsive with high load
Hello Mathew,
On Fri,
Hello Mathew,
On Fri, Apr 01, 2016 at 04:01:04PM +, Mathew Ian Eis wrote:
> What OS are you running your BIND server on? Is it virtualized?
Linux Kernel 3.4.111 with glibc 2.22, 32bit, not virtualized. No distribution -
everything was compiled by hand.
> Is it fully unresponsive, or could i
-Original Message-
From: on behalf of Michael Brunnbauer
Date: Thursday, March 31, 2016 at 8:57 AM
To: "bind-users@lists.isc.org"
Subject: Recursive bind becomes unresponsive with high load
>
>hi all,
>
>I am using bind on a server that does massive crawling with a multithr
sth...@nethelp.no wrote:
>
> Have you checked your operating system limits? One recursive client
> often means one open socket (waiting for response from authoritative
> server), i.e. one open file descriptor. If you have thousands of
> simultaneous recursive clients, you will need a corresponding
On Thu, Mar 31, 2016 at 2:00 PM, Michael Brunnbauer wrote:
>
> hi all,
>
> On Thu, Mar 31, 2016 at 07:32:21PM +0200, Michael Brunnbauer wrote:
>> Is is possible that is this connected to rndc stats? I will stop doing
>> rndc stats for a while to test (it currently runs every minute).
>
> Not doing
hi all,
On Thu, Mar 31, 2016 at 07:32:21PM +0200, Michael Brunnbauer wrote:
> Is is possible that is this connected to rndc stats? I will stop doing
> rndc stats for a while to test (it currently runs every minute).
Not doing rndc stats did not prevent the problem. Any other ideas?
Regards,
Mi
Hello Steinar,
On Thu, Mar 31, 2016 at 07:35:39PM +0200, sth...@nethelp.no wrote:
> Have you checked your operating system limits? One recursive client
> often means one open socket (waiting for response from authoritative
> server), i.e. one open file descriptor. If you have thousands of
> simul
> > If you are crawling lots of new names, the cache size won't have much
> > impact. Each new query will require recursing vs hitting the cache. Try
> > "rndc recursing" and look at what you have sitting around waiting for
> > answers. Hopefully that provides some clues. This can be all sorts
Hello Tony,
On Thu, Mar 31, 2016 at 05:08:43PM +0100, Tony Finch wrote:
> Michael Brunnbauer wrote:
> >
> > I am using bind on a server that does massive crawling with a multithreaded
> > Java app. This server occasionally has to do lookups for hosts in our local
> > zone netestate.de - for whic
Hello Mike,
On Thu, Mar 31, 2016 at 04:05:39PM +, Mike Hoskins (michoski) wrote:
> If you are crawling lots of new names, the cache size won't have much
> impact. Each new query will require recursing vs hitting the cache. Try
> "rndc recursing" and look at what you have sitting around wait
Michael Brunnbauer wrote:
>
> I am using bind on a server that does massive crawling with a multithreaded
> Java app. This server occasionally has to do lookups for hosts in our local
> zone netestate.de - for which it is not authoritative - and those lookups tend
> to fail when the load is high (
If you are crawling lots of new names, the cache size won't have much
impact. Each new query will require recursing vs hitting the cache. Try
"rndc recursing" and look at what you have sitting around waiting for
answers. Hopefully that provides some clues. This can be all sorts of
things like u
hi all,
I am using bind on a server that does massive crawling with a multithreaded
Java app. This server occasionally has to do lookups for hosts in our local
zone netestate.de - for which it is not authoritative - and those lookups tend
to fail when the load is high (e.g. >1000 recursing clien
18 matches
Mail list logo
