Re: still have named memory leak
On Fri, Dec 12, 2014 at 8:12 AM, Mukund Sivaraman m...@isc.org wrote: Hi Len On Fri, Dec 12, 2014 at 09:52:23AM -0600, lcon...@go2france.com wrote: binary upgraded Freebsd 10 to Freebsd 10.1 named 9.10.1, compiled from source at named start, 305 MB memory after several hours of running named is approaching 800 MB. I'm sure after a couple of days, as before, it will head towards 2000 MB suggestions? this is a recursive only NS, about 20M q/day restricted by ACL to ournetworks This tells us that the named process size grows large, but more information is needed to discover why. Can you send us the following? 1. Your named configuration. 2. Regular dumps over time of the statistics that are available via HTTP, as the named process grows. See the statistics-channels documentation in the manual. You can use curl or wget to dump them to a file. The standard tool for this on FreeBSD is fetch(1). E.g. fetch -o FILE URL In a script I usually also use '-q' to eliminate noise, but YMMV. I suspect most systems have wget and/or curl installed, but fetch is always present on FreeBSD. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ 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: still have named memory leak
Here’s some suggestions from ISC on capturing information on this memory growth issue: https://kb.isc.org/article/AA-01208 Frank From: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Kevin Oberman Sent: Saturday, December 13, 2014 12:07 PM To: Mukund Sivaraman Cc: bind-users@lists.isc.org Subject: Re: still have named memory leak On Fri, Dec 12, 2014 at 8:12 AM, Mukund Sivaraman m...@isc.org mailto:m...@isc.org wrote: Hi Len On Fri, Dec 12, 2014 at 09:52:23AM -0600, lcon...@go2france.com mailto:lcon...@go2france.com wrote: binary upgraded Freebsd 10 to Freebsd 10.1 named 9.10.1, compiled from source at named start, 305 MB memory after several hours of running named is approaching 800 MB. I'm sure after a couple of days, as before, it will head towards 2000 MB suggestions? this is a recursive only NS, about 20M q/day restricted by ACL to ournetworks This tells us that the named process size grows large, but more information is needed to discover why. Can you send us the following? 1. Your named configuration. 2. Regular dumps over time of the statistics that are available via HTTP, as the named process grows. See the statistics-channels documentation in the manual. You can use curl or wget to dump them to a file. The standard tool for this on FreeBSD is fetch(1). E.g. fetch -o FILE URL In a script I usually also use '-q' to eliminate noise, but YMMV. I suspect most systems have wget and/or curl installed, but fetch is always present on FreeBSD. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com mailto:rkober...@gmail.com ___ 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: still have named memory leak
Hi Len On Fri, Dec 12, 2014 at 09:52:23AM -0600, lcon...@go2france.com wrote: binary upgraded Freebsd 10 to Freebsd 10.1 named 9.10.1, compiled from source at named start, 305 MB memory after several hours of running named is approaching 800 MB. I'm sure after a couple of days, as before, it will head towards 2000 MB suggestions? this is a recursive only NS, about 20M q/day restricted by ACL to ournetworks This tells us that the named process size grows large, but more information is needed to discover why. Can you send us the following? 1. Your named configuration. 2. Regular dumps over time of the statistics that are available via HTTP, as the named process grows. See the statistics-channels documentation in the manual. You can use curl or wget to dump them to a file. By looking at the statistics file (it's available as XML and JSON), we can see if any memory contexts grow large and that could point to where this large amount of memory is being used. Also, did you use a max-cache-size option when running the above named? Mukund pgp12oF0oUHF5.pgp Description: PGP signature ___ 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: still have named memory leak
On Friday 12/12/2014 at 10:12 am, Mukund Sivaraman wrote: Hi Len On Fri, Dec 12, 2014 at 09:52:23AM -0600, lcon...@go2france.com wrote: binary upgraded Freebsd 10 to Freebsd 10.1 named 9.10.1, compiled from source at named start, 305 MB memory after several hours of running named is approaching 800 MB. I'm sure after a couple of days, as before, it will head towards 2000 MB suggestions? this is a recursive only NS, about 20M q/day restricted by ACL to ournetworks This tells us that the named process size grows large, but more information is needed to discover why. Can you send us the following? 1. Your named configuration. 2. Regular dumps over time of the statistics that are available via HTTP, as the named process grows. See the statistics-channels documentation in the manual. You can use curl or wget to dump them to a file. By looking at the statistics file (it's available as XML and JSON), we can see if any memory contexts grow large and that could point to where this large amount of memory is being used. Also, did you use a max-cache-size option when running the above named? Mukund With earlier Freebsd 10 and bind 9.10, max-cache didn't limit the growth in named memory size. named.conf sent privately. I'll work on your other points. Len ___ 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
