Random Rebooting in PFsense 2.3.4-RELEASE amd64
-
FWIW, I have an HP 5150 and it's rock solid. I'd suspect a hardware problem. You can download some Linux distro and use it to run memtest for several hours, to see how it holds up.
-
FWIW, I have an HP 5150 and it's rock solid. I'd suspect a hardware problem. You can download some Linux distro and use it to run memtest for several hours, to see how it holds up.
I have a stick with Kali on it so I'll give that a shot and report back on it. I'm worried that there might be an issue with the NIC or its communication to the board. Which would suck a lot. Don't really wanna go through the process of waiting for a return and replacement lol.
-
FWIW, I have an HP 5150 and it's rock solid. I'd suspect a hardware problem. You can download some Linux distro and use it to run memtest for several hours, to see how it holds up.
Ok, so the RAM seems to be running fine. But in the dashboard it appears to report only half the RAM I have installed, regardless of how many sticks I put it.
Also, I have noticed that the device will not reboot for about 12 minutes if I am doing very low intensity tasks, like using this forum. But when I load up a 1080p60fps stream on Twitch, it is only a matter of about 15-30 seconds before it shuts down.
Could this be a problem with the NIC overheating or overloading in some manner? If so, what might I do to troubleshoot it? Still not seeing anything in the /var/crash logs btw
-
Well, NICs are cheap. Do you have another you can try? Also, that memory issue sounds suspicious.
-
Well, NICs are cheap. Do you have another you can try? Also, that memory issue sounds suspicious.
Well, that specific NIC was 70 bucks lol, don't have another available one at the moment unfortunately. And yeah, I'm not sure what to make of it.
-
It seems I was mistaken concerning the RAM. The stickers on it were referring to the size when used in a dual channel config. I am now testing the NIC in a different computer, will see how it performs in my windows box under my max WAN load. I'll also try to find a new single stick to use as I have a feeling it's the ram giving the most issues here.
-
Just a short hint: Did you check if powerd is active? If yes, please deactivate it under System -> Advanced -> Miscellaneous
This solved the issue with my box and pfsense 2.4 -
Just a short hint: Did you check if powerd is active? If yes, please deactivate it under System -> Advanced -> Miscellaneous
This solved the issue with my box and pfsense 2.4Powerd was off on install and during this reboot issue. I turned it on with the adaptive option to test that as well but got no benefit out of that.
The NIC has been working nicely in my other windows box for a day so I don't think it's a problem with the NIC. I am going to borrow a stick of RAM from my roommate and try that without any of the ram I had previously used in my system. If that doesn't work out I'll get one of the other elitedesk's I have at work and try that.
-
Just tried running the system with Powerd off with completely differnet RAM with the same results. Will grab a different EliteDesk tomorrow and try that out. Don't know what else I can do here.
-
OK. So I just tested in a different HP EliteDesk as well as a Dell Optiplex 790. Both machines experienced the same result. Even after I reinstalled pfSense on the hard drive. I can only think that there is some interaction going on with the NIC that when it tries to draw sufficient power it overloads and forces a reboot. I have now placed a return on the quad port NIC and am ordering two 2port NIC's instead. We'll see if I have better luck with these.
-
ALRIGHT. So I returned the Quad Port Intel Gigabit NIC and am now using two dual port gigabit Intel NIC's with the new version of pfSense 2.4.0 . This appears to be running successfully now. I have tested it with the same load I placed against the previous build with the different NIC and it has not rebooted once yet.
The Dual port NIC I got is the Intel PRO/1000 Py Dual Port Server Adapter.
I will provide an update if the issue re-occurs but we appear to be running smoothly now.