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 <Client_IP> port <Client_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
<d...@debian.org<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 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.
