the backends do not
> get
> >>> enough traffic to keep the mysql connection open. You will notice it
> by
> >>> abnormally high virtual memory usage after pdns has been running for a
> >>> time. Each backend that dies leaves 10MB of virtual memo
Ok,
So i guess we go "manual" or inhouse cleaning methods.
Thanks for the infos!
On Jan 29, 2008 5:34 PM, Augie Schwer <[EMAIL PROTECTED]> wrote:
> On Jan 26, 2008 8:22 AM, Catalin Constantin <[EMAIL PROTECTED]> wrote:
> > We could not find any way of H
a running mysql server ? Also check the database that
> you have specified in your pdns.conf matches your actual database
> information (db name, user/password etc).
>
> Regards,
> Nico
> WARP3.COM
>
> From: Catalin Constantin [mailto:[EMAIL
this error not to happen ?
Nice would be to have a real example.
Note:
- we use latest pdns package from Debian Etch (stable).
Thanks,
--
Catalin Constantin
Dazoot Software
http://www.dazoot.eu/
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
onf? Does it have anything to do with a front-end
> for PDNS. What do you use a front-end to it?
>
> Sincerely
> Eugene
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Catalin
> Constantin
> Sent: Saturday, January 26
delete the DOMAIN entry for "test.com" from the master.
How does the SLAVE gets notified about this ?
In the slave logs we have lines like:
Jan 26 17:37:14 k2 pdns[28941]: Error trying to retrieve/refresh
'test.com': Remote nameserver reported error: RCODE=2
Any hint would be apprec