Actions
Bug #11854
closed
DNS resolver stopped by himself with fatal error
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
04/27/2021
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
Affected Architecture:
Description
2.5.1-RELEASE (amd64)
built on Mon Apr 12 07:50:14 EDT 2021
Please note that nobody was editing pfsense settings.
Uptime 1 Day 19 Hours 37 Minutes 14 Seconds
Last config change Mon Apr 26 18:47:55 CEST 2021
Apr 27 09:33:40 unbound 23027 [23027:3] fatal error: ./services/outside_network.c:2704: serviced_callbacks: pointer whitelist fptr_whitelist_serviced_query(p->cb) failed
Apr 27 09:33:40 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.113.1 port 53
Apr 27 09:33:40 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.113.1 port 53
Apr 27 09:33:40 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.113.1 port 53
Apr 27 09:33:40 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.113.1 port 53
Apr 27 09:33:40 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.121.1 port 53
Apr 27 09:33:40 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.121.1 port 53
Apr 27 09:33:40 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.113.1 port 53
Apr 27 09:33:40 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.121.1 port 53
Apr 27 09:33:40 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.121.1 port 53
Apr 27 09:33:39 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.121.1 port 53
Apr 27 09:33:39 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.121.1 port 53
Apr 27 09:33:39 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.121.1 port 53
Apr 27 09:33:39 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.121.1 port 53
Apr 27 09:33:39 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.113.1 port 53
Apr 27 09:33:39 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.113.1 port 53
Apr 27 09:33:38 unbound 23027 [23027:0] error: read (in tcp s): Connection refused for 199.249.113.1 port 53
Apr 27 09:33:38 unbound 23027 [23027:0] error: read (in tcp s): Connection refused for 199.249.121.1 port 53
Apr 27 09:33:30 unbound 23027 [23027:2] error: read (in tcp s): Connection refused for 199.249.112.1 port 53
Apr 27 09:33:30 unbound 23027 [23027:2] error: read (in tcp s): Connection refused for 199.249.112.1 port 53
Apr 27 09:33:26 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.120.1 port 53
Apr 27 09:33:26 unbound 23027 [23027:1] error: read (in tcp s): Connection refused for 199.249.120.1 port 53
Apr 27 09:33:21 unbound 23027 [23027:3] error: read (in tcp s): Connection refused for 199.249.112.1 port 53
Apr 27 09:33:21 unbound 23027 [23027:3] error: read (in tcp s): Connection refused for 199.249.112.1 port 53
Apr 27 09:33:21 unbound 23027 [23027:3] error: read (in tcp s): Connection refused for 199.249.112.1 port 53
Apr 27 09:33:21 unbound 23027 [23027:3] error: read (in tcp s): Connection refused for 199.249.112.1 port 53
Apr 27 09:33:21 unbound 23027 [23027:3] error: read (in tcp s): Connection refused for 199.249.112.1 port 53
Apr 27 09:33:21 unbound 23027 [23027:3] error: read (in tcp s): Connection refused for 199.249.112.1 port 53
Apr 27 09:33:21 unbound 23027 [23027:0] info: generate keytag query _ta-4f66. NULL IN
Apr 27 09:33:20 unbound 23027 [23027:3] info: generate keytag query _ta-4f66. NULL IN
Apr 27 09:33:16 unbound 23027 [23027:0] info: start of service (unbound 1.13.1).
Apr 27 09:33:16 unbound 23027 [23027:0] notice: init module 1: iterator
Apr 27 09:33:16 unbound 23027 [23027:0] notice: init module 0: validator
Apr 27 09:33:16 unbound 23027 [23027:0] notice: Restart of unbound 1.13.1.
Apr 27 09:33:16 unbound 23027 [23027:0] info: 4.000000 8.000000 1
Apr 27 09:33:16 unbound 23027 [23027:0] info: 2.000000 4.000000 5
Apr 27 09:33:16 unbound 23027 [23027:0] info: 1.000000 2.000000 6
Apr 27 09:33:16 unbound 23027 [23027:0] info: 0.524288 1.000000 3
Apr 27 09:33:16 unbound 23027 [23027:0] info: 0.262144 0.524288 5
Apr 27 09:33:16 unbound 23027 [23027:0] info: 0.131072 0.262144 5
Apr 27 09:33:16 unbound 23027 [23027:0] info: 0.065536 0.131072 3
Apr 27 09:33:16 unbound 23027 [23027:0] info: 0.032768 0.065536 1
Apr 27 09:33:16 unbound 23027 [23027:0] info: lower(secs) upper(secs) recursions
Apr 27 09:33:16 unbound 23027 [23027:0] info: [25%]=0.216269 median[50%]=0.603573 [75%]=1.79167
Apr 27 09:33:16 unbound 23027 [23027:0] info: histogram of recursion processing times
Apr 27 09:33:16 unbound 23027 [23027:0] info: average recursion processing time 1.205448 sec
Apr 27 09:33:16 unbound 23027 [23027:0] info: server stats for thread 3: requestlist max 34 avg 9.93103 exceeded 0 jostled 0
Apr 27 09:33:16 unbound 23027 [23027:0] info: server stats for thread 3: 65 queries, 36 answers from cache, 29 recursions, 0 prefetch, 0 rejected by ip ratelimiting
Apr 27 09:33:16 unbound 23027 [23027:0] info: 2.000000 4.000000 1
Apr 27 09:33:16 unbound 23027 [23027:0] info: 1.000000 2.000000 2
Updated by Jim Pingle about 3 years ago
- Status changed from New to Closed
Updated by Yann Papouin about 3 years ago
Jim Pingle wrote:
Doesn't look exactly like #11316 but may be related. If not, it's a different Unbound bug that is out of our control. Either way not enough information here to keep open as-is. We'll be moving back to Unbound 1.12.x for now which is more stable. Keep an eye on #11316.
You are right, the issue is the same. It just happen again today after a new WiFi device was connected to our network.
The traceback is also pointing exactly to the commit referenced by you in #11316, basic null check:
https://github.com/NLnetLabs/unbound/commit/7396eff7af10eb85bee277ad06e2858cfa6f553e
I have disabled "Register DHCP leases in the DNS Resolver" until a new pfSense version is released.
Thank you for your feedback.
Actions