Unbound service routinely stopping/crashing following 20.7.7 update

[guest25283]

Here's the latest Unbound revision 1 from FreeBSD ports to try:

# pkg add -f https://pkg.opnsense.org/FreeBSD:12:amd64/20.7/misc/unbound-1.13.0_1.txz

Cheers,
Franco

Updated unbound on my system to the provided revision. Will report back with feedback.

Unbound has been running stable for 24 hours now on the new revision. Issue appears resolved on my end.

I can confirm the same! Any chance this could make it into a hotfix, or will this have to wait until 21.1?

[allebone]

Im also having the same issue and cannot easily apply the patch right now

What can I do? Is there an eta till the next update? Im having to start the service every few hours

[franco]

20.7.8 is needed to bundle the Unbound fix. I am afraid we have to give it more time for multiple reasons. The non-obvious reason is that there is still one bugfix missing and that may be one of the reasons netlabs hasn't released 1.13.1 yet.


Cheers,
Franco

PS: The patch apply is trivial and perfectly safe.

[allebone]

Thank you for your reply. I appreciate it. It is kind of you to reply directly to me.


I am not able to Reboot as I already had my reboot window this week which I used to upgrade the firewall. As the issue is not a security problem, but a problem that requires me to login and start the service it is seen as a problem that I have to live with until Saturday when I can reboot again.

Is there any way to apply this fix without rebooting?

Kind regards
Peter

[Gauss23]

I don’t think there is a reboot needed.

[allebone]

Ok thank you that is awesome. I will run the patch then

Im just going to turn on ssh and do this then:

opnsense-revert -r 20.7.6 unbound

[allebone]

Thank you all. You were correct. No reboot. Just typed that command and turned off ssh again. I did restart unbound just in case also after but whole process was only 1 minute long

[eculcea]

Same for me
opnsense-revert -r 20.7.6 unbound
fixed the issue

[talopensense]

Thank you all - I add the same issue. I applied 1.13.0_1 patch and I will see how it goes.

[mahescho]

Same here, just FTR. For me it crashes about every second day. I will apply the patch.

[Sabkor]

Here's the latest Unbound revision 1 from FreeBSD ports to try:

# pkg add -f https://pkg.opnsense.org/FreeBSD:12:amd64/20.7/misc/unbound-1.13.0_1.txz

I tried this and can confirm that I am still getting crashes. Here is the latest General log lines from the last crash, running the above patch.

Code: [Select]

2020-12-28T23:16:15 kernel -> pid: 15953 ppid: 1 p_pax: 0xa50<SEGVGUARD,ASLR,NOSHLIBRANDOM,NODISALLOWMAP32BIT>
2020-12-28T23:16:15 kernel [HBSD SEGVGUARD] [unbound (15953)] Suspension expired.
2020-12-28T23:16:15 kernel pid 15953 (unbound), jid 0, uid 59: exited on signal 11
For now, I *think* I've setup a monit test to restart unbound if it crashes. Never used monit before, so we'll see if I did it right...

[hive]

I'm seeing this too! 

[Steven]

Thanks for the advice everyone, the opnsense-revert command worked for me.  No reboot needed.

Code: [Select]

opnsense-revert -r 20.7.6 unbound
I was going crazying trying to trace why my network kept dying till I discovered the DNS service shutting down over and over again. I originally thought it was due to my provider since they had a recent bad outage.

[tschlappinger]

Here's the latest Unbound revision 1 from FreeBSD ports to try:

# pkg add -f https://pkg.opnsense.org/FreeBSD:12:amd64/20.7/misc/unbound-1.13.0_1.txz

I installed the patch yesterday morning and since then, no problems anymore. Unbound is working again!

Thanks,
Timo

[potes]

For now, I *think* I've setup a monit test to restart unbound if it crashes. Never used monit before, so we'll see if I did it right...

Hi,

I'm also newbie, and also having the same issue with the unbound service stopping. Where you able to create a monit service to restart unbound when stop? can you share the configuration?

Thank you very much