Opensense router crashed

Started by DoubleSpeed, November 13, 2024, 04:50:02 PM

Previous topic - Next topic
November 13, 2024, 04:50:02 PM Last Edit: November 13, 2024, 04:59:15 PM by DoubleSpeed
I'm running Opensense on a Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz (2 cores, 4 threads) with 8GBs RAM

Versions
OPNsense 24.7.8-amd64
FreeBSD 14.1-RELEASE-p6
OpenSSL 3.0.15

and everything seems good however without warning Opensense crashed and I lost all access to this as well as the internet access etc.

I power cycled the device and this restarted and reconnected to the internet etc and all seems to be running normally again.

Can anyone advise what logs I should check to look for the possible root causes of this in case it happens again?

Also is there a configuration for Monit that will reboot the device in the event of major failures in services etc?

I had another 'random' crash of my Opensense router today and had to power cycle several times to get the box/Opnsesne to boot and work again. I have Monit 'monitoring' however ideally I would like to get Monit to reboot the device automatically if this happens again, does anyone have a suggested strategy for doing this I don't want to cause my box to reboot unnecessarily however if critical issues occur like I've mentioned it would be good if this were self-healing?

If you have a crash depending on the crash usually Monit nor any automated system that is part of that crashed system will work.

Crash means something unexpected happened and device either went to limbo or rebooted it self. Do you see any crash logs created when the device crashed?

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
APU2D2 - deceased
N5105 - i226-V | Patriot 2x8G 3200 DDR4 | L 790 512G - VM HA(SOON)
N100   - i226-V | Crucial 16G  4800 DDR5 | S 980 500G - PROD

I may have to wait to see if it happens again as I don't remember now what time it was when the router crashed if I get another occurrence I will make sure to dig around the logs once restarted.