Opnsense 20.7 on QOTOM i5

[curto]

Guys, NOOB here - rolled out a QOTOM i5 with 20.7 - very basic config - only a single port forward and upnp whilst we are testing.

At least once a week the system appears to shutdown/sleep and the only reliable method we have found to wake it up is to remove power and then power it back on.

This has now happened 3 weeks in a row and appears to happen only on the weekends.

I have found a number of online guides that talk about various BIOS settings to stop the hardware sleeping. I enabled these on one unit (we have 3 units in total - but only one live at this stage whilst we test)

We have set the various BIOS settings, swapped in one of the other units and then put the device that was having the problems onto our test bench and let it sit there - not traffic going through it - and it was fine for a week (with a monitor connected) - no shutdowns etc.

Is there a log setting we can set on OpnSense to have it write activity logs etc to disc prior to a shutdown (if that is what is happening)  so can try and troubleshoot this ? Or can we redirect the logs out to a remote syslog server etc ?

Craig

[FingerlessGloves]

I've had 2 Qotom devices and current one is the Q535G6 u7100

Mine doesn't do this, which one do you have?

[curto]

Thanks for the reply Jonny

I have 3 of the

NO RAM NO SSD, Q555G6 7200U NO WiFi

I have one running as my home Untangle Firewall - it has worked without missing a beat for about 4 months, i have another that i have installed with OpnSense for a friend - this is the one giving me problems - the 3rd one is a hot spare, which i use to make changes on and then drop in for the OpnSense unit to try and identify/resolve issues.

I added Corsair 8GB RAM to each of them and Samsung 850 Pro SSDs - all bought at the same time from the same vendor.

Initially i thought it was a hardware issue so i took the first unit that appeared to "fail" and swapped in the hot spare, then put the apparent failed unit on my testbench and had two PCs hammer data through it for a week - no issues.

I then started thinking it was some form of hardware sleeep setting so i did some searching and found a few comments across the web about disabling cstates and other hardware sleep control - so turned all of these off and then tested for another week (meanwhile the 2nd unit with OpnSense on my friends site was shutting down once a week or so - does not respond to pings, does not pass any traffic, can not log into web interface.

Set it up to log to a syslog box but nothing of interest.

So took the box with the BIOS options set to disabled and swapped it in - and the same thing happened again - so i have now started thinking it is something to do with OpnSense.

Again thinking it may be some form of sleep issue - i setup a cron job on OpnSense to restart the captive portal every 10 minutes (we do not use the catpive portal) - thinking this would stop it going into a sleep state if this was what was happening - but no difference.

Any ideas ?

Craig