Your message dated Wed, 12 Jul 2006 08:13:03 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Crash on startup
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: pdns-server
Severity: important
Hi,
Ben Damm wrote:
> Hi there,
>
> I've got a persistent problem with the debian-packaged version of
> PowerDNS. It used to be working fine, however after recent upgrades
> (solved by downgrading, but I can't do that for very long) it crashes on
> startup, producing the following in the system log.
>
>
> Jan 13 12:38:18 heap pdns[19718]: PowerDNS 2.9.19 (C) 2001-2005
> PowerDNS.COM BV (Jan 6 2006, 12:53:36, gcc 4.0.3 20051201 (prerelease)
> (Debian 4.0.2-5)) starting up
> Jan 13 12:38:18 heap pdns[19718]: 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.
> Jan 13 12:38:18 heap pdns[19718]: Creating backend connection for TCP
> Jan 13 12:38:18 heap pdns[19718]: [bindbackend] Parsing 30 domain(s),
> will report when done
> Jan 13 12:38:18 heap postfix/smtpd[18360]: lost connection after RCPT
> from nsg93-1-82-67-182-127.fbx.proxad.net[82.67.182.127]
> Jan 13 12:38:18 heap postfix/smtpd[18360]: disconnect from
> nsg93-1-82-67-182-127.fbx.proxad.net[82.67.182.127]
> Jan 13 12:38:18 heap pdns[19718]: Got a signal 6, attempting to print trace:
> Jan 13 12:38:18 heap pdns[19718]: /usr/sbin/pdns_server-instance [0x809d18b]
> Jan 13 12:38:18 heap pdns[19718]: [0xffffe420]
> Jan 13 12:38:18 heap pdns[19718]: [0xffffe410]
> Jan 13 12:38:18 heap pdns[19718]:
> /lib/tls/i686/cmov/libc.so.6(gsignal+0x51) [0xb7cae691]
> Jan 13 12:38:18 heap pdns[19718]:
> /lib/tls/i686/cmov/libc.so.6(abort+0xeb) [0xb7caff5b]
> Jan 13 12:38:18 heap pdns[19718]:
> /lib/tls/i686/cmov/libc.so.6(__assert_fail+0x115) [0xb7ca7695]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(_ZN12Bind2Backend6insertEiRKSsS1_S1_ii+0x4f3)
> [0x80c3d13]
> Jan 13 12:38:18 heap pdns[19718]: /usr/sbin/pdns_server-instance [0x80c3f19]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(_ZN10ZoneParser5parseERKSsS1_j+0x65d)
> [0x80d4ced]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(_ZN12Bind2Backend10loadConfigEPSs+0x87f)
> [0x80c62ff]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(_ZN12Bind2BackendC1ERKSs+0x119) [0x80c8719]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(_ZN12Bind2Factory4makeERKSs+0x1d) [0x80d04ad]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(_ZN17BackendMakerClass3allEv+0xa1)
> [0x8091391]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(_ZN12UeberBackendC1ERKSs+0x170) [0x80a3ae0]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(_ZN13PacketHandlerC1Ev+0x1d) [0x8077ccd]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(_ZN13TCPNameserver2goEv+0x98) [0x807db38]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(_Z10mainthreadv+0x3a4) [0x80bd534]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(main+0x17f5) [0x80a0745]
> Jan 13 12:38:18 heap pdns[19718]:
> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd0) [0xb7c99eb0]
> Jan 13 12:38:18 heap pdns[19718]:
> /usr/sbin/pdns_server-instance(__gxx_personality_v0+0x105) [0x80605e1]
>
> Any idea what this could be? This problem has persisted over two
> revisions of PowerDNS (2.9.19-2 and 2.9.19-3).
>
I have at this moment no idea what's going wrong, so 2.9.19-1 is working ?
We'll try to reproduce this bug and try to fix it. Can you give me some
more information about your zones and configuration ? And how you put it
in /etc/powerdns/pdns.conf (the launch and the bindbackend configuration
parameters)
> Thanks,
> -Ben
>
I put the bug in the BTS. (Please use next time reportbug or another
tool to report the bug)
Thanks for reporting :)
Regards,
Matthijs Mohlmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDyN8Y2n1ROIkXqbARAo+AAJ4iGISuSTcYSbkOURGhy3hpOsb5XwCeKjPl
r84Mk6lo3VhhtGgTbbP5PNI=
=SVaW
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Ben Damm wrote:
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
Thanks for the explanation. I hereby close the bug report.
Regards,
Matthijs Mohlmann
--- End Message ---
