Unbound log full of errors

[Antony500]

Hi,

After some days using a fresh OPNsense install, I noticed that unbound logs are just filled up with these errors:

Code Select Expand

2022-02-17T00:53:25 Error unbound [97508:1] error: recvfrom 22 failed: Protocol not available
2022-02-17T00:53:24 Error unbound [97508:1] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:23 Error unbound [97508:3] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:1] error: recvfrom 25 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:0] error: recvfrom 22 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:3] error: recvfrom 24 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:3] error: recvfrom 23 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:3] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:3] error: recvfrom 22 failed: Protocol not available
2022-02-17T00:53:12 Error unbound [97508:1] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:10 Error unbound [97508:1] error: recvfrom 24 failed: Protocol not available
2022-02-17T00:53:09 Error unbound [97508:0] error: recvfrom 23 failed: Protocol not available
2022-02-17T00:53:08 Error unbound [97508:1] error: recvfrom 28 failed: Protocol not available
2022-02-17T00:53:07 Error unbound [97508:1] error: recvfrom 22 failed: Protocol not available
2022-02-17T00:53:06 Error unbound [97508:3] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:05 Error unbound [97508:0] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:04 Error unbound [97508:3] error: recvfrom 23 failed: Protocol not available
2022-02-17T00:53:03 Error unbound [97508:0] error: recvfrom 23 failed: Protocol not available
2022-02-17T00:53:02 Error unbound [97508:3] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:01 Error unbound [97508:3] error: recvfrom 25 failed: Protocol not available

I wonder if this is expected behaviour or something's wrong with my install, I haven't found anything similar to this issue anywhere else. Has anybody else encountered this issue?

[binoix]

Hello,

I see the same thing and experience issues resolving DNS requests, hence blocking connections on clients.
Very annoying and I can't find the reason why so far

[cookiemonster]

If I go to Services > Unbound DNS > Log File and change to "error" from the drop-down, I have nothing showing.
So I don't think is a very common problem. I suggest to check your configuration of Unbound and logging in the system.

[jclendineng]

Check and make sure you are not logging ALL queries...unbound will have hundreds of thousands of requests at times, and if you have all logging enabled it will show stuff like that but most likely it is fine...

Hi,

After some days using a fresh OPNsense install, I noticed that unbound logs are just filled up with these errors:

Code Select Expand

2022-02-17T00:53:25 Error unbound [97508:1] error: recvfrom 22 failed: Protocol not available
2022-02-17T00:53:24 Error unbound [97508:1] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:23 Error unbound [97508:3] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:1] error: recvfrom 25 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:0] error: recvfrom 22 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:3] error: recvfrom 24 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:3] error: recvfrom 23 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:3] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:22 Error unbound [97508:3] error: recvfrom 22 failed: Protocol not available
2022-02-17T00:53:12 Error unbound [97508:1] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:10 Error unbound [97508:1] error: recvfrom 24 failed: Protocol not available
2022-02-17T00:53:09 Error unbound [97508:0] error: recvfrom 23 failed: Protocol not available
2022-02-17T00:53:08 Error unbound [97508:1] error: recvfrom 28 failed: Protocol not available
2022-02-17T00:53:07 Error unbound [97508:1] error: recvfrom 22 failed: Protocol not available
2022-02-17T00:53:06 Error unbound [97508:3] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:05 Error unbound [97508:0] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:04 Error unbound [97508:3] error: recvfrom 23 failed: Protocol not available
2022-02-17T00:53:03 Error unbound [97508:0] error: recvfrom 23 failed: Protocol not available
2022-02-17T00:53:02 Error unbound [97508:3] error: recvfrom 21 failed: Protocol not available
2022-02-17T00:53:01 Error unbound [97508:3] error: recvfrom 25 failed: Protocol not available

I wonder if this is expected behaviour or something's wrong with my install, I haven't found anything similar to this issue anywhere else. Has anybody else encountered this issue?

[binoix]

I was pretty much in a fresh default installation.
I have not found the root cause of these messages, but I found was caused my unbound not to work: "Register DHCP static leases" is causing it to reboot on each new DHCP lease.
-> Unchecking this option made unbound work like charm :)

hope this helps

[jclendineng]

Hmm how fresh? Im on a fresh install and it definitely doesn't do that. Are you sure its "fresh"? Any odd hardware? Static leases doesn't do that...unless something perhaps is corrupted.  Did you try running the health check in the package manager?

[binoix]

Intel NIC, health check was OK yes.
I suspected problems with the NIC drivers (seems others have issues also), and downgraded to 21.7 which seems to have less problems.