Your message dated Sat, 10 Nov 2018 16:22:56 +0100 with message-id <[email protected]> and subject line Re: pdns-server: Using an RFC7505 null MX entry crashes pdns-server threads has caused the Debian Bug report #829647, regarding pdns-server: Using an RFC7505 null MX entry crashes pdns-server threads 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 829647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829647 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: pdns-server Version: 3.4.1-4+deb8u5 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I was adding null MX entrys as defined in RFC7505 to the pdns-server running with the bind backend * What exactly did you do (or not do) that was effective (or ineffective)? Added "@ IN MX 0 ." for a Host wich does not run a MTA. * What was the outcome of this action? The pdns-Server threads crashes, the dns changes and any further changes are not published. Logentries: Jul 05 00:00:17 dns pdns_server[8928]: Jul 05 00:00:17 Signing thread died because of std::exception: All data was not consumed Jul 05 00:00:17 dns pdns[8930]: Signing thread died because of std::exception: All data was not consumed Jul 05 00:00:17 dns pdns[8930]: Signing thread died because of std::exception: All data was not consumed Jul 05 00:00:17 dns pdns_server[8928]: Jul 05 00:00:17 Signing thread died because of std::exception: All data was not consumed Jul 05 00:00:17 dns pdns[8930]: Signing thread died because of std::exception: failed in writen2: Broken pipe Jul 05 00:00:17 dns pdns[8930]: TCP Connection Thread died because of STL error: Reading from socket in Signing Pipe loop: Connection reset by peer Jul 05 00:00:17 dns pdns_server[8928]: Jul 05 00:00:17 Signing thread died because of std::exception: failed in writen2: Broken pipe Jul 05 00:00:17 dns pdns_server[8928]: Jul 05 00:00:17 TCP Connection Thread died because of STL error: Reading from socket in Signing Pipe loop: Connection reset by peer * What outcome did you expect instead? The change were published to dns See Upstream Bug https://github.com/PowerDNS/pdns/issues/2836 and Upstream Commit https://github.com/PowerDNS/pdns/commit/e94c2c40ac6e0ecf8a5fdf7c415da5c59a8330d6 *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pdns-server depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii init-system-helpers 1.22 ii libboost-program-options1.55.0 1.55.0+dfsg-3 ii libboost-serialization1.55.0 1.55.0+dfsg-3 ii libbotan-1.10-0 1.10.8-2+deb8u1 ii libc6 2.19-18+deb8u4 ii libcrypto++9 5.6.1-6+deb8u2 ii libgcc1 1:4.9.2-10 ii libgmp10 2:6.0.0+dfsg-6 ii liblua5.1-0 5.1.5-7.1 ii libpolarssl7 1.3.9-2.1+deb8u1 ii libsqlite3-0 3.8.7.1-1+deb8u1 ii libstdc++6 4.9.2-10 ii lsb-base 4.1+Debian13+nmu1 ii ucf 3.0030 pdns-server recommends no packages. Versions of packages pdns-server suggests: ii pdns-backend-geo [pdns-backend] 3.4.1-4+deb8u5 ii pdns-recursor 3.6.2-2+deb8u2 -- debconf information: * pdns-server/localaddress: 217.70.197.53 * pdns-server/allowrecursion: 127.0.0.1
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Closing this as only oldstable or older versions are affected by this.
--- End Message ---
