Core-159: error: can't bind socket: Address already in use for port 8953

Hi all,
I just did the update to 159 and I am experiencing a loss of internet connection. My clients most often show no route to host. My feeling is it’s unbound. Here are a few snippets from the machine (commands executed as root)

unbound -d -v
[1630743646] unbound[17775:0] notice: Start of unbound 1.13.1.
Sep 04 10:20:46 unbound[17775:0] error: can't bind socket: Address already in use for port 8953
Sep 04 10:20:46 unbound[17775:0] error: cannot open control interface 8953
Sep 04 10:20:46 unbound[17775:0] fatal error: could not open ports
dhcpcd -k red0
sending signal ALRM to pid 9229
waiting for pid 9229 to exit
dhcpcd -n red0
dhcpcd-9.4.0 starting
DUID 00:04:00:00:00:00:00:00:00:00:00:00:00:25:.......
red0: IAID 90:bd:.......
red0: adding address fe80::225:90ff:febd:8654
ipv6_addaddr1: Permission denied
red0: soliciting an IPv6 router
red0: soliciting a DHCP lease
red0: offered blah
red0: probing address blah
red0: leased blah for 5400 seconds
red0: adding route to blah/24
red0: adding default route via blah
[  OK  ]tatic routes...
[  OK  ]g firewall
DNS NOT functioning... Trying to sync time with (
forked to background, child pid 13367

Any ideas? All help and hints appreciated an welcome.
Thanks a lot in advance

I think you are seeing this message because unbound -d -v is trying to start unbound in verbose debug mode but it is already running.

Running the command:-

ps aux | grep unbound

I see the following

nobody    1527  0.6  0.5  22488 20648 ?        Ss   Aug27  82:11 /usr/sbin/unbound
root      1555  0.0  0.0      0     0 ?        I    14:38   0:00 [kworker/u8:1-events_unbound]
ahb       2166  0.0  0.0   6436  1952 pts/0    S+   14:47   0:00 grep unbound
root      2656  0.0  0.2  15508 11412 ?        S    Aug27   1:07 /usr/bin/python3 /usr/sbin/unbound-dhcp-leases-bridge -d

the first line of which which indicates that unbound is running.

What status do you see on your DNS menu page.

It’s fixed. But I don’t know what is wrong. I removed a DNS server (I am not using my ISP’s ones) and re-added it (both via UI). Now it working. Crazy.

But thanks a lot for helping.


Possible that it may have been a rare occurrence of unbound already running and the service thought that it still wasn’t or something like that. So yeah, a reboot has very high chances of solving this kind of problem and glad to know that it got fixed :+1: