"
I hit this again today and was able to look into it a bit more. In my case, it appears the unbound_watcher.py process is dying--I'm assuming this process should run continuously.
after a restart of the service:
I see what appears to be restarts of unbound and the watcher in the logs--not sure why. The last one at 13:27 with the watcher process demonized, but then as the ps above shows, the unbound process was still alive, but no active watcher process.
--Michael
Code Select
$ ps auxww | grep unb
unbound 28040 0.0 1.4 337936 232912 - Ss 13:27 0:51.71 /usr/local/sbin/unbound -c /var/unbound/unbound.conf
root 13628 0.0 0.0 12752 2356 0 S+ 19:27 0:00.00 grep unb
after a restart of the service:
Code Select
ps auxww | grep unb
unbound 3865 56.9 1.4 323600 228148 - Ss 19:28 0:01.29 /usr/local/sbin/unbound -c /var/unbound/unbound.conf
root 9160 14.0 0.1 25768 15548 - Ss 19:28 0:01.56 /usr/local/bin/python3 /usr/local/opnsense/scripts/dhcp/unbound_watcher.py --domain some.domain (python3.9)
root 14811 0.0 0.0 12752 2356 0 S+ 19:28 0:00.00 grep unb
Code Select
$ w
7:33PM up 5 days, 7:27, 1 user, load averages: 0.22, 0.28, 0.28
I see what appears to be restarts of unbound and the watcher in the logs--not sure why. The last one at 13:27 with the watcher process demonized, but then as the ps above shows, the unbound process was still alive, but no active watcher process.
Code Select
2023-05-10T13:27:47-06:00 Notice unbound daemonize unbound dhcpd watcher.
2023-05-10T13:27:47-06:00 Notice unbound [28040:0] notice: init module 0: python
--Michael
