[Pdns-users] Issues with PowerDNS 2.9.21-svn.20060412.686

Sat May 20 14:36:09 UTC 2006

For some reason this never made it through, so here it is again:

_____________________________________________
From: David Levy 
Sent: Friday, May 12, 2006 12:10
To: 'pdns-users at mailman.powerdns.com'
Subject: Issues with PowerDNS 2.9.21-svn.20060412.686

Hi all,
	I am presently having a couple of (likely related) issues with
PowerDNS 2.9.21-svn.20060412.686.  The first few times we saw the issue,
it presented itself as PowerDNS barfing on AXFRs.  The TCP port would
remain open, but then the connection would drop on the server side and
the client would of course just hang until it timed out.  Messages such
as the following would show up in our logs each time this happened:

TCP nameserver had error, cycling backend:Trying to read data from
remote TCP client 64.62.228.79: Connection reset by peer

This wouldn't happen immediately; it seemed to be a function of time and
queries.  So we started a packet sniffer and restarted PowerDNS with the
hope that we would be able to send you a packet dump from the time our
server started until it started exhibiting this behavior, but something
else happened this time, instead of just AXFRs having problems, PowerDNS
completely crashed.

May 11 21:00:38 bdns01 pdns-bdns[12275]: AXFR of domain
'zzzzzzzzzzzzzzz.com' initiated by 10.30.120.35
May 11 21:00:38 bdns01 pdns-bdns[12275]: Got a signal 11, attempting to
print trace:
May 11 21:00:38 bdns01 pdns-bdns[12275]:
/usr/local/sbin/pdns_server-bdns-instance [0x80b84f8]
May 11 21:00:38 bdns01 pdns-bdns[12275]: /lib/tls/libc.so.6 [0x3daa48]
May 11 21:00:38 bdns01 pdns-bdns[12275]:
/usr/local/sbin/pdns_server-bdns-instance(_ZN13TCPNameserver6doAXFRERKSs
P9DNSPacketi+0x494) [0x8093da4]
May 11 21:00:38 bdns01 pdns-bdns[12275]:
/usr/local/sbin/pdns_server-bdns-instance(_ZN13TCPNameserver12doConnecti
onEPv+0x1203) [0x80962df]
May 11 21:00:38 bdns01 pdns-bdns[12275]: /lib/tls/libpthread.so.0
[0x5213ae]
May 11 21:00:38 bdns01 pdns-bdns[12275]:
/lib/tls/libc.so.6(__clone+0x5e) [0x479b6e]
May 11 21:00:39 bdns01 pdns-bdns[7881]: Our pdns instance (12275) exited
after signal 6
May 11 21:00:39 bdns01 pdns-bdns[7881]: Respawning
May 11 21:00:40 bdns01 pdns-bdns[25211]: Virtual configuration name:
bdns
May 11 21:00:40 bdns01 pdns-bdns[25211]: Guardian is launching an
instance
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
10.30.131.30:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.71:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.72:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.73:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.74:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.75:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.76:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.77:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.78:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.79:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.80:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.81:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.82:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.83:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.84:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.85:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.86:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.87:53
May 11 21:00:40 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.88:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.89:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.90:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: UDP server bound to
111.11.234.91:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
10.30.131.30:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.71:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.72:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.73:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.74:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.75:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.76:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.77:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.78:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.79:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.80:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.81:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.82:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.83:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.84:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.85:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.86:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.87:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.88:53
May 11 21:00:41 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.89:53
May 11 21:00:42 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.90:53
May 11 21:00:42 bdns01 pdns-bdns[25211]: TCP server bound to
111.11.234.91:53
May 11 21:00:42 bdns01 pdns-bdns[25211]: Set effective group id to 20920
May 11 21:00:42 bdns01 pdns-bdns[25211]: Set effective user id to 20920
May 11 21:00:42 bdns01 pdns-bdns[25211]: Creating backend connection for
TCP
May 11 21:00:44 bdns01 pdns-bdns[25211]: 5018 questions waiting for
database attention. Limit is 5000, respawning
May 11 21:00:44 bdns01 pdns-bdns[25211]: Got a signal 11, attempting to
print trace:
May 11 21:00:44 bdns01 last message repeated 3 times
May 11 21:00:44 bdns01 pdns-bdns[25211]:
/usr/local/sbin/pdns_server-bdns-instance [0x80b84f8]
May 11 21:00:44 bdns01 pdns-bdns[25211]: /lib/tls/libc.so.6 [0x3daa48]
May 11 21:00:44 bdns01 pdns-bdns[25211]:
/usr/lib/libstdc++.so.6(_ZNKSs7compareEPKc+0x16) [0x699ea8]
May 11 21:00:44 bdns01 pdns-bdns[25211]:
/usr/local/sbin/pdns_server-bdns-instance(_ZN5QType10chartocodeEPKc+0x26
) [0x807cab6]
May 11 21:00:44 bdns01 pdns-bdns[25211]:
/usr/local/sbin/pdns_server-bdns-instance(_ZN5QTypeaSERKSs+0x14)
[0x807cb80]
May 11 21:00:44 bdns01 pdns-bdns[25211]:
/usr/local/sbin/pdns_server-bdns-instance(_ZN11GSQLBackend3getER17DNSRes
ourceRecord+0x18e) [0x812557a]
May 11 21:00:44 bdns01 pdns-bdns[25211]:
/usr/local/sbin/pdns_server-bdns-instance(_ZN12UeberBackend6handle3getER
17DNSResourceRecord+0x20) [0x80c526c]
May 11 21:00:45 bdns01 pdns-bdns[7881]: Our pdns instance exited with
code 1
May 11 21:00:45 bdns01 pdns-bdns[7881]: Respawning

Pdns continued to repawn over and over again until we manually stopped
and started the service.  If anyone has any insight that would be great,
but I'm guessing that this is one for Bert.  I am having some issues
with the dnswasher, but I would be fine with sending the dumps directly
so the problem can be corrected, and I obfuscated our IP addresses
somewhat, thanks.

-David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20060520/0f14858c/attachment.html>