[Pdns-users] signal 6 - pdns 2.9.20 from RPM on RHEL ES v3

[Kirk Friggstad]

FYI - finally tracked down the problem (with guidance from Bert) - it turns
out I had duplicate entries for a few zones in my named.conf that the old
bindbackend (< 2.9.19) didn't complain about, but caused a signal 6 in the
new bindbackend (>= 2.9.19). Removing the duplicates fixed the problem -
running without issue now.

Thanks again to Bert for all the help in tracking this down.

Kirk

-----Original Message-----
From: pdns-users-bounces at mailman.powerdns.com
[mailto:pdns-users-bounces at mailman.powerdns.com] On Behalf Of Miroslaw
Majorek
Sent: Friday, March 24, 2006 10:54 AM
To: pdns-users at mailman.powerdns.com
Subject: Re: [Pdns-users] signal 6 - pdns 2.9.20 from RPM on RHEL ES v3

Kirk Friggstad wrote:

>I'll be sending a separate message with the config files for you. Thanks!
>  
>
Please be sure to share the solution with the list. I am currently 
having the same problem - also using BIND backend, but on CentOS 4.2. 
PowerDNS on that machine is configured to be a pure slave PowerDNS, so 
named.conf is modified ONLY by PowerDNS.