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

[Kirk Friggstad]

Hi all:

I'm trying to get pdns running on a RedHat Enterprise v3 box - downloaded
and installed the RPM from powerdns.com - but I keep getting a signal 6
whenever I start. /var/log/messages excerpt below:

Mar 23 14:49:13 newt pdns[2604]: Listening on controlsocket in
'/var/run/pdns.controlsocket'
Mar 23 14:49:13 newt pdns[2607]: Guardian is launching an instance
Mar 23 14:49:13 newt pdns[2607]: This is a guarded instance of pdns
Mar 23 14:49:13 newt pdns[2607]: UDP server bound to 127.0.0.1:53
Mar 23 14:49:13 newt pdns[2607]: UDP server bound to xx.xx.xx.94:53
Mar 23 14:49:13 newt pdns[2607]: TCP server bound to 127.0.0.1:53
Mar 23 14:49:13 newt pdns[2607]: TCP server bound to xx.xx.xx.94:53
Mar 23 14:49:13 newt pdns[2607]: PowerDNS 2.9.20 (C) 2001-2006 PowerDNS.COM
BV (Mar 15 2006, 19:32:45, gcc 4.0.2) starting up
Mar 23 14:49:13 newt pdns[2607]: PowerDNS comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it according to
the terms of the GPL version 2.
Mar 23 14:49:13 newt pdns[2607]: Set effective group id to 502
Mar 23 14:49:13 newt pdns[2607]: Set effective user id to 502
Mar 23 14:49:13 newt pdns[2607]: DNS Proxy launched, local port 32626,
remote 127.0.0.1:4754
Mar 23 14:49:13 newt pdns[2611]: Launched webserver on xx.xx.xx.94:8081
Mar 23 14:49:13 newt pdns[2607]: Creating backend connection for TCP
Mar 23 14:49:13 newt pdns[2607]: [bindbackend] Parsing 611 domain(s), will
report when done
Mar 23 14:49:13 newt pdns[2607]: Got a signal 6, attempting to print trace:
Mar 23 14:49:13 newt pdns[2607]: [0x80a4a4a]
Mar 23 14:49:13 newt pdns[2607]: [0x814e25b]
Mar 23 14:49:13 newt pdns[2607]: [0x81d65e8]
Mar 23 14:49:13 newt pdns[2607]: [0x814bc96]
Mar 23 14:49:13 newt pdns[2607]: [0x81d6a22]
Mar 23 14:49:13 newt pdns[2607]: [0x81d211d]
Mar 23 14:49:13 newt pdns[2607]: [0x80ce818]
Mar 23 14:49:13 newt pdns[2607]: [0x80ce9ed]
Mar 23 14:49:13 newt pdns[2607]: [0x80df9d8]
Mar 23 14:49:13 newt pdns[2607]: [0x80d0f2b]
Mar 23 14:49:13 newt pdns[2607]: [0x80d3339]
Mar 23 14:49:13 newt pdns[2607]: [0x80db1d9]
Mar 23 14:49:13 newt pdns[2607]: [0x8097f68]
Mar 23 14:49:13 newt pdns[2607]: [0x80abd30]
Mar 23 14:49:13 newt pdns[2607]: [0x807d45b]
Mar 23 14:49:13 newt pdns[2607]: [0x80838de]
Mar 23 14:49:13 newt pdns[2607]: [0x80c80e5]
Mar 23 14:49:13 newt pdns[2607]: [0x80a87f9]
Mar 23 14:49:13 newt pdns[2607]: [0x81cfe35]
Mar 23 14:49:13 newt pdns[2607]: [0x8048111]
Mar 23 14:49:14 newt pdns[2604]: Our pdns instance (2607) exited after
signal 6

The pdns.conf file is simply a modified copy (changed IP addresses) from an
existing and normally functioning pdns 2.9.17 installation, and the bind
zone files are an unmodified copy of what's running on the 2.9.17
installation. According to the release notes, it looks like bindbackend has
been replaced with bind2backend - could there be something subtle in my zone
files that's causing the new bindbackend to fail? zone2sql seems to process
it without error. 

I'd rather not post my bind named.conf file publicly - if you need a copy, I
can send it via private mail.

Thanks in advance

Kirk