unbound restarts anyone?
-
After upgrading to 23.01 I see that my
ServiceWatchdog
restartsunbound, It happens not too often 1-2 times a day.Mar 10 09:30:03 php-cgi 7499 servicewatchdog_cron.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1678469403] unbound[47459:0] error: bind: address already in use [1678469403] unbound[47459:0] fatal error: could not open ports'Is anybody else seeing this?
I did find this post but is it really a good idea not to add
unboundtoServiceWatchdog?Thx
-
@chudak I don't even have servicewatchdog installed.. What are you needing it for - what services are stopping that need to be restarted? That you would need it in the first place?
-
@johnpoz said in unbound restarts anyone?:
@chudak I don't even have servicewatchdog installed.. What are you needing it for - what services are stopping that need to be restarted? That you would need it in the first place?
We’ll the answer is obvious - restart unbound
-
@chudak said in unbound restarts anyone?:
We’ll the answer is obvious - restart unbound
I have never had an issue that I can recall of unbound just stopping to be honest.. But you could for sure run into a race type condition issue where if something restarted unbound, say dhcp leases or something - and servicewatchdog said oh, unbound isn't running let me restart it.
-
@johnpoz
and other packages as well:Arpwatch Daemon
ntopngThe point is that it has not been like this before 23.01
-
@chudak said in unbound restarts anyone?:
The point is that it has not been like this before 23.01
I must restart clamd, snort and unbound once more by hand after upgrading to 23.01 and then I have to reboot it.
After the reboot it was stating again like before automatically. -
@chudak If you have DHCP lease registration then it will restart at each renewal. In that case I'd remove it from watchdog.
If not, then I'd check to see whether it's stopping (logged) or crashing.
I don't think it results in the processing stopping but if you use forwarding in DNS Resolver then uncheck DNSSEC, and some have reported they need to uncheck the option to use TLS as well.
-
@steveits said in unbound restarts anyone?:
@chudak If you have DHCP lease registration then it will restart at each renewal. In that case I'd remove it from watchdog.
If not, then I'd check to see whether it's stopping (logged) or crashing.
I don't think it results in the processing stopping but if you use forwarding in DNS Resolver then uncheck DNSSEC, and some have reported they need to uncheck the option to use TLS as well.
Thx for the reply.
I actually don't have either DHCP lease registration or DNSSEC checked.But that's all related ti pfBNG. And I do see other packages as well being restarted.
-
@chudak said in unbound restarts anyone?:
see other packages as well being restarted
If they're all at the same time, an interface going down/up can do that.
"address already in use" is basically saying unbound is already running and you (watchdog) can't start it again.
-
@chudak Yeah. We thought we had sorted out unbound issues on v23. Had a complete crash of unbound. Never once saw that on any box with v22. Unbound just isn't good under v23. I wish I could have v23 with old unbound.
-
I applied all recommended patches and so far in last 2 days see no restarts!
