Twice this month, I have lost WAN. PPPoE was still running (according to the UI), but restarting it fixed it.
Then today UBound stopped for no apparent reason.
I expect services to restart, when there is a problem. Or at least allow for a restart if certain conditions are not met, like pinging an external server.
Don't know what hardware you're using but my X86 running Opnsense never needs any rebooting or shows symptoms you described.
It only gets rebooted when I apply firmware updates.
It's a Ryzen Mini-ITX board. I don't believe there is anything wrong with it. Worked great for two years, but with the occasional loss of services.
Even if it was caused by a hardware issue, I would have expected services to attempt to restart.
Quote from: LogicEthos on March 17, 2021, 12:07:26 AM
Twice this month, I have lost WAN. PPPoE was still running (according to the UI), but restarting it fixed it.
Then today UBound stopped for no apparent reason.
I expect services to restart, when there is a problem. Or at least allow for a restart if certain conditions are not met, like pinging an external server.
Easy enough to do with monit, that's what its there for.
monit seems to be about sending alerts/e-mails.
When a service is set to run as default, I would expect that service to restart if it crashed, or at least have the option to do that.
Can monit do that for Unbound? I couldn't find any examples.
Monit can watch and restart services as well as send mails.
Quote from: LogicEthos on March 17, 2021, 12:07:26 AM
Twice this month, I have lost WAN. PPPoE was still running (according to the UI), but restarting it fixed it.
Then today UBound stopped for no apparent reason.
I expect services to restart, when there is a problem. Or at least allow for a restart if certain conditions are not met, like pinging an external server.
Is that using a realtek NIC? Have you looked at the logs to verify if the RE driver is crashing?