Tough time with Unbound

Stewart

@Stewart While I thought that was the issue, it isn't. The started plugging things in and internet isn't working. I come out and it's the same thing. Unbound periodically high cpu even with nothing plugged in. Running dig from the CLI when it doesn't work shows:

/root: dig @127.0.0.1 google.com A

; <<>> DiG 9.12.2-P1 <<>> @127.0.0.1 google.com A
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

It comes and goes.

Edit: When i run clog -f on the resolver.log file I can see it just scrolling through with all the lookups. Then it just stops and no DNS resolution can occur. Then it alll starts again.

Stewart

System log after a reboot shows

Mar 19 10:03:54 	php-fpm 	341 	/services_unbound_advanced.php: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1584626634] unbound[3232:0] error: bind: address already in use [1584626634] unbound[3232:0] fatal error: could not open ports'
Mar 19 10:03:54 	dhcpleases 		kqueue error: unknown
Mar 19 10:09:30 	dhcpleases 		Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such process.

Stewart

@Stewart said in Tough time with Unbound:

/usr/local/sbin/unbound -c /var/unbound/unbound.conf

Removed pfBlockerNG-devel and rebooted but that didn't help. Still the same errors. Went into services and restarted unbound and it started working. Rebooted and it's working. This is the first time I haven't seen error messages. Maybe some setting in pfBlockerNG-devel?