Hi there, I'm impressed that you sent this, wow! I ended up finding the problem. There was a duplicate slave domain entry in named.conf, and I reported it to the pdns-users mailing list:
On Fri, Mar 03, 2006 at 11:49:12AM -0800, Ben Damm wrote: > A followup. I've finally narrowed this down to a crash due to a duplicate > slave domain entry in named.conf. > Mar 3 03:09:06 ns1 pdns[11585]: [0xffffe420] > Mar 3 03:09:06 ns1 pdns[11585]: /lib/tls/libc.so.6(gsignal+0x47) [0xb7cbc7c7] > Mar 3 03:09:06 ns1 pdns[11585]: /lib/tls/libc.so.6(abort+0xeb) [0xb7cbe06b] > Mar 3 03:09:06 ns1 pdns[11585]: /lib/tls/libc.so.6(__assert_fail+0x115) [0xb7cb5735] > Mar 3 03:09:06 ns1 pdns[11585]: /usr/sbin/pdns_server-instance(_ZN12Bind2Backend6insertEiRKSsS1_S1_ii+0x4f3) [0x80c3d13] Thanks for your work! I'm considering picking up some packaging work too but I'm not sure yet where to start. Cheers, -Ben On Tuesday 11 July 2006 15:27, Matthijs Mohlmann wrote: > Hi, > > I couldn't reproduce this problem, are you still experiencing the > problems described in this bug report ? > > See: http://bugs.debian.org/348041 for more information. > > Regards, > > Matthijs Mohlmann -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
