Bug#962459: unbound: constantly crashing after about 3 minutes since start
Applied '0001-Apply-a-series-of-fixes-for-Unbound-1.9.0-suggested-.patch' Result: Oct 28 20:24:28 debian systemd[1]: Starting Unbound DNS server... Oct 28 20:24:28 debian package-helper[464]: /var/lib/unbound/root.key has content Oct 28 20:24:28 debian package-helper[464]: fail: the anchor is NOT ok and could not be fixed Oct 28 20:24:28 debian unbound[468]: [468:0] notice: init module 0: subnet Oct 28 20:24:28 debian unbound[468]: [468:0] notice: init module 1: validator Oct 28 20:24:28 debian unbound[468]: [468:0] notice: init module 2: iterator Oct 28 20:24:28 debian systemd[1]: Started Unbound DNS server. Oct 28 20:24:28 debian unbound[468]: [468:0] info: start of service (unbound 1.9.0). ... Oct 28 20:31:31 debian kernel: unbound[470]: segfault at 1b0 ip 7fdb28876e48 sp 7fdb26fd6cf0 error 4 in libevent-2.1.so.6.0.2[7fdb28857000+54000] Oct 28 20:31:31 debian kernel: Code: 00 00 41 55 41 54 41 89 d5 55 53 41 89 f4 48 89 fb 48 83 ec 08 48 8b 05 76 51 23 00 8b 10 85 d2 0f 85 8c 00 00 00 48 8b 6b 40 <48> 8b bd b0 01 00 00 48 85 ff 74 11 48 8b 05 2d 51 23 00 8b 00 85 Oct 28 20:31:31 debian systemd[1]: unbound.service: Main process exited, code=killed, status=11/SEGV Oct 28 20:31:31 debian systemd[1]: unbound.service: Failed with result 'signal'. Oct 28 20:31:31 debian systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart. Oct 28 20:31:31 debian systemd[1]: unbound.service: Scheduled restart job, restart counter is at 1. Oct 28 20:31:31 debian systemd[1]: Stopped Unbound DNS server. Oct 28 20:31:31 debian systemd[1]: Starting Unbound DNS server... Oct 28 20:31:31 debian package-helper[1994]: /var/lib/unbound/root.key has content Oct 28 20:31:31 debian package-helper[1994]: success: the anchor is ok Oct 28 20:31:31 debian unbound[1998]: [1998:0] notice: init module 0: subnet Oct 28 20:31:31 debian unbound[1998]: [1998:0] notice: init module 1: validator Oct 28 20:31:31 debian unbound[1998]: [1998:0] notice: init module 2: iterator Oct 28 20:31:31 debian systemd[1]: Started Unbound DNS server. Oct 28 20:31:31 debian unbound[1998]: [1998:0] info: start of service (unbound 1.9.0). ... Oct 28 20:32:41 debian kernel: unbound[2001]: segfault at 7fbb0009 ip 560e7af6bfb0 sp 7fbb29274480 error 4 in unbound[560e7af52000+c6000] Oct 28 20:32:41 debian kernel: Code: 24 20 0f b7 80 86 00 00 00 66 89 02 41 0f b6 76 20 49 8b 1e 83 e6 02 49 8b 47 28 48 8d 53 02 48 8d 0c ed 00 00 00 00 49 89 16 <48> 8b 04 e8 48 3b 44 24 08 0f 8d 21 05 00 00 40 84 f6 0f 85 48 04 Oct 28 20:32:41 debian systemd[1]: unbound.service: Main process exited, code=killed, status=11/SEGV Oct 28 20:32:41 debian systemd[1]: unbound.service: Failed with result 'signal'. Oct 28 20:32:41 debian systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart. Oct 28 20:32:41 debian systemd[1]: unbound.service: Scheduled restart job, restart counter is at 2. Oct 28 20:32:41 debian systemd[1]: Stopped Unbound DNS server. Oct 28 20:32:41 debian systemd[1]: Starting Unbound DNS server... Oct 28 20:32:41 debian package-helper[2199]: /var/lib/unbound/root.key has content Oct 28 20:32:41 debian package-helper[2199]: success: the anchor is ok Oct 28 20:32:41 debian unbound[2203]: [2203:0] notice: init module 0: subnet Oct 28 20:32:41 debian unbound[2203]: [2203:0] notice: init module 1: validator Oct 28 20:32:41 debian unbound[2203]: [2203:0] notice: init module 2: iterator Oct 28 20:32:41 debian systemd[1]: Started Unbound DNS server. Oct 28 20:32:41 debian unbound[2203]: [2203:0] info: start of service (unbound 1.9.0). S pozdravem Martin Kebert Informace obsa?en? v t?to e-mailov? zpr?v? a v?ech p?ilo?en?ch souborech jsou d?v?rn? a jsou ur?eny pouze pro pot?ebu adres?ta. Pros?me, abyste v p??pad?, ?e tento e-mail obdr??te omylem, neprodlen? upozornili odes?latele a tento e-mail odstranili z Va?eho syst?mu. Pokud nejste zam??len?m p??jemcem, berte pros?m na v?dom?, ?e zve?ejn?n?, kop?rov?n?, ???en? ?i p?ijet? jak?hokoliv opat?en? v souvislosti s obsahem t?to zpr?vy je zak?z?no a m??e b?t protipr?vn?. _ The information contained in this e-mail message and all attached files is confidential and is intended solely for the use of the individual or entity to whom they are addressed. Please notify the sender immediately if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is prohibited and may be unlawful.
Bug#962459: unbound: constantly crashing after about 3 minutes since start
Hi, I tried the patch "p1_and_2.diff" from #973052. I'm not saying it was extensive test, but 7 minutes after start I got first crash: Oct 28 17:35:26 debian systemd[1]: Started Unbound DNS server. Oct 28 17:35:26 debian unbound[450]: [450:0] info: start of service (unbound 1.9.0). ... Oct 28 17:42:26 debian systemd[1]: unbound.service: Main process exited, code=killed, status=11/SEGV Oct 28 17:42:26 debian systemd[1]: unbound.service: Failed with result 'signal'. Oct 28 17:42:26 debian systemd[1]: unbound.service: Service RestartSec=100ms expired, scheduling restart. Oct 28 17:42:26 debian systemd[1]: unbound.service: Scheduled restart job, restart counter is at 1. ... and 10 minutes later flood (about 30/sec) of these messages: ... Oct 28 17:52:49 debian unbound[1885]: [warn] Epoll ADD(1) on fd 52 failed. Old events were 0; read change was 1 (add); w rite change was 0 (none); close change was 0 (none): Bad file descriptor Oct 28 17:52:49 debian unbound[1885]: [1885:3] error: read (in tcp s): Bad file descriptor for port ... and "unbound" stopped responding to "unbound-control" (even simple "unbound-control status" hangs). I can't decide whether it was caused by this patch or whether it is someting different. Anyway I installed version 1.10 back which works. BTW. In meantime second server had installed original "debian stable" version of unbound-1.9.0 (to compare with patched version) with: ... Oct 28 17:48:45 debian2 unbound[519]: [err] evmap.c:381: Assertion nread >= 0 failed in evmap_io_del_ Oct 28 17:48:45 debian2 systemd[1]: unbound.service: Main process exited, code=killed, status=6/ABRT ... Oct 28 17:55:13 debian2 unbound[2811]: [err] evmap.c:381: Assertion nread >= 0 failed in evmap_io_del_ Oct 28 17:55:13 debian2 systemd[1]: unbound.service: Main process exited, code=killed, status=6/ABRT ... Oct 28 18:01:42 debian2 unbound[3951]: [err] evmap.c:381: Assertion nread >= 0 failed in evmap_io_del_ Oct 28 18:01:42 debian2 systemd[1]: unbound.service: Main process exited, code=killed, status=6/ABRT ... Oct 28 18:07:22 debian2 unbound[5187]: [err] evmap.c:381: Assertion nread >= 0 failed in evmap_io_del_ Oct 28 18:07:22 debian2 systemd[1]: unbound.service: Main process exited, code=killed, status=6/ABRT ... Oct 28 18:18:03 debian2 unbound[6196]: [err] evmap.c:381: Assertion nread >= 0 failed in evmap_io_del_ Oct 28 18:18:03 debian2 systemd[1]: unbound.service: Main process exited, code=killed, status=6/ABRT ... Oct 28 18:22:36 debian2 unbound[8178]: [err] evmap.c:381: Assertion nread >= 0 failed in evmap_io_del_ Oct 28 18:22:36 debian2 systemd[1]: unbound.service: Main process exited, code=killed, status=6/ABRT ... I'd say it is quite consistent (although frequency might depends on amount of traffic). S pozdravem Martin Kebert 28. 10. 2020 v 2:04, Daniel Kahn Gillmor mailto:d...@debian.org>>: Control: forcemerge 973052 962459 Hi Kebert-- On Mon 2020-06-08 12:28:46 +0200, Kebert Martin wrote: unbound constantly crashing with: [err] evmap.c:381: Assertion nread >= 0 failed in evmap_io_del_ The issue is fixed in unbound 1.9.2 but this version is not available in debian packages. As a workaround I had unbound from testing but it is not possible now, because currect testing version 1.10.1-1 relies on libpython3.8 which relies on libc6 >= 2.29 whereas stable libc6 is 2.28-10. Thanks for this note! sorry i missed it when reporting 973052, but it looks like it's the same issue. Would you be up for trying a version of unbound that includes the patch from 973052 and letting me know whether the crash is still happening? I haven't seen "consistent" failures with the workload where i encountered the bug, so it'd be great to hear whether the patch solves the problem for you if you've got a repeatable workload. If you don't know how to rebuild the package with the extra patch, please respond here and maybe one of the debian packagers who is used to working with unbound can offer a proposed update. Regards, --dkg Informace obsa?en? v t?to e-mailov? zpr?v? a v?ech p?ilo?en?ch souborech jsou d?v?rn? a jsou ur?eny pouze pro pot?ebu adres?ta. Pros?me, abyste v p??pad?, ?e tento e-mail obdr??te omylem, neprodlen? upozornili odes?latele a tento e-mail odstranili z Va?eho syst?mu. Pokud nejste zam??len?m p??jemcem, berte pros?m na v?dom?, ?e zve?ejn?n?, kop?rov?n?, ???en? ?i p?ijet? jak?hokoliv opat?en? v souvislosti s obsahem t?to zpr?vy je zak?z?no a m??e b?t protipr?vn?. _ The information contained in this e-mail message and all attached files is confidential and is intended solely for the use of the individual or entity to whom they are addressed. Please notify the sender immediately if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intend
Bug#962459: unbound: constantly crashing after about 3 minutes since start
Package: unbound Version: 1.9.0-2+deb10u2 Severity: important Dear Maintainer, unbound constantly crashing with: [err] evmap.c:381: Assertion nread >= 0 failed in evmap_io_del_ The issue is fixed in unbound 1.9.2 but this version is not available in debian packages. As a workaround I had unbound from testing but it is not possible now, because currect testing version 1.10.1-1 relies on libpython3.8 which relies on libc6 >= 2.29 whereas stable libc6 is 2.28-10. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (100, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages unbound depends on: ii adduser 3.118 ii dns-root-data 2019031302 ii libc6 2.28-10 ii libevent-2.1-6 2.1.8-stable-4 ii libfstrm0 0.4.0-1 ii libprotobuf-c1 1.3.1-1+b1 ii libpython3.73.7.3-2+deb10u1 ii libssl1.1 1.1.1d-0+deb10u3 ii libsystemd0 241-7~deb10u4 ii lsb-base10.2019051400 ii openssl 1.1.1d-0+deb10u3 ii unbound-anchor 1.9.0-2+deb10u2 unbound recommends no packages. Versions of packages unbound suggests: pn apparmor -- no debconf information
