Error: can't bind socket: Address already in use for 127.0.0.1 port 5335

[wd9895]

System: Pi 2B with Raspios Bullseye + PiHole + Unbound

Expected Behaviour:

Unbound -v should report no warning.

Actual Behaviour:

Unbound -v reports a port error but system works fine.
"error: can't bind socket: Address already in use for 127.0.0.1 port 5335"

Debug Token:

https://tricorder.pi-hole.net/UcMfR6oU/

Replies in english or german are welcome.

[jfb]

What is the complete output of the following command from the Pi terminal:

sudo grep -v '#\|^$' -R /etc/unbound/unbound.conf*

[wd9895]

pi@x-pihole:~ $ sudo grep -v '#\|^$' -R /etc/unbound/unbound.conf*
/etc/unbound/unbound.conf:include-toplevel: "/etc/unbound/unbound.conf.d/*.conf"
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf:server:
/etc/unbound/unbound.conf.d/root-auto-trust-anchor-file.conf:    auto-trust-anchor-file: "/var/lib/unbound/root.key"
/etc/unbound/unbound.conf.d/pi-hole.conf:server:
/etc/unbound/unbound.conf.d/pi-hole.conf:    verbosity: 0
/etc/unbound/unbound.conf.d/pi-hole.conf:    interface: 127.0.0.1
/etc/unbound/unbound.conf.d/pi-hole.conf:    port: 5335
/etc/unbound/unbound.conf.d/pi-hole.conf:    do-ip4: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    do-udp: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    do-tcp: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    do-ip6: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    prefer-ip6: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    harden-glue: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    harden-dnssec-stripped: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    use-caps-for-id: no
/etc/unbound/unbound.conf.d/pi-hole.conf:    edns-buffer-size: 1472
/etc/unbound/unbound.conf.d/pi-hole.conf:    prefetch: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    num-threads: 2
/etc/unbound/unbound.conf.d/pi-hole.conf:    so-rcvbuf: 1m
/etc/unbound/unbound.conf.d/pi-hole.conf:    serve-expired: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: 192.168.0.0/16
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: 169.254.0.0/16
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: 172.16.0.0/12
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: 10.0.0.0/8
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: fd00::/8
/etc/unbound/unbound.conf.d/pi-hole.conf:    private-address: fe80::/10
/etc/unbound/unbound.conf.d/pi-hole.conf:    msg-cache-size: 128m
/etc/unbound/unbound.conf.d/pi-hole.conf:    rrset-cache-size: 256m
/etc/unbound/unbound.conf.d/pi-hole.conf:    auth-zone:
/etc/unbound/unbound.conf.d/pi-hole.conf:       name: "."
/etc/unbound/unbound.conf.d/pi-hole.conf:fallback-enabled: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:       for-downstream: no
/etc/unbound/unbound.conf.d/pi-hole.conf:       for-upstream: yes
/etc/unbound/unbound.conf.d/pi-hole.conf:       zonefile: "/var/lib/unbound/root.zone"

[jfb]

@wd9895

Expected Behaviour:

Unbound -v should report no warning.

This is not the expected behavior. That is just the way unbound works, apparently. From my install:

unbound -v
[1673455265] unbound[29700:0] notice: Start of unbound 1.13.1.
[1673455265] unbound[29700:0] error: can't bind socket: Address already in use for 127.0.0.1 port 5335
[1673455265] unbound[29700:0] fatal error: could not open ports

You can check configuration with the following, which I anticipate will show no errors:

unbound-checkconf

And check unbound status, which I also anticipate will show no problems:

sudo service unbound status

[wd9895]

You're right. No errors and status "active (running)"

I was just a bit worried about the Unbound message.
Thanks !