Random crashes on 2.4.5_1
-
Greetings,
I have been having random crashes on 2.4.5_1 without any real indications as to why. The system stays powered on, but the console display goes black, and both the WAN and LAN interfaces go down. A reboot of the system usually brings it back, but it crashes again within earliest as 5 minutes and latest of 2-3 days. I've checked both syslog and /var/crash without and obvious indications. Crash contains a file titled "minfree" which outputs "2048", aside nothing else is in the directory. It did crash once to the "db>" prompt, I clean installed and recovered my config. The crashes still persist after the clean install.
My initial thought here was a hardware issue, but all of the components have been purchased in the last year aside from the power supply. Memory tests pass, SSD passes SMART, no errors at post. I plugged the power supply into a tester and everything reads fine.
Does anyone have any other ideas on logs/tests to check that may point me in the right direction?
Hardware:
Gigabyte B450M DS3H
Ryzen 7 2700X
16gb Corsair LPX 2133 DDR4
Kingston 120gb SSDPerforming routing, DHCP, firewall, etc. supporting 6 VLANS
Running FreeRadius, OpenVPN Client and Server, Suricata on WAN in passive mode. -
The fact it just up and dies really does sort of scream "hardware failure". However, you could start troubleshooting by turning off and/or disabling the installed packages and run with plain pfSense to see if it still crashes.
I say it screams hardware because 99.5% of the time, when a software piece crashes (like the binary portion of one of the installed packages, for instance), the kernel will log an error message, kill the errant program, and remain up.
The easiest first step is to disable the extra packages to see how that works. My guess is you still get crashes. If you do, then it might be the power supply, it might be failed or failing capacitors on the motherboard, or it could be a bad RAM chip or problem with the SSD.
I didn't see your type of NIC mentioned. That is a remote possibility as well if the NIC driver is sketchy on FreeBSD.
-
Ahh yes, forgot to add the NIC. I've got a genuine Intel dual port NIC in it, not sure on the exact model, I will have to pull it out and look. I have ran this NIC in prior pfsense builds and earlier OS versions without any issues.
-
@zyntec724 said in Random crashes on 2.4.5_1:
Ahh yes, forgot to add the NIC. I've got a genuine Intel dual port NIC in it, not sure on the exact model, I will have to pull it out and look. I have ran this NIC in prior pfsense builds and earlier OS versions without any issues.
That would suggest the NIC is not a likely suspect, then.
If the other hardware ran fine previously, and this behavior just started, I would really lean even more toward a hardware issue.
