Unbound 1.13.1 segfault

Petr Menšík pemensik at redhat.com
Fri Dec 16 14:10:15 UTC 2022

Hi Manish.

If you had included what kind of distribution or system do you use, we 
may offer some help. Unless your unbound version still receives some 
support, I would definitely recommend upgrading.

Analysing created core dump would help, but we have no idea what do you 
have available. I would try coredumpctl at least if you have recent 
enough system. Please try to report more details about your crash to 
whatever distribution you have obtained this version.

It might be necessary to make some changes to default configuration, 
otherwise coredump is not recorded. Read bug 
https://bugzilla.redhat.com/show_bug.cgi?id=1640285 for some hints, what 
might help.


On 12/16/22 14:02, Manish via Unbound-users wrote:
> Hi Everyone,
> All my unbound nodes are failing at the same time and showing the 
> segault error. I'm running the 1.13.1 version.
> kernel: unbound[2575264]: segfault at 108 ip 00000000004973c0 sp 
> 00007f5dddffad38 error 4 in unbound[400000+e8000]
> Any thoughts?
> Regards,

Petr Menšík
Software Engineer, RHEL
Red Hat, https://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB

More information about the Unbound-users mailing list