Unbound crashing

Started by seed, August 22, 2023, 08:18:48 AM

Previous topic - Next topic
Quote from: jefeman on January 23, 2024, 09:12:08 AM
snip

Thanks for the thorough guide for installing the patches.
I had left it for a few days after migrating the hardware to see what would happen.
I had 1 definite show stopper style unbound crash as normal however it would appear that the service didn't restart on that one... looking at the logs I have had a couple others but its possible the monit workaround has helped in getting it to restart as it didn't appear to stop resolving on those times.

I jumped in on applying all 3 patches. Will clear the logs and see what pops up over the next few days

It only took 18 days or so, and now I have 100% CPU on Unbound on one core. So the changes I have done has made it more stable kind-of, but still does NOT solve the issue.

Can also confirm that after a while I got the root.stubs issue again and unbound stopped resolving.
It seemed to have reduced the frequency of the issue, but not completely.

I installed Unbound from FreeBSD ports with debug symbols. But unfortunately (for me) Unbound hasn't crashed since January 27.

The only change I made (on January 28) is installing from source. So assuming I compiled the same way OPNsense does, eventually I'll get a crash and a core dump.

I think I saw upthread someone asking for the debug symbols that go with the OPNsense Unbound binaries. Does anyone more familiar with FreeBSD know if they are available for download somewhere?

So as i was still seeing this happen on 23.7 after applying the patches (it was better just not as bad) I decided to give 24.1 a run and see if anything else had changed. I have been running it for the last few days.

I can't even get through a single day without multiple reboots due to instances of this.

So i am on 24.1 and have just re-run the patches and see how it goes from there.

So since re-doing the patches (and a minor update)
I have seen 2 x entries in the log of errors, however I have not actually seen any issues from a usability standpoint.

I have seen none for coming up to almost 20hours.