> On Dec 16, 2022, at 08:13, Petr Špaček via Unbound-users > <unbound-users@lists.nlnetlabs.nl> wrote: > > On 16. 12. 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? > > "Upgrade." > > Latest Unbound is 1.17.0 - that's far away from 1.13.1, with _lots_ of fixes > merged in meanwhile. > > Debugging old versions is waste of developer's time.
If this is an OS-supplied Unbound, then that debug is on the OS vendor. They may be able to help. -FG