Project

General

Profile

Actions

Regression #11316

closed

Unbound crashes with signal 11 when reloading

Added by Martin Müller about 3 years ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Category:
DNS Resolver
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.01
Release Notes:
Default
Affected Version:
2.5.x
Affected Architecture:

Description

Seems to be the same as here...
https://forum.opnsense.org/index.php?topic=20516.0

My workaround: I have moved to DNS forwarder.

  • Why has the command opnsense-revert not been adopted for pfSense?

Files

resolver.log.0.7z (1.06 MB) resolver.log.0.7z Christian Borchert, 03/09/2021 08:55 PM
resolver.log.0.7z (750 KB) resolver.log.0.7z Christian Borchert, 03/10/2021 05:08 AM
Screenshot from 2021-06-05 14-37-06.png (42.8 KB) Screenshot from 2021-06-05 14-37-06.png Kris Phillips, 06/05/2021 03:41 PM
Screenshot from 2021-06-05 14-37-24.png (41 KB) Screenshot from 2021-06-05 14-37-24.png Kris Phillips, 06/05/2021 03:41 PM
unbound-crash-2021-08-11.log (3.33 KB) unbound-crash-2021-08-11.log Akom Benevolent, 08/11/2021 02:12 PM
unbound-crash-2021-08-11-corrected.log (7.36 KB) unbound-crash-2021-08-11-corrected.log Akom Benevolent, 08/11/2021 03:19 PM

Related issues

Related to Bug #5413: Incorrect Handling of Unbound Resolver [service restarts, cache loss, DNS service interruption]ConfirmedChristian McDonald11/10/2015

Actions
Related to Todo #11915: Temporarily move back to Unbound 1.12.x due to instability on Unbound 1.13.xResolvedRenato Botelho05/12/2021

Actions
Related to Bug #10624: Memory leak in Unbound with Python module and DHCP lease registration activeResolvedChristian McDonald

Actions
Actions

Also available in: Atom PDF