@4o4rh said in 24.03 servicewatchdog_cron unbound certificate no such file (service won't start):
servicewatchdog_cron.php:
Simply put : the service watchdog package has no brains.
It's like the guy that has a heart defibrillator in it's pocket, and sees someone lying on the street, not moving, and clearly in agony.
Our guy doesn't think, gets out the manual, apply the electric-patches, arms the defibrillator and activates a 'shock'.
Our guy never noticed that medics were already occupied with our person on the ground, and that the shouldn't have done what he just did.
The result was : one person and several medics electrocuted. More medics are needed now.
More to the point :
The "service watchdog package" is a package that was meant to be used by a pfsense software developer.
During my last 10+ years of pfSense & unbound usage : I never found my 'unbound' in a not running state (except when I was messing around, but I know what I do, and can undo what I've done).
If unbound stops, the reason why it stopped should be found, and resolved.
pfSense itself can, under circumstances like : the admin changed a setting, or an interface went down (why ?) and the unbound gets restarted. If this took some time, and thus the "service watchdog package" kicks in, while unbound was already in a OS generated restarting sequence, everything has been setup to create a perfect mess. The result is classic, "DNS" will be out of order.
And you just discovered a new effect : as pfSense thinks the system didn't rebooted ok, you found this :
"Boot verification failed for default. Netgate pfSense Plus was automatically rebooted back
My advise : get rid of this "service watchdog package".
Or, at least, do what you have to, but don't bother unbound with it.
unbound still fails on you :
Tell us about your pfSense / hardware / settings and I'm sure we'll figure it out.