21.02 Sudden lockup
-
@mcury I don't think is a pfblocker issue TBH.
Mine keeps locking up even though is fully disabled, I am now going to uninstall it. -
@ffuentes Try to set the pfblocker cron settings to run once a day, instead of one hour to confirm if the problem will happen to you again.
Or completely remove the pfblockerng package. If it happens again even without the package installed (not only disabled). We will have a better understanding about it.. -
@mcury I just uninstalled it. Let see how far the rabbit holes go. :/
-
@ffuentes said in 21.02 Sudden lockup:
@mcury I just uninstalled it. Let see how far the rabbit holes go. :/
Let's hope that we all here have the same problem, one fix is faster than two or more :)
-
@mcury I also disabled and got a lockup again just now. This is bad news, folks. I don’t think it’s pfBlockerNG either.
How do I downgrade back to 2.4.5p1?
-
@bldnightowl said in 21.02 Sudden lockup:
@mcury I also disabled and got a lockup again just now. This is bad news, folks. I don’t think it’s pfBlockerNG either.
How do I downgrade back to 2.4.5p1?
Try to remove pfblockerng package, just to make sure tick that setting to remove the configuration too, this option is inside pfblockerng.
-
How do I downgrade back to 2.4.5p1?
Reinstall & restore Config Backup
-
@mcury said in 21.02 Sudden lockup:
@ffuentes said in 21.02 Sudden lockup:
@mcury I just uninstalled it. Let see how far the rabbit holes go. :/
Let's hope that we all here have the same problem, one fix is faster than two or more :)
Completely agree. I am trying to avoid going back to the previous version to try and help narrow this down.
But is really causing a lot of pain as it seems to be very consistent. (That's good news in a technical way)I have a console up and running via USB to see if I can catch anything, but is a HARD lockup. You can't get any output at all.
-
@ffuentes said in 21.02 Sudden lockup:
@mcury said in 21.02 Sudden lockup:
@ffuentes said in 21.02 Sudden lockup:
@mcury I just uninstalled it. Let see how far the rabbit holes go. :/
Let's hope that we all here have the same problem, one fix is faster than two or more :)
Completely agree. I am trying to avoid going back to the previous version to try and help narrow this down.
But is really causing a lot of pain as it seems to be very consistent. (That's good news in a technical way)I have a console up and running via USB to see if I can catch anything, but is a HARD lockup. You can't get any output at all.
Hm, the console also stops? You can't reboot it through the console?
Did you upgrade from 2.4.5p1 or performed a clean 21.02 install? -
@mcury I did an upgrade. 2.4.5p1 -> 21.02.
One hour later, instant lockup, and happily ever since (not... but you get the idea
)Worth mentioning that after hours of troubleshooting I did do a factory default, and reconfigure everything. Still the same behavir.
-
@ffuentes I've been watching this thread all day. It seems the focus is turning to pfblockerNG, yet I have uninstalled all my packages. Removing PfblockerNG-devel did lengthen the time between lockups, it did not eliminate the problem.
edit: I am rebooting via USB cable->putty->console
-
@bulfinch Thanks for this update.
I suspect not a pfblocker issue, but something a bit deeper.
When we get lockups like this, sometimes it hints a kernel issue.
Maybe a wild process, but even then you get a ping response when the OS is running low on resources. -
@ffuentes @Bulfinch I tried to upgrade from 2.4.5p1, got a lot of errors, so decided to perform a clean install and configure everything from scratch..
I suggest you guys do the same, I lost a few hours yesterday reinstalling everything.. but I'm not getting this 'lockups'.
The only thing I restored from my 2.4.5p1 backup was the aliases..I saved a screenshot from my update from 2.4.5p1 to 21.02 (this screen doesn't show all the errors, there were plenty more..
-
@mcury For me, the console has never frozen. And I can still access the WAN from the console (pings, etc.) -- it's the LAN and the DNS Resolver that go down.
I have fully removed pfBlockerNG and will give this one more shot before throwing in the towel. But if the root cause really is pfBlockerNG somehow, I hope that gets resolved very quickly -- it's very important to have that.
How can I downgrade though to 2.4.5p1 though if I can't reach the internet because my pfSense is down? I did backup the configuration before I upgraded to 21.02, but that backup doesn't include the full pfSense software does it?
-
@mcury said in 21.02 Sudden lockup:
, so decided to perform a clean install and configure
I may need to move in this direction. The family is rising up like the French resistance. I fear for my head.
-
@mcury do you know how many hours I have to invest in a reconfigure?
I am not sure I want to do that...Its going to be painful. very painful.
-
@bulfinch said in 21.02 Sudden lockup:
@mcury said in 21.02 Sudden lockup:
, so decided to perform a clean install and configure
I may need to move in this direction. The family is rising up like the French resistance. I fear for my head.
kkkkkk, be careful, nowadays, a family without internet can be real dangerous :)
I'm in the same boat, this SG-3100 is a home device, my family went berzerk mode.. You should do it drinking a beer
@ffuentes said in 21.02 Sudden lockup:
@mcury do you know how many hours I have to invest in a reconfigure?
I am not sure I want to do that...
Its going to be painful. very painful.I took some minutes thinking about that, how bad was going to be, but now I'm feeling better that I did it..
-
@mcury I am curious, how do you do a fresh install with an SG-3100
-
@ffuentes Open a TAC ticket with the support, go.netgate.com is the link to do it, click in support and create a ticket asking for the 21.02 version, they will provide a link to download.
You will need a pendrive, If you are in Windows, just download 7zip to extract the file, and Balena Etcher to burn that image to the pendrive.
Reinstall instructions:
https://docs.netgate.com/pfsense/en/latest/solutions/sg-3100/reinstall-pfsense.html -
@mcury u know... after some serious thoughts. I think is time for me to move on and find a new solution. Thanks for your help.
