Unbound service routinely stopping/crashing following 20.7.7 update

[potes]

Hi toxic, thanks for sharing the set-up, but for what I know (really little as I'm learning), I think is missing the test to see if the unbound service is working. How the machine know that unbound has stop? Thats not done by the test?

Regards

Same issue here, unbound keeps crashing. I tyed the opnsense-revert thing, we'll see if it holds

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...

Meanwhile I tried monit for the first time as well.
I *think* also I got it, but it took me a lot of tries, so for those who might be even more lost than I am, here is what I did in the monit>settings>service settings : add a new service as you can see in the attached picture.

Attached as well, in the monit>status you'll see it has found the proper process id.

I even stopped unbound and it got restarted within the 120 seconds of polling interval.

If you want to make it check faster, it happens on the first settings page, I think that is what would be the polling interval.

Couldn't find a way to get an email notification when the service gets restarted though... At least it restarts

[NKnusperer]

Same issue here with 20.7.7_1

Looks like this does not exist anymore:

Code: [Select]

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

[chemlud]

I have Unbound stable (in forwarding mode with DNS-over-TLS), not seeing and problems with latest version. Maybe this is worth a try before downgrading...

[Fright]

Looks like this does not exist anymore

looks like 21.1 on the way

[franco]

Looks like this does not exist anymore:

Code: [Select]

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

Because it's part of the official 20.7.7 now.

[jean.paradis]

The problem is the same for me. it stops at all times.
I assign the interface manually and the problem is still there.

Versions   OPNsense 20.7.7_1-amd64
FreeBSD 12.1-RELEASE-p11-HBSD
OpenSSL 1.1.1i 8 Dec 2020



here are the logs:

2021-01-04T12:41:23 unbound[473] [473:0] info: start of service (unrelated 1.13.0).   
2021-01-04T12:41:23 unbound[473] [473:0] review: init module 0: iterator   
2021-01-04T07:56:12 unbound[8518] [8518:0] review: sendto failed: Permission denied   
2021-01-04T03:00:19 unbound[8518] [8518:0] info: start of service (unrelated 1.13.0).   
2021-01-04T03:00:19 unbound[8518] [8518:0] review: init module 0: iterator   
2021-01-04T03:00:19 unbound[8518] [8518:0] review: Reboot of 1.13.0 unrelated.   
2021-01-04T03:00:19 unbound[8518] [8518:0] info: server statistics for thread 1: requestlist max 0 avg 0 exceeded 0 hustled 0   
2021-01-04T03:00:19 unbound[8518] [8518:0] info: server statistics for thread 1: 0 queries, 0 cache responses, 0 recurrences, 0 preference, 0 rejected by ip ratelimiting   
2021-01-04T03:00:19 unbound[8518] [8518:0] info: server statistics for thread 0: requestlist max 0 avg 0 exceeded 0 hustled 0   
2021-01-04T03:00:19 unbound[8518] [8518:0] info: server statistics for thread 0: 0 queries, 0 cache responses, 0 recurrences, 0 prefeasing, 0 rejected by ip ratelimiting   
2021-01-04T03:00:19 unbound[8518] [8518:0] info: service stopped (unrelated 1.13.0).   
2021-01-04T03:00:18 unbound[8518] [8518:0] info: start of service (unrelated 1.13.0).   
2021-01-04T03:00:18 unbound[8518] [8518:0] review: init module 0: iterator   
2021-01-04T03:00:18 unbound[8518] [8518:0] review: Reboot of 1.13.0 unrelated.   
2021-01-04T03:00:18 unbound[8518] [8518:0] info: server statistics for thread 1: requestlist max 0 avg 0 exceeded 0 hustled 0   
2021-01-04T03:00:18 unbound[8518] [8518:0] info: server statistics for thread 1: 0 queries, 0 cache responses, 0 recurrences, 0 prefeasing, 0 rejected by ip ratelimiting   
2021-01-04T03:00:18 unbound[8518] [8518:0] info: server statistics for thread 0: requestlist max 0 avg 0 exceeded 0 hustled 0   
2021-01-04T03:00:18 unbound[8518] [8518:0] info: server statistics for thread 0: 0 queries, 0 cache responses, 0 recurrences, 0 prefeasing, 0 rejected by ip ratelimiting   
2021-01-04T03:00:18 unbound[8518] [8518:0] info: service stopped (unrelated 1.13.0).   
2021-01-04T03:00:18 unbound[8518] [8518:0] info: start of service (unrelated 1.13.0).

[franco]

Again: fetch latest updates, restart Unbound from GUI.


Cheers,
Franco

[miruoy]

Because it's part of the official 20.7.7 now.

Nice!

[Tol Phobos]

Because it's part of the official 20.7.7 now.
Fetch latest updates, restart Unbound from GUI.

unbound 1.13.0_1 deployed for 1 day without any trouble. Seems OK.
Thanks franco !

[dcol]

This was driving me nuts with all kinds of weird errors and slow responding servers until I noticed that unbound was stopped in the Dashboard. Applied patch and seems ok now. Thanks again @franco

[toxic]

Hi toxic, thanks for sharing the set-up, but for what I know (really little as I'm learning), I think is missing the test to see if the unbound service is working. How the machine know that unbound has stop? Thats not done by the test?

Regards

I was baffeled by this as well but my current understanding is that it's meant to keep a process alive anyway, and you give it the pid file if you look at my config. So it's able to read the file and check that there is indeed a process with this pid, if not, then it uses start command and probably stop before...

It did detect me killing the service and did restart it, so pidfile is enought from what I understand, but I agree that's either "too intuitive" or maybe not explicit enough in the config gui...

Nevertheless, I got the _1 update as well, dunno if the monit service or the update did the trick but I'm fine now

Not sure why there is not a monit entry by default for all core services, even disabled, so we just have to enable it when needed...

[dcol]

Would be nice if someone could post a Monit How-To for core services like unbound. and restart the service.

[RDO]

This just happened to me again today. I am up with 20.7.7_1. This has happened quite a few times with me. I am a newbie with OPNsense. Please let me know what I can do to supply more info.

[Greelan]

Check for updates as you may not have the patch - 20.7.7_1 was released before the patch, and then the patch later added

[qwei]

unbound 1.13.0_1 installed yesterday. Still crashed today.

unbound 1.13.0_1 deployed for 1 day without any trouble. Seems OK.
Thanks franco !