OPNsense

493 readers

1 users here now

All discussions about the open source, FreeBSD-based firewall called OPNsense.

founded 1 year ago

MODERATORS

IceBearCushion

Determine shutdown cause (self.opnsense)

submitted 6 months ago by doctorzeromd to c/opnsense

5 comments fedilink hide all child comments

Hi all, I've got a cheap Celeron box running OPNSense and it's been pretty good so far, but I found twice that the device turned off at some point while I was at work, and I have been unable to figure out what's causing it.

The only change was that I enabled Monit to see if I could figure out what was causing crowdsec to stop sometimes but never ended up configuring anything. I've only been running it for a couple months though, so it's possible that that is not related.

I know that on a Mac (based on freebsd, right?) you can determine whether the shutdown reason was a hard shutdown, regular shutdown, or the power cable being unplugged. Is it possible to do that with OPNSense? I'd like to narrow it down to software or hardware ideally.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 6 months ago* (last edited 6 months ago)

The system logs go straight from No IP Change detected to the next boot, so a crash or failure seem likely.

I think so. If it was shut down orderly, there should be log entries for the shutdown.

It's a passively cooled computer, is there any way that I can determine whether a high temp forced the computer down?

Some bios have logging. I remember a Asrock board with bmc which remembered CPU too hot events. It depends on the board, normally I would say: I don't think so.

If it is a hardware issue: boot a Live Linux from an USB-stick. Memtest86, long smart test,fsck, CPU burnin test, a network load test could show failures. But it is just wild guessing at this point from my side. Sorry.

CPU temps in opnsense: system / settings/ misc/ thermal. Not helpful but maybe interesting.