On Wed, 2007-10-10 at 09:40 -0600, Darren Gamble wrote:
> Hi Brad,
>
> > I am using this release: pdns-recursor-3.1.4-1.i386.rpm
> >
> > The memory usage on the pdns_recursor daemon seems to keep growing
> > steadily. I currently have it set to cap at 1 million cache entries.
> My
> > graphs show
Hi Brad,
> I am using this release: pdns-recursor-3.1.4-1.i386.rpm
>
> The memory usage on the pdns_recursor daemon seems to keep growing
> steadily. I currently have it set to cap at 1 million cache entries.
My
> graphs show me hitting upwards of 1.07 million entries. I am currently
> at 287MB f
I am using this release: pdns-recursor-3.1.4-1.i386.rpm
The memory usage on the pdns_recursor daemon seems to keep growing
steadily. I currently have it set to cap at 1 million cache entries. My
graphs show me hitting upwards of 1.07 million entries. I am currently
at 287MB from the initial 226MB
> "Brad" == Brad Dameron <[EMAIL PROTECTED]> writes:
Brad> pdns_recursor[4174]: Unable to parse packet from remote UDP client
Brad> XX.XX.XXX.XXX: Can't parse non-query packet with opcode=4
Brad> Oct 5 08:40:15 rs-2 pdns_recursor[4174]: Unable to parse packet from
Brad> remote UDP client XX.XX
I am running pdns-recursor-3.1.4-1.i386.rpm. I have my
max-cache-entries=200 which is using 620MB. I am not forking the process to
the hyperthreadding. I am running this on two load balanced single P4 3Ghz
servers with 1GB and a 80GB SATA on CentOS 4.4. Let me tell you this thing
screams.