[Pdns-users] Pdns Remote backend crash

[Aleksey Chudov]

Hello,

I encountered the following problem. When executing Remote backend 
(tested with Remote + socket, pipe and http) and distributor-threads 
parameter greater than 1 pdns_server process crash while performance 
testing.

Pdns was built on Debian 6.0.7

aptitude install libboost-program-options-dev libboost-serialization-dev 
liblua5.1-dev libz-dev
wget http://downloads.powerdns.com/releases/pdns-3.2.tar.gz
tar -xzf pdns-3.2.tar.gz
cd pdns-3.2/
./configure --prefix=/usr --sysconfdir=/etc/powerdns 
--localstatedir=/var/run/pdns --libdir=/usr/lib/pdns --disable-shared 
--enable-static --enable-static-boost --enable-static-binaries 
--enable-pdns_server --disable-recursor --with-modules="pipe remote" 
--with-dynmodules=""
make
make install


There is no errors when pdns_server starts with distributor-threads=1. 
Performance is quite good – 7k qps according to dnsperf statistics (32 
instances of dnsperf simultaneously). But if I start pdns_server with 
distributor-threads greater than 1 and run more than one instance 
dnsperf simultaneously, the process crash.

log-level is set to 9 but only the following message is printed to log file

Feb 27 19:49:01 srv1 pdns[28609]: Got a signal 6, attempting to print 
trace:
Feb 27 19:49:01 srv1 pdns[28609]: [0x49a720]
Feb 27 19:49:01 srv1 pdns[28609]: [0x6598d0]
Feb 27 19:49:01 srv1 pdns[28609]: [0x762f75]
Feb 27 19:49:01 srv1 pdns[28609]: [0x6f5b90]
Feb 27 19:49:01 srv1 pdns[28609]: [0x6f0ac5]
Feb 27 19:49:01 srv1 pdns[28609]: [0x42b227]
Feb 27 19:49:01 srv1 pdns[28609]: [0x47f202]
Feb 27 19:49:01 srv1 pdns[28609]: [0x4a5e41]
Feb 27 19:49:01 srv1 pdns[28609]: [0x456399]
Feb 27 19:49:01 srv1 pdns[28609]: [0x45e9b7]
Feb 27 19:49:01 srv1 pdns[28609]: [0x460825]
Feb 27 19:49:01 srv1 pdns[28609]: [0x4e1244]
Feb 27 19:49:01 srv1 pdns[28609]: [0x65561a]
Feb 27 19:49:01 srv1 pdns[28609]: [0x741fa9]
Feb 27 19:49:01 srv1 pdns[28607]: Our pdns instance (28609) exited after 
signal 6
Feb 27 19:49:01 srv1 pdns[28607]: Respawning

I specifically checked that there is no such problem with Pipe backend 
only with Remote backend.

Any ideas?


Best regards,
Aleksey