1
22.7 Legacy Series / [Fixed] Unbound did not start - how to debug?
« on: August 10, 2022, 03:48:02 pm »
Hello 👋
I have two OPNsense, which only hang with one interface in the network, on which the unbound service no longer starts since the 22.x.
Both installed on a Hyper-V 2012R2 and 2019 host.
The Unbound Protocol is empty (cleared, but it comes no new entry's).
Reset to Factory-Default and reconfigure interface only, Unbound did not start.
How to search, why Unbound did not start.
Thanks for help - Meik
I have two OPNsense, which only hang with one interface in the network, on which the unbound service no longer starts since the 22.x.
Both installed on a Hyper-V 2012R2 and 2019 host.
Code: [Select]
Date
Severity
Process
Line
2022-08-10T14:24:33 Error configd.py [305016fc-62f2-4ec1-8c49-9f09771a06c8] Script action stderr returned "b"pgrep: Cannot open pidfile `/var/run/unbound.pid': No such file or directory""
2022-08-10T14:24:33 Notice configd.py [305016fc-62f2-4ec1-8c49-9f09771a06c8] request Unbound status
2022-08-10T14:24:28 Debug configd.py OPNsense/Unbound/* generated //usr/local/etc/unbound_dhcpd.conf
2022-08-10T14:24:28 Debug configd.py OPNsense/Unbound/* generated //var/unbound/root.hints
2022-08-10T14:24:28 Debug configd.py OPNsense/Unbound/* generated //usr/local/etc/unbound.opnsense.d/miscellaneous.conf
2022-08-10T14:24:28 Debug configd.py OPNsense/Unbound/* generated //usr/local/etc/unbound.opnsense.d/domainoverrides.conf
2022-08-10T14:24:28 Debug configd.py OPNsense/Unbound/* generated //var/unbound/private_domains.conf
2022-08-10T14:24:28 Debug configd.py OPNsense/Unbound/* generated //usr/local/etc/unbound.opnsense.d/dot.conf
2022-08-10T14:24:28 Debug configd.py OPNsense/Unbound/* generated //tmp/unbound-blocklists.conf
2022-08-10T14:24:28 Notice configd.py generate template container OPNsense/Unbound/core
2022-08-10T14:24:28 Notice configd.py [9290ca78-7411-4ef0-976a-28e390648445] generate template OPNsense/Unbound/*
2022-08-10T00:12:22 Notice configd.py [0b216cc1-e978-4b48-8ded-18428ea0abe2] Unbound cache flush
2022-08-09T20:45:57 Notice configd.py [c7bf4753-f82c-4712-aeba-db93fee1cc8b] Unbound cache flush
------------------------
PID
USERNAME
PRI
NICE
SIZE
RES
STATE
C
TIME
WCPU
COMMAND
14274 root 102 0 32M 19M CPU0 0 80:30 99.62% /usr/local/sbin/unbound-checkconf /var/unbound/unbound.conf
14167 root 52 0 13M 2284K wait 0 0:00 0.00% /bin/sh /usr/local/opnsense/scripts/unbound/start.sh
14121 root 52 0 13M 2144K wait 0 0:00 0.00% /usr/local/bin/flock -n -E 0 -o /tmp/unbound_start.lock /usr/local/opnsense/scripts/unbound/start.sh
The Unbound Protocol is empty (cleared, but it comes no new entry's).
Reset to Factory-Default and reconfigure interface only, Unbound did not start.
How to search, why Unbound did not start.
Thanks for help - Meik