Operating system recommendation
Hi, I want to know in your experience what is the best operating system to run bind for an ISP. We currently have Debian for the 5 Cache servers and for the 2 Authoritative servers. We have around 111851 success querys in the cache servers and around 7267 zones created in the authoritative servers. We are doing a major re analysis for all the arquitecture and Debian is changing to soon their versions and only have support for 1 version before so I dont know if this is best option Best regards and thanks ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
The thread is dead?
I do not see any activity in the thread... is everyone on holidays? Regards ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: socket: too many open file descriptors
On 4 dic, 19:43, Mark Andrews <[EMAIL PROTECTED]> wrote: > In message <[EMAIL PROTECTED]>, > > > > pollex writes: > > On 4 dic, 10:59, Mark Andrews <[EMAIL PROTECTED]> wrote: > > > =A0 =A0 =A0 =A0 --enable-threads=3Dyes > > > > In message <[EMAIL PROTECTED] > > com>, > > > > pollex writes: > > > > On 3 dic, 21:08, Mark Andrews <[EMAIL PROTECTED]> wrote: > > > > > In message <[EMAIL PROTECTED] > > ups.=3D > > > > com>, > > > > > > pollex writes: > > > > > > Hi Jinmei I have followed your advice and I have installed and > > > > > > compiled the Bind 9.3.6 with the following command: > > > > > > STD_CDEFINES=3D3D"-ISC_SOCKET_FDSETSIZE=3D3D4096" ./configure --pre= > > fix=3D3D/u=3D > > > > sr/ > > > > > > local/bind9.3.6 --enable-threads > > > > > > But now I have the following issue, I can't start bind with multi > > > > > > threading... > > > > > > I have in the init script the lines: > > > > > > OPTIONS=3D3D"-u bind -n 8 -t /var/lib/named -c /etc/bind/named.conf" > > > > > > and in the start part: > > > > > > mount --bind /proc/ /var/lib/named/proc/ -o ro (This is needed beca= > > use > > > > > > bin runs in jail) > > > > > > > Any idea? (With the previous version this works ok) > > > > > > =3DA0 =3DA0 =3DA0 =3DA0 Log messages would be useful. > > > > > > =3DA0 =3DA0 =3DA0 =3DA0 What does the following report? > > > > > =3DA0 =3DA0 =3DA0 =3DA0 "named -g -u bind -n 8 -t /var/lib/named -c /= > > etc/bind/nam=3D > > > > ed.conf" > > > > > > > Thanks for all > > > > > > > ___ > > > > > > bind-users mailing list > > > > > > [EMAIL PROTECTED] > > > > > >https://lists.isc.org/mailman/listinfo/bind-users > > > > > > -- > > > > > Mark Andrews, ISC > > > > > 1 Seymour St., Dundas Valley, NSW 2117, Australia > > > > > PHONE: +61 2 9871 4742 =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA0 =3DA= > > 0 INTERNET: Mark_And=3D > > > > [EMAIL PROTECTED] > > > > > ___ > > > > > bind-users mailing list > > > > > [EMAIL PROTECTED]://lists.isc.org/mailman/listinfo/bind-u= > > sers > > > > > Mark, thanks for the reply > > > > this is the report: > > > > 04-Dec-2008 09:52:54.950 starting BIND 9.3.6 -g -u bind -n 8 -t /var/ > > > > lib/named -c /etc/bind/named.conf > > > > 04-Dec-2008 09:52:54.950 using up to 4096 sockets > > > > 04-Dec-2008 09:52:54.954 loading configuration from '/etc/bind/ > > > > named.conf' > > > > 04-Dec-2008 09:52:54.956 using default UDP/IPv4 port range: [1024, > > > > 65535] > > > > 04-Dec-2008 09:52:54.956 using default UDP/IPv6 port range: [1024, > > > > 65535] > > > > 04-Dec-2008 09:52:54.958 listening on IPv4 interface lo, 127.0.0.1#53 > > > > 04-Dec-2008 09:52:54.958 could not listen on UDP socket: address in > > > > use > > > > 04-Dec-2008 09:52:54.958 creating IPv4 interface lo failed; interface > > > > > ignored > > > > 04-Dec-2008 09:52:54.958 listening on IPv4 interface eth1, > > > > ###.###.#.### #53 > > > > 04-Dec-2008 09:52:54.958 could not listen on UDP socket: address in > > > > use > > > > 04-Dec-2008 09:52:54.958 creating IPv4 interface eth1 failed; > > > > interface ignored > > > > 04-Dec-2008 09:52:54.958 not listening on any interfaces > > > > 04-Dec-2008 09:52:54.959 /etc/bind/named.conf:80: couldn't add command > > > > channel 127.0.0.1#953: address in use > > > > 04-Dec-2008 09:52:54.959 ignoring config file logging statement due to > > > > -g option > > > > 04-Dec-2008 09:52:54.960 additionally listening on IPv4 interface lo, > > > > 127.0.0.1#53 > > > > 04-Dec-2008 09:52:54.960 could not listen on UDP socket: address in > > > > use > > > > 04-Dec-2008 09:52:54.960 creating IPv4 interface lo failed; interface > > > > ignored > > > > 04-Dec-2008 09:52:54.960 additionally listening on IPv4 interface > > > > eth1, ###.###.#.### #53 > > > >
Re: socket: too many open file descriptors
On 4 dic, 10:59, Mark Andrews <[EMAIL PROTECTED]> wrote: > --enable-threads=yes > > In message <[EMAIL PROTECTED]>, > > pollex writes: > > On 3 dic, 21:08, Mark Andrews <[EMAIL PROTECTED]> wrote: > > > In message <[EMAIL PROTECTED] > > com>, > > > > pollex writes: > > > > Hi Jinmei I have followed your advice and I have installed and > > > > compiled the Bind 9.3.6 with the following command: > > > > STD_CDEFINES=3D"-ISC_SOCKET_FDSETSIZE=3D4096" ./configure --prefix=3D/u= > > sr/ > > > > local/bind9.3.6 --enable-threads > > > > But now I have the following issue, I can't start bind with multi > > > > threading... > > > > I have in the init script the lines: > > > > OPTIONS=3D"-u bind -n 8 -t /var/lib/named -c /etc/bind/named.conf" > > > > and in the start part: > > > > mount --bind /proc/ /var/lib/named/proc/ -o ro (This is needed because > > > > bin runs in jail) > > > > > Any idea? (With the previous version this works ok) > > > > =A0 =A0 =A0 =A0 Log messages would be useful. > > > > =A0 =A0 =A0 =A0 What does the following report? > > > =A0 =A0 =A0 =A0 "named -g -u bind -n 8 -t /var/lib/named -c /etc/bind/nam= > > ed.conf" > > > > > Thanks for all > > > > > ___ > > > > bind-users mailing list > > > > [EMAIL PROTECTED] > > > >https://lists.isc.org/mailman/listinfo/bind-users > > > > -- > > > Mark Andrews, ISC > > > 1 Seymour St., Dundas Valley, NSW 2117, Australia > > > PHONE: +61 2 9871 4742 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 INTERNET: Mark_And= > > [EMAIL PROTECTED] > > > ___ > > > bind-users mailing list > > > [EMAIL PROTECTED]://lists.isc.org/mailman/listinfo/bind-users > > > Mark, thanks for the reply > > this is the report: > > 04-Dec-2008 09:52:54.950 starting BIND 9.3.6 -g -u bind -n 8 -t /var/ > > lib/named -c /etc/bind/named.conf > > 04-Dec-2008 09:52:54.950 using up to 4096 sockets > > 04-Dec-2008 09:52:54.954 loading configuration from '/etc/bind/ > > named.conf' > > 04-Dec-2008 09:52:54.956 using default UDP/IPv4 port range: [1024, > > 65535] > > 04-Dec-2008 09:52:54.956 using default UDP/IPv6 port range: [1024, > > 65535] > > 04-Dec-2008 09:52:54.958 listening on IPv4 interface lo, 127.0.0.1#53 > > 04-Dec-2008 09:52:54.958 could not listen on UDP socket: address in > > use > > 04-Dec-2008 09:52:54.958 creating IPv4 interface lo failed; interface > > > ignored > > 04-Dec-2008 09:52:54.958 listening on IPv4 interface eth1, > > ###.###.#.### #53 > > 04-Dec-2008 09:52:54.958 could not listen on UDP socket: address in > > use > > 04-Dec-2008 09:52:54.958 creating IPv4 interface eth1 failed; > > interface ignored > > 04-Dec-2008 09:52:54.958 not listening on any interfaces > > 04-Dec-2008 09:52:54.959 /etc/bind/named.conf:80: couldn't add command > > channel 127.0.0.1#953: address in use > > 04-Dec-2008 09:52:54.959 ignoring config file logging statement due to > > -g option > > 04-Dec-2008 09:52:54.960 additionally listening on IPv4 interface lo, > > 127.0.0.1#53 > > 04-Dec-2008 09:52:54.960 could not listen on UDP socket: address in > > use > > 04-Dec-2008 09:52:54.960 creating IPv4 interface lo failed; interface > > ignored > > 04-Dec-2008 09:52:54.960 additionally listening on IPv4 interface > > eth1, ###.###.#.### #53 > > 04-Dec-2008 09:52:54.960 could not listen on UDP socket: address in > > use > > 04-Dec-2008 09:52:54.960 creating IPv4 interface eth1 failed; > > interface ignored > > 04-Dec-2008 09:52:54.961 zone 0.in-addr.arpa/IN: loaded serial 1 > > 04-Dec-2008 09:52:54.961 zone 127.in-addr.arpa/IN: loaded serial 1 > > 04-Dec-2008 09:52:54.962 zone 255.in-addr.arpa/IN: loaded serial 1 > > 04-Dec-2008 09:52:54.962 /etc/bind/db.bind:5: class 'CH' !=3D zone class > > 'IN' > > 04-Dec-2008 09:52:54.962 zone bind/IN: loading master file /etc/bind/ > > db.bind: bad class > > 04-Dec-2008 09:52:54.962 zone localhost/IN: loaded serial 1 > > 04-Dec-2008 09:52:54.962 running > > 04-Dec-2008 09:52:56.244 shutting down > > 04-Dec-2008 09:52:56.245 exiting > > > In the other version i had a line like this > > found X CPUs, using X worker threads > > > Thanks again > > ___ > > bind-users mailing list > > [EMAIL PROTECTED] > >https://lists.isc.org/mailman/listinfo/bind-users > > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] > ___ > bind-users mailing list > [EMAIL PROTECTED]://lists.isc.org/mailman/listinfo/bind-users Ok Mark, I can try that... But in the config.log I see the lines: checking whether to build with thread support... yes checking whether to build with threads... yes So I think putting only --enable-threads is the same. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: socket: too many open file descriptors
On 3 dic, 21:08, Mark Andrews <[EMAIL PROTECTED]> wrote: > In message <[EMAIL PROTECTED]>, > > pollex writes: > > Hi Jinmei I have followed your advice and I have installed and > > compiled the Bind 9.3.6 with the following command: > > STD_CDEFINES="-ISC_SOCKET_FDSETSIZE=4096" ./configure --prefix=/usr/ > > local/bind9.3.6 --enable-threads > > But now I have the following issue, I can't start bind with multi > > threading... > > I have in the init script the lines: > > OPTIONS="-u bind -n 8 -t /var/lib/named -c /etc/bind/named.conf" > > and in the start part: > > mount --bind /proc/ /var/lib/named/proc/ -o ro (This is needed because > > bin runs in jail) > > > Any idea? (With the previous version this works ok) > > Log messages would be useful. > > What does the following report? > "named -g -u bind -n 8 -t /var/lib/named -c /etc/bind/named.conf" > > > Thanks for all > > > ___ > > bind-users mailing list > > [EMAIL PROTECTED] > >https://lists.isc.org/mailman/listinfo/bind-users > > -- > Mark Andrews, ISC > 1 Seymour St., Dundas Valley, NSW 2117, Australia > PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] > ___ > bind-users mailing list > [EMAIL PROTECTED]://lists.isc.org/mailman/listinfo/bind-users Mark, thanks for the reply this is the report: 04-Dec-2008 09:52:54.950 starting BIND 9.3.6 -g -u bind -n 8 -t /var/ lib/named -c /etc/bind/named.conf 04-Dec-2008 09:52:54.950 using up to 4096 sockets 04-Dec-2008 09:52:54.954 loading configuration from '/etc/bind/ named.conf' 04-Dec-2008 09:52:54.956 using default UDP/IPv4 port range: [1024, 65535] 04-Dec-2008 09:52:54.956 using default UDP/IPv6 port range: [1024, 65535] 04-Dec-2008 09:52:54.958 listening on IPv4 interface lo, 127.0.0.1#53 04-Dec-2008 09:52:54.958 could not listen on UDP socket: address in use 04-Dec-2008 09:52:54.958 creating IPv4 interface lo failed; interface ignored 04-Dec-2008 09:52:54.958 listening on IPv4 interface eth1, ###.###.#.### #53 04-Dec-2008 09:52:54.958 could not listen on UDP socket: address in use 04-Dec-2008 09:52:54.958 creating IPv4 interface eth1 failed; interface ignored 04-Dec-2008 09:52:54.958 not listening on any interfaces 04-Dec-2008 09:52:54.959 /etc/bind/named.conf:80: couldn't add command channel 127.0.0.1#953: address in use 04-Dec-2008 09:52:54.959 ignoring config file logging statement due to -g option 04-Dec-2008 09:52:54.960 additionally listening on IPv4 interface lo, 127.0.0.1#53 04-Dec-2008 09:52:54.960 could not listen on UDP socket: address in use 04-Dec-2008 09:52:54.960 creating IPv4 interface lo failed; interface ignored 04-Dec-2008 09:52:54.960 additionally listening on IPv4 interface eth1, ###.###.#.### #53 04-Dec-2008 09:52:54.960 could not listen on UDP socket: address in use 04-Dec-2008 09:52:54.960 creating IPv4 interface eth1 failed; interface ignored 04-Dec-2008 09:52:54.961 zone 0.in-addr.arpa/IN: loaded serial 1 04-Dec-2008 09:52:54.961 zone 127.in-addr.arpa/IN: loaded serial 1 04-Dec-2008 09:52:54.962 zone 255.in-addr.arpa/IN: loaded serial 1 04-Dec-2008 09:52:54.962 /etc/bind/db.bind:5: class 'CH' != zone class 'IN' 04-Dec-2008 09:52:54.962 zone bind/IN: loading master file /etc/bind/ db.bind: bad class 04-Dec-2008 09:52:54.962 zone localhost/IN: loaded serial 1 04-Dec-2008 09:52:54.962 running 04-Dec-2008 09:52:56.244 shutting down 04-Dec-2008 09:52:56.245 exiting In the other version i had a line like this found X CPUs, using X worker threads Thanks again ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: socket: too many open file descriptors
On 20 nov, 17:09, JINMEI Tatuya / 神明達哉 <[EMAIL PROTECTED]> wrote: > At Thu, 20 Nov 2008 04:30:00 -0800 (PST), > > pollex <[EMAIL PROTECTED]> wrote: > > > "9.3.4-P1.1" still seems to be a Debian specific version, but if this > > > is featurewise equivalent to 9.3.5-P1, you should at least upgrade to > > > 9.3.5-P2 (and build it with a large value of ISC_SOCKET_MAXSOCKETS). > > > In fact, I'd rather more strongly recommend 9.3.6. > > First off, there was a typo in my previous response: > ISC_SOCKET_MAXSOCKETS should have been ISC_SOCKET_FDSETSIZE. > > > how is the exact command line to compile with 4096 FDs? > > ./configure --ISC_SOCKET_MAXSOCKETS='4096'? > > Replacing the macro name with the correct one, and assuming you're > using a bsh variant such as zsh and bash: > > % STD_CDEFINES='-DISC_SOCKET_FDSETSIZE=4096' ./configure > > But again, I'd rather strongly recommend 9.3.6. Then you won't have > to care about ISC_SOCKET_MAXSOCKETS or any other annoying details > about FD consumption in the first place. There should be no reason > for someone considering an upgrade to 9.3.5-P2 not to rather use > 9.3.6. > > --- > JINMEI, Tatuya > Internet Systems Consortium, Inc. > ___ > bind-users mailing list > [EMAIL PROTECTED]://lists.isc.org/mailman/listinfo/bind-users Hi Jinmei I have followed your advice and I have installed and compiled the Bind 9.3.6 with the following command: STD_CDEFINES="-ISC_SOCKET_FDSETSIZE=4096" ./configure --prefix=/usr/ local/bind9.3.6 --enable-threads But now I have the following issue, I can't start bind with multi threading... I have in the init script the lines: OPTIONS="-u bind -n 8 -t /var/lib/named -c /etc/bind/named.conf" and in the start part: mount --bind /proc/ /var/lib/named/proc/ -o ro (This is needed because bin runs in jail) Any idea? (With the previous version this works ok) Thanks for all ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Bind MultiCPU in Debian
Hi, we have installed BIND 9.3.6 and we can't start it with this feature... In the other version (bind 9.3.5) we had to add this lines: /etc/default/bind9 OPTIONS="-u bind -n 8 -t /var/lib/named -c /etc/bind/named.conf" /etc/init.d/bind9 mount --bind /proc/ /var/lib/named/proc/ -o ro But now since I compiled the binaries with the command: STD_CDEFINES="-ISC_SOCKET_FDSETSIZE=4096" ./configure --prefix=/usr/ local/bind9.3.6 --enable-threads When I start bind I don't even see the line with the processors found... starting BIND 9.3.6 -g 03-Dec-2008 10:10:12.716 using up to 4096 sockets 03-Dec-2008 10:10:12.720 loading configuration from '/usr/local/ bind9.3.6/etc/named.conf' In BIND 9.3.5 starting BIND 9.3.4-P1.1 -g 03-Dec-2008 10:11:10.243 found 2 CPUs, using 2 worker threads 03-Dec-2008 10:11:10.248 loading configuration from '/etc/bind/ named.conf' Any idea what I am missing here? Thanks ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: socket: too many open file descriptors
On 20 nov, 17:09, JINMEI Tatuya / 神明達哉 <[EMAIL PROTECTED]> wrote: > At Thu, 20 Nov 2008 04:30:00 -0800 (PST), > > pollex <[EMAIL PROTECTED]> wrote: > > > "9.3.4-P1.1" still seems to be a Debian specific version, but if this > > > is featurewise equivalent to 9.3.5-P1, you should at least upgrade to > > > 9.3.5-P2 (and build it with a large value of ISC_SOCKET_MAXSOCKETS). > > > In fact, I'd rather more strongly recommend 9.3.6. > > First off, there was a typo in my previous response: > ISC_SOCKET_MAXSOCKETS should have been ISC_SOCKET_FDSETSIZE. > > > how is the exact command line to compile with 4096 FDs? > > ./configure --ISC_SOCKET_MAXSOCKETS='4096'? > > Replacing the macro name with the correct one, and assuming you're > using a bsh variant such as zsh and bash: > > % STD_CDEFINES='-DISC_SOCKET_FDSETSIZE=4096' ./configure > > But again, I'd rather strongly recommend 9.3.6. Then you won't have > to care about ISC_SOCKET_MAXSOCKETS or any other annoying details > about FD consumption in the first place. There should be no reason > for someone considering an upgrade to 9.3.5-P2 not to rather use > 9.3.6. > > --- > JINMEI, Tatuya > Internet Systems Consortium, Inc. > ___ > bind-users mailing list > [EMAIL PROTECTED]://lists.isc.org/mailman/listinfo/bind-users Ok, thanks I will try that Compiling bind 9.3.6 with: STD_CDEFINES="-ISC_SOCKET_FDSETSIZE=4096" ./configure --prefix=/usr/ local/bind9.3.6 --enable-threads ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: socket: too many open file descriptors
On 19 nov, 13:32, JINMEI Tatuya / 神明達哉 <[EMAIL PROTECTED]> wrote: > At Wed, 19 Nov 2008 04:03:23 -0800 (PST), > > pollex <[EMAIL PROTECTED]> wrote: > > > Running bind9 9.3.4-2etch3 on Debian etch 4.0(last stable version with > > > apt-get install bind9) and I continue to get "socket: too many open > > > file descriptors" messages. > > The version of bind is "BIND 9.3.4-P1.1" > > And the error appears when named open around of 1000 sockets: > > lsof | grep named | wc -l > > 968 > > "9.3.4-P1.1" still seems to be a Debian specific version, but if this > is featurewise equivalent to 9.3.5-P1, you should at least upgrade to > 9.3.5-P2 (and build it with a large value of ISC_SOCKET_MAXSOCKETS). > In fact, I'd rather more strongly recommend 9.3.6. > > --- > JINMEI, Tatuya > Internet Systems Consortium, Inc. > ___ > bind-users mailing list > [EMAIL PROTECTED]://lists.isc.org/mailman/listinfo/bind-users Hi how is the exact command line to compile with 4096 FDs? ./configure --ISC_SOCKET_MAXSOCKETS='4096'? thanks again ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: socket: too many open file descriptors
On 18 nov, 18:50, Fr34k <[EMAIL PROTECTED]> wrote: > Hello, > > When we were using 9.5.0-P2, we had to compile with 4096 FDs; otherwise, we= > saw the same socket complaints. > > The default only has 1024. It would appear that your environment may requir= > e more FDs as ours did. > > HTH -- Chris > > =A0 > > - Original Message > From: pollex <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Sent: Tuesday, November 18, 2008 9:04:55 AM > Subject: socket: too many open file descriptors > > Hello, > Running bind9 9.3.4-2etch3 on Debian etch 4.0(last stable version with > apt-get install bind9) and I continue to get "socket: too many open > file descriptors" messages. > > my ulimit -a: > core file size=A0 =A0 =A0 =A0 =A0 (blocks, -c) 0 > data seg size=A0 =A0 =A0 =A0 (kbytes, -d) unlimited > max nice=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (-e) 0 > file size=A0 =A0 =A0 =A0 =A0 =A0 =A0 (blocks, -f) unlimited > pending signals=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (-i) unlimited > max locked memory=A0 =A0 =A0 (kbytes, -l) unlimited > max memory size=A0 =A0 =A0 =A0 (kbytes, -m) unlimited > open files=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (-n) 24576 > pipe size=A0 =A0 =A0 =A0 =A0 =A0 (512 bytes, -p) 8 > POSIX message queues=A0 =A0 (bytes, -q) unlimited > max rt priority=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (-r) 0 > stack size=A0 =A0 =A0 =A0 =A0 =A0 =A0 (kbytes, -s) 8192 > cpu time=A0 =A0 =A0 =A0 =A0 =A0 =A0 (seconds, -t) unlimited > max user processes=A0 =A0 =A0 =A0 =A0 =A0 =A0 (-u) unlimited > virtual memory=A0 =A0 =A0 =A0 =A0 (kbytes, -v) unlimited > file locks=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (-x) unlimited > > And we already tried the selectest tool: > ./selecttest > selecttest: nsocks =3D 4093, TEST_FDSETSIZE =3D -1, FD_SETSIZE =3D 1024, > sizeof fd_set =3D 128 > created 4093 sockets, maxfd =3D 4095 > FD_CLR test...OK > FD_SET test...OK > select test...OK > > Any ideas? > Thanks in advice > ___ > bind-users mailing list > [EMAIL PROTECTED]://lists.isc.org/mailman/listinfo/bind-users > > ___ > bind-users mailing list > [EMAIL PROTECTED]://lists.isc.org/mailman/listinfo/bind-users First of all thanks for the answerings. The version of bind is "BIND 9.3.4-P1.1" And the error appears when named open around of 1000 sockets: lsof | grep named | wc -l 968 If I have to reinstall bind, there are any way to do it via apt-get? Or the only way is compiling the binaries? Thanks again ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
socket: too many open file descriptors
Hello, Running bind9 9.3.4-2etch3 on Debian etch 4.0(last stable version with apt-get install bind9) and I continue to get "socket: too many open file descriptors" messages. my ulimit -a: core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited max nice(-e) 0 file size (blocks, -f) unlimited pending signals (-i) unlimited max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 24576 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) unlimited max rt priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) unlimited virtual memory (kbytes, -v) unlimited file locks (-x) unlimited And we already tried the selectest tool: ./selecttest selecttest: nsocks = 4093, TEST_FDSETSIZE = -1, FD_SETSIZE = 1024, sizeof fd_set = 128 created 4093 sockets, maxfd = 4095 FD_CLR test...OK FD_SET test...OK select test...OK Any ideas? Thanks in advice ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
