Unbound fails to start after reboot

Started by Claypenguin, December 06, 2021, 12:47:38 PM

Previous topic - Next topic
Hello all,

I reboot my opnsense box regularly with cron and every time I do that unbound fails to come up or rather it starts and then stops again (the logs don't really show any errors). When I start it again in the GUI it works without any problems.

Any ideas what might be causing this?

Regards

A regular reboot would also produce the same error?

What does the log say?

I am just thinking off the top of my head here; do you have any services that is prohibiting Unbound to start. .. If you do a regular reboot, and you see that Unbound does not start - but you can start it manually and everything works fine - how about disabling other services 1-by-1 & reboot; to find out what the culprit service might be? I have no idea which service might be interferring with the Unbound service though :)

Running OPNsense through Proxmox
4 x Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (1 Socket)
24 GB RAM

Hi
is "Dynamic state reset" enabled in Firewall: Settings: Advanced?

I had similar issues when I was running Maltrail. Once I disabled it (because of the notorious memory leak) Unbound started working again after reboots without manual intervention.