Unbound Restarting every 2 hours after upgrade to 22.7

Started by andrema2, July 29, 2022, 10:01:52 PM

Previous topic - Next topic
Hi

I have seen at Unbound log that it has restarted itself 3 times since 9am today exactly every 2 hours.

I didn't see any other information on the log that could explain it. Any one else having this issue ?

Same here, except it seems to be every 45 minutes, see attachment. I increased verbosity, maybe something comes up.


Does it perhaps restart at dhcp renewal of one the network interfaces?
In theory there is no difference between theory and practice. In practice there is.

Mine frequently renews the wan ip address, which didn't change, and caused unbound to restart.

Level 5 logs just show <code>got control cmd quit</code> for every thread, so not much more info there.


2022-07-30T00:22:10 Informational unbound [12754:0] info: server stats for thread 0: 198 queries, 61 answers from cache, 137 recursions, 0 prefetch, 0 rejected by ip ratelimiting
2022-07-30T00:22:10 Debug unbound [12754:0] debug: comm_point_close of 36: event_del
2022-07-30T00:22:10 Debug unbound [12754:0] debug: cleanup.
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join success 7
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join 7
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join success 6
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join 6
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join success 5
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join 5
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join success 4
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join 4
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join success 3
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join 3
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join success 2
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join 2
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join success 1
2022-07-30T00:22:10 Debug unbound [12754:1] debug: got control cmd quit
2022-07-30T00:22:10 Debug unbound [12754:6] debug: got control cmd quit
2022-07-30T00:22:10 Debug unbound [12754:7] debug: got control cmd quit
2022-07-30T00:22:10 Debug unbound [12754:0] debug: join 1
2022-07-30T00:22:10 Debug unbound [12754:5] debug: got control cmd quit
2022-07-30T00:22:10 Debug unbound [12754:3] debug: got control cmd quit
2022-07-30T00:22:10 Debug unbound [12754:4] debug: got control cmd quit
2022-07-30T00:22:10 Debug unbound [12754:2] debug: got control cmd quit
2022-07-30T00:22:10 Debug unbound [12754:0] debug: stop threads
2022-07-30T00:22:10 Informational unbound [12754:0] info: service stopped (unbound 1.16.1).
2022-07-30T00:22:09 Informational unbound [12754:3] info: send_udp over interface: 127.0.0.1
2022-07-30T00:22:09 Debug unbound [12754:3] debug: using localzone . transparent
2022-07-30T00:22:09 Informational unbound [12754:3] info: receive_udp on interface: 127.0.0.1
2022-07-30T00:22:09 Informational unbound [12754:5] info: send_udp over interface: 127.0.0.1
2022-07-30T00:22:09 Debug unbound [12754:5] debug: using localzone localdomain. transparent
2022-07-30T00:22:09 Informational unbound [12754:5] info: receive_udp on interface: 127.0.0.1

I have checked my logs, and indeed unbound is restarted upon dhcp renewal. Wouldn't it make sense to make it a bit smarter and only restart when the ip address changes?
In theory there is no difference between theory and practice. In practice there is.

Yeah, this is not how it was working before. I upgraded to 22.7_4 and the behaviour is the same. Apparently there is something wrong with the current implementation.

Might be a side effect of https://github.com/opnsense/core/issues/5624

Need to check on Monday.

I need one info from everyone having this issue: under WAN settings, what is your IPv4 type?


Cheers,
Franco

Quote from: franco on July 30, 2022, 09:16:24 PM
I need one info from everyone having this issue: under WAN settings, what is your IPv4 type?

IPv4 Configuration Type: DHCP

I have a fiber setup with internet access on one vlan (a PPPoE connection which uses dhcp) and I have IP TV on another vlan which also uses dhcp, but directly, without PPPoE.
Please let me know if you need more specific info.
In theory there is no difference between theory and practice. In practice there is.

Same issue. Noticed some tcp errors since I was using DoT. Had switch over to dnsmasq in mean time

In my case Unbound restart with a 30 min intervall. Wan uses DHCP on IPv4.

Has anyone checked their IPv4 lease time? It might "coincide" with the reload interval measured.


Cheers,
Franco