Re: BIND - out of memory

2009-04-23 Thread Jan Arild Lindstrøm
Hi, would be great if someone could explain why this happens and how we can correct it. Regards Jan Arild Lindstrøm At 09:13 26/03/2009, Jan Arild Lindstrøm wrote: >Hi, > >I allready tried 9.4.3, and it happened there. > >Trying 9.6.0-P1 gives the same result: > >

Re: BIND - out of memory

2009-03-26 Thread Jan Arild Lindstrøm
to not flush the whole cache or restart BIND. I have asked before about that problem, but no solution have been found. But perhaps now, the 1000/default "limit" and out-of-memory might be the/one of the reasons for this. Regards Jan Arild Lindstrom At 22:41 25/03/2009, Doug

Re: BIND - out of memory

2009-03-24 Thread Jan Arild Lindstrøm
s another number for it? Or? Regards Jan Arild Lindstrom At 11:44 24/03/2009, Jan Arild Lindstrøm wrote: >Hi, > >I am running ResPerf from Nominum against BIND 9.6.1b1, and I get a lot of: > >--cut-- >24-Mar-2009 08:51:30.495 database: adb: fetch of 'ns2.state.oh.us' A f

BIND - out of memory

2009-03-24 Thread Jan Arild Lindstrøm
Hi, I am running ResPerf from Nominum against BIND 9.6.1b1, and I get a lot of: --cut-- 24-Mar-2009 08:51:30.495 database: adb: fetch of 'ns2.state.oh.us' A failed: out of memory 24-Mar-2009 08:51:30.630 database: adb: fetch of 'gz-dns.cncnet.net' A failed: out of memory 24-Mar-2009 08:51:30.65

EDNS - edns-udp-size and max-udp-size

2009-02-24 Thread Jan Arild Lindstrøm
cing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:21.905 edns-disabled: success resolving '125.91.110.212.in-addr.arpa/PTR' (in '212.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:22.488 edns-disabled: success resolving 'ns7.virtua.com.br/A' (in 'virtua.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets 24-Feb-2009 08:56:22.490 edns-disabled: success resolving 'ns8.virtua.com.br/A' (in 'virtua.com.br'?) after reducing the advertised EDNS UDP packet size to 512 octets --cut-- How can it reduce it from 512 that is in the config, down to 512? I was expecting to see only "after disabling EDNS" messages after setting the size(s) to 512. It seems to me that max-udp-size and/or edns-udp-size does not do what I want, wich is to use 512 bytes packets. OS: Solaris 10 (SunOS 5.10 13-01) BIND: 9.6.0-P1, threaded. Regards Jan Arild Lindstrøm ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users

Re: BIND 9.4.x vs 9.6.x - pid-file check and creation

2009-01-29 Thread Jan Arild Lindstrøm
At 16:06 28/01/2009, Thomas Schulz wrote: >In article , >Jan Arild =?iso-8859-1?Q?Lindstr=F8m?= wrote: >> >>Hi, >> >>ah, of course. I did not think about it as a Solaris bug. >> >>I patched BIND 9.6.0-P1 os.c code so it first checks for the diretory >>before it tries the fast approach of just run

Re: BIND 9.4.x vs 9.6.x - pid-file check and creation

2009-01-28 Thread Jan Arild Lindstrøm
instead run with pid-file "/var/run/named/named/named.pid" and be happy with that. Thanks Jan Arild Lindstrøm At 15:35 27/01/2009, Mark Andrews wrote: >Looking at the publically available parts of SunSolve there are at least >bug reports about it. > >Requires Supp

Re: BIND 9.4.x vs 9.6.x - pid-file check and creation

2009-01-26 Thread Jan Arild Lindstrøm
> 25403] >> >> 25404/65: fstat(10, 0x79D0E9D0) =3D3D 0 >> >> 25404/65: fstat(10, 0x79D0E8A0) =3D3D 0 >> >> 25404/65: ioctl(10, TCGETA, 0x79D0E90C) Err#25= >> ENOT=3D &g

Re: BIND 9.4.x vs 9.6.x - pid-file check and creation

2009-01-26 Thread Jan Arild Lindstrøm
=3D 0 >> >25730/10: open("/var/log/confignew.log", O_WRONLY|O_APPEND|O_CREAT, = >> 0666) =3D 10 >> >25730/10: lseek(10, 0, SEEK_END) =3D 0 >> >25730/10: close(10) =3D 0 >> >25730/10: stat("/var/run/named/namednew.pid", 0x7D90F660) Er= >> r#2 ENOENT >> >25730/10: unlink("/var/run/named/namednew.pid") Err#2 ENOE= >> NT >> >25730/10: open("/var/run/named/namednew.pid", O_WRONLY|O_CREAT|O_EXC= >> L, 0644) =3D 10 >> >25730/10: fcntl(10, F_GETFD, 0x01A4) =3D 0 >> >25730/10: getpid()=3D 25730 = >> [25729] >> >25730/10: fstat(10, 0x7D90E6B0) =3D 0 >> >25730/10: fstat(10, 0x7D90E580) =3D 0 >> >25730/10: ioctl(10, TCGETA, 0x7D90E5EC) Err#25 ENO= >> TTY >> >25730/10: write(10, " 2 5 7 3 0\n", 6)=3D 6 >> >--CUT-- >> > >> > >> >It seems that someone has "shorted" the code to create and/or check the pi= >> d-file. >> > >> >Maybe that "shortcut" will work on Linux, but it for sure does not work on= >> Solaris 10. >> > >> >Having to use .../named/named/... in the pid-file option is of course poss= >> ible, but I = >> >> >guess that it is not the way it is supposed to be...(?)... >> > >> >Help? Ideas? >> > >> >Regards >> >Jan Arild Lindstr=F8m >> > >> >___ >> >bind-users mailing list >> >bind-users@lists.isc.org >> >https://lists.isc.org/mailman/listinfo/bind-users >> >> ___ >> bind-users mailing list >> bind-users@lists.isc.org >> 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: mark_andr...@isc.org Regards Jan Arild Lindstrøm ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users

Re: BIND 9.4.x vs 9.6.x - pid-file check and creation

2009-01-26 Thread Jan Arild Lindstrøm
=3D 0 >> 25730/10: stat("/var/run/named/namednew.pid", 0x7D90F660) Err= >> #2 ENOENT >> 25730/10: unlink("/var/run/named/namednew.pid") Err#2 ENOENT >> 25730/10: open("/var/run/named/namednew.pid", O_WRONLY|

Re: BIND 9.4.x vs 9.6.x - pid-file check and creation

2009-01-26 Thread Jan Arild Lindstrøm
;File exists". I'd say Solaris 10 first checks if the user have permissions to create the directory before it checks if it exists. So I would say the code for creating the pid-file has been changed between 9.4.3 and 9.6.0-P1, and that a bug has been introduced on Solaris. ? Regards Ja

BIND 9.4.x vs 9.6.x - pid-file check and creation

2009-01-25 Thread Jan Arild Lindstrøm
FFF7D90E6B0) = 0 25730/10: fstat(10, 0x7D90E580) = 0 25730/10: ioctl(10, TCGETA, 0x7D90E5EC) Err#25 ENOTTY 25730/10: write(10, " 2 5 7 3 0\n", 6)= 6 --CUT-- It seems tha