unable to obtain neither an IPv4 nor an IPv6 dispatch
I'm completely new to BIND configuration. I'm running on BIND 9.9.5-3-Ubuntu (Extended Support Version) on Ubuntu 14.04 and seeing this error on startup/reload. Jul 15 19:20:57 named[1978]: server.c:2772: unexpected error: Jul 15 19:20:57 named[1978]: unable to obtain neither an IPv4 nor an IPv6 dispatch This happens if I do rndc reload/reconfig. My named.conf.local has many around 500 views and large match-client ACLs because I am experimenting with a global split-horizon configuration. I would appreciate any help. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: unable to obtain neither an IPv4 nor an IPv6 dispatch
Thanks Mark. I tried building with increased ISC_SOCKET_MAXSOCKETS with BIND 9.9.5 but I kept seeing the same error. Eventually, I tried BIND 9.10.0 and the error no longer happens. On Wed, Jul 16, 2014 at 3:56 PM, Mark Andrews wrote: > > You need to increase ISC_SOCKET_MAXSOCKETS. > > e.g. > > ./configure STC_CDEFINES=-DISC_SOCKET_MAXSOCKETS=21000 > > In message < > cancffbvv2wktdc-dtzzcecc4gif1nfvgqvq-kxqgptex6++...@mail.gmail.com> > , Matthew Calder writes: > > --===1218088129802327245== > > Content-Type: multipart/alternative; > boundary=089e013a044a72db8004fe551784 > > > > --089e013a044a72db8004fe551784 > > Content-Type: text/plain; charset=UTF-8 > > > > I'm completely new to BIND configuration. I'm running on BIND > > 9.9.5-3-Ubuntu (Extended Support Version) on Ubuntu 14.04 and seeing this > > error on startup/reload. > > > > Jul 15 19:20:57 named[1978]: server.c:2772: unexpected error: > > Jul 15 19:20:57 named[1978]: unable to obtain neither an IPv4 nor an IPv6 > > dispatch > > > > This happens if I do rndc reload/reconfig. My named.conf.local has > > many around 500 views and large match-client ACLs because I am > > experimenting with a global split-horizon configuration. I would > appreciate > > any help. > > > > --089e013a044a72db8004fe551784 > > Content-Type: text/html; charset=UTF-8 > > Content-Transfer-Encoding: quoted-printable > > > > style=3D"color:windowtext;line-height:17px;font= > > -family:Calibri,Sans-Serif;font-size:11pt"> style=3D"background-color:= > > inherit">I'm completely new to BIND configuration. I'm running > on <= > > span > style=3D"color:windowtext;line-height:17px;font-family:Calibri,Sans-Se= > > rif;font-size:11pt">BIND > 9.9.5-3-U= > > buntu (Extended Support Version) on Ubuntu 14.04 and seeing this error > on s= > > tartup/reload. > > style=3D"color:windowtext;line-height:17px;font-family:Calibri,S= > > ans-Serif;font-size:11pt"> style=3D"background-color:inherit"><= > > /span> style=3D"color:windowtext;line-height:17px;font-= > > family:Calibri,Sans-Serif;font-size:11pt"> style=3D"background-color:i= > > nherit">Jul 15 19:20:57 > nam= > > ed[1978]: server.c:2772: unexpected error: style=3D"line= > > > -height:17px;font-family:Calibri,Sans-Serif;font-size:11pt">=C2=A0 > pan> > > style=3D"color:windowtext;line-height:17px;font-family:Calibri= > > ,Sans-Serif;font-size:11pt">Jul > 15= > > 19:20:57 named[1978]: > unab= > > le to obtain neither an IPv4 nor an IPv6 dispatch > > style=3D"color:windowtext;line-height:17px;font-family:Calibri,S= > > ans-Serif;font-size:11pt"> style=3D"background-color:inherit"><= > > /span> style=3D"color:windowtext;line-height:17px;font-= > > family:Calibri,Sans-Serif;font-size:11pt"> style=3D"background-color:i= > > nherit"> style=3D"color:windowtext;line-height:17px;font-family:Calibr= > > i,Sans-Serif;font-size:11pt"> style=3D"background-color:inherit">This = > > happens if I do rndc reload/reconfig. sty= > > > le=3D"color:windowtext;line-height:17px;font-family:Calibri,Sans-Serif;font= > > -size:11pt">My named.conf.local > ha= > > s many=C2=A0around=C2=A0500 views=C2=A0and large match-client ACLs > because = > > I am experimenting with a global split-horizon configuration. I would > appre= > > ciate any help. > > > > > > --089e013a044a72db8004fe551784-- > > > > --===1218088129802327245== > > Content-Type: text/plain; charset="us-ascii" > > MIME-Version: 1.0 > > Content-Transfer-Encoding: 7bit > > Content-Disposition: inline > > > > ___ > > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe > > from this list > > > > bind-users mailing list > > bind-users@lists.isc.org > > https://lists.isc.org/mailman/listinfo/bind-users > > --===1218088129802327245==-- > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org > ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: unable to obtain neither an IPv4 nor an IPv6 dispatch
Hi Cathy, I think you may be correct. I am running these in cloud hosted VMs. I found that the problem is difficult to reproduce with a 2 core instance. With a 4 core instance it only happens with reload/reconfig and with 8 cores it doesn't get past start up. From the VM's perspective, I only have 2 interfaces, lo and eth0. Here is what shows up in the logs for BIND 9.9.5 on start. Jul 18 18:42:39 named[11861]: adjusted limit on open files from 4096 to 1048576 Jul 18 18:42:39 named[11861]: found 4 CPUs, using 4 worker threads Jul 18 18:42:39 named[11861]: using 4 UDP listeners per interface Jul 18 18:42:39 named[11861]: using up to 4096 sockets Jul 18 18:42:39 named[11861]: loading configuration from '/etc/bind/named.conf' Jul 18 18:42:45 named[11861]: reading built-in trusted keys from file '/etc/bind/bind.keys' Jul 18 18:42:45 named[11861]: using default UDP/IPv4 port range: [1024, 65535] Jul 18 18:42:45 named[11861]: using default UDP/IPv6 port range: [1024, 65535] Jul 18 18:42:45 named[11861]: listening on IPv6 interfaces, port 53 Jul 18 18:42:45 named[11861]: listening on IPv4 interface lo, 127.0.0.1#53 Jul 18 18:42:45 named[11861]: listening on IPv4 interface eth0, 100.67.236.8#53 On Fri, Jul 18, 2014 at 8:20 AM, Cathy Almond wrote: > It might have something to do with the number of CPUs that named detects > when it starts, which (by default) drives how many listening tasks it > starts per listening interface. > > BIND 9.10 changed the defaults slightly, but you can also control how > many listening tasks per interface using the -U option. > > Is there anything else unusual in your test set-up? I notice you said > that you have 500 views - do you also have a large number of virtual > interfaces, each with their own listen-on? > > > On 18/07/2014 07:06, Matthew Calder wrote: > > Thanks Mark. I tried building with increased ISC_SOCKET_MAXSOCKETS with > > BIND 9.9.5 but I kept seeing the same error. Eventually, I tried BIND > > 9.10.0 and the error no longer happens. > > > > > > On Wed, Jul 16, 2014 at 3:56 PM, Mark Andrews > <mailto:ma...@isc.org>> wrote: > > > > > > You need to increase ISC_SOCKET_MAXSOCKETS. > > > > e.g. > > > > ./configure STC_CDEFINES=-DISC_SOCKET_MAXSOCKETS=21000 > > > > In message > > > cancffbvv2wktdc-dtzzcecc4gif1nfvgqvq-kxqgptex6%2b%2b...@mail.gmail.com>> > > , Matthew Calder writes: > > > --===1218088129802327245== > > > Content-Type: multipart/alternative; > > boundary=089e013a044a72db8004fe551784 > > > > > > --089e013a044a72db8004fe551784 > > > Content-Type: text/plain; charset=UTF-8 > > > > > > I'm completely new to BIND configuration. I'm running on BIND > > > 9.9.5-3-Ubuntu (Extended Support Version) on Ubuntu 14.04 and > > seeing this > > > error on startup/reload. > > > > > > Jul 15 19:20:57 named[1978]: server.c:2772: unexpected error: > > > Jul 15 19:20:57 named[1978]: unable to obtain neither an IPv4 nor > > an IPv6 > > > dispatch > > > > > > This happens if I do rndc reload/reconfig. My named.conf.local has > > > many around 500 views and large match-client ACLs because I am > > > experimenting with a global split-horizon configuration. I would > > appreciate > > > any help. > > > > > > --089e013a044a72db8004fe551784 > > > Content-Type: text/html; charset=UTF-8 > > > Content-Transfer-Encoding: quoted-printable > > > > > > > style=3D"color:windowtext;line-height:17px;font= > > > -family:Calibri,Sans-Serif;font-size:11pt"> > style=3D"background-color:= > > > inherit">I'm completely new to BIND configuration. I'm > > running on <= > > > span > > > style=3D"color:windowtext;line-height:17px;font-family:Calibri,Sans-Se= > > > rif;font-size:11pt">BIND > > 9.9.5-3-U= > > > buntu (Extended Support Version) on Ubuntu 14.04 and seeing this > > error on s= > > > tartup/reload. > > > > style=3D"color:windowtext;line-height:17px;font-family:Calibri,S= > > > ans-Serif;font-size:11pt"> > style=3D"background-color:inherit"><= > > > /span> > style=3D"color:windowtext;line-height:17px;font-= > > > family:Calibri,Sans-Serif;font-size:11pt"> > style=3D"background-color
Re: unable to obtain neither an IPv4 nor an IPv6 dispatch
At the moment I'm limited to using 2 UDP listeners per interface. When stress testing I can see that only 2 out of 4 CPUs are being used, I'm guessing because I'm limited to 2 listeners. Any suggestions for what could be limiting BIND from using a higher number of UDP listeners? On Fri, Jul 18, 2014 at 11:46 AM, Matthew Calder wrote: > Hi Cathy, > > I think you may be correct. I am running these in cloud hosted VMs. I > found that the problem is difficult to reproduce with a 2 core instance. > With a 4 core instance it only happens with reload/reconfig and with 8 > cores it doesn't get past start up. From the VM's perspective, I only have > 2 interfaces, lo and eth0. > > Here is what shows up in the logs for BIND 9.9.5 on start. > > Jul 18 18:42:39 named[11861]: adjusted limit on open files from 4096 to > 1048576 > Jul 18 18:42:39 named[11861]: found 4 CPUs, using 4 worker threads > Jul 18 18:42:39 named[11861]: using 4 UDP listeners per interface > Jul 18 18:42:39 named[11861]: using up to 4096 sockets > Jul 18 18:42:39 named[11861]: loading configuration from > '/etc/bind/named.conf' > Jul 18 18:42:45 named[11861]: reading built-in trusted keys from file > '/etc/bind/bind.keys' > Jul 18 18:42:45 named[11861]: using default UDP/IPv4 port range: [1024, > 65535] > Jul 18 18:42:45 named[11861]: using default UDP/IPv6 port range: [1024, > 65535] > Jul 18 18:42:45 named[11861]: listening on IPv6 interfaces, port 53 > Jul 18 18:42:45 named[11861]: listening on IPv4 interface lo, 127.0.0.1#53 > Jul 18 18:42:45 named[11861]: listening on IPv4 interface eth0, > 100.67.236.8#53 > > > > On Fri, Jul 18, 2014 at 8:20 AM, Cathy Almond wrote: > >> It might have something to do with the number of CPUs that named detects >> when it starts, which (by default) drives how many listening tasks it >> starts per listening interface. >> >> BIND 9.10 changed the defaults slightly, but you can also control how >> many listening tasks per interface using the -U option. >> >> Is there anything else unusual in your test set-up? I notice you said >> that you have 500 views - do you also have a large number of virtual >> interfaces, each with their own listen-on? >> >> >> On 18/07/2014 07:06, Matthew Calder wrote: >> > Thanks Mark. I tried building with increased ISC_SOCKET_MAXSOCKETS with >> > BIND 9.9.5 but I kept seeing the same error. Eventually, I tried BIND >> > 9.10.0 and the error no longer happens. >> > >> > >> > On Wed, Jul 16, 2014 at 3:56 PM, Mark Andrews > > <mailto:ma...@isc.org>> wrote: >> > >> > >> > You need to increase ISC_SOCKET_MAXSOCKETS. >> > >> > e.g. >> > >> > ./configure STC_CDEFINES=-DISC_SOCKET_MAXSOCKETS=21000 >> > >> > In message >> > > > > cancffbvv2wktdc-dtzzcecc4gif1nfvgqvq-kxqgptex6%2b%2b...@mail.gmail.com>> >> > , Matthew Calder writes: >> > > --===1218088129802327245== >> > > Content-Type: multipart/alternative; >> > boundary=089e013a044a72db8004fe551784 >> > > >> > > --089e013a044a72db8004fe551784 >> > > Content-Type: text/plain; charset=UTF-8 >> > > >> > > I'm completely new to BIND configuration. I'm running on BIND >> > > 9.9.5-3-Ubuntu (Extended Support Version) on Ubuntu 14.04 and >> > seeing this >> > > error on startup/reload. >> > > >> > > Jul 15 19:20:57 named[1978]: server.c:2772: unexpected error: >> > > Jul 15 19:20:57 named[1978]: unable to obtain neither an IPv4 nor >> > an IPv6 >> > > dispatch >> > > >> > > This happens if I do rndc reload/reconfig. My named.conf.local has >> > > many around 500 views and large match-client ACLs because I am >> > > experimenting with a global split-horizon configuration. I would >> > appreciate >> > > any help. >> > > >> > > --089e013a044a72db8004fe551784 >> > > Content-Type: text/html; charset=UTF-8 >> > > Content-Transfer-Encoding: quoted-printable >> > > >> > > > > style=3D"color:windowtext;line-height:17px;font= >> > > -family:Calibri,Sans-Serif;font-size:11pt">> > style=3D"background-color:= >> > > inherit">I'm completely new to BIND configuration. I'm >> >
