2.3.3 is live!
-
How many of you do a "sane" upgrade process. Like reboot first to make sure everything comes up clean before compounding any issues that may be lurking with a upgrade?
-
And also disable packages like Snort/Suricata/pfBlockerNG/etc before the reboot .
-
Just completed the upgrade via the web dashboard with success.
-
Had to do a complete clean install. Restored config and things are working again.
-
How many of you do a "sane" upgrade process. Like reboot first to make sure everything comes up clean before compounding any issues that may be lurking with a upgrade?
Never have and I've never had an upgrade problem in the 2+ years I've been using pfSense.
-
How many of you do a "sane" upgrade process. Like reboot first to make sure everything comes up clean before compounding any issues that may be lurking with a upgrade?
Never have and I've never had an upgrade problem in the 2+ years I've been using pfSense.
I always do. And until this time the pre-upgrade reboot always went fine. This time pfSense wouldn't shutdown. Config write or some such thing had it locked. Dropped to shell and forced it to shutdown.
Just can't wonder how many of the issues people have are due to some obscure issue lurking that would be cleared away by a pre-upgrade reboot. Know it shouldn't be necessary but think it is a good practice anyway.
-
Okay, I finally worked out my issue.
Console option 13 - no go as well, then I've tried option 8 (shell)
pkg update -f
pkg upgrade -f
System complain about about gcc has no blah-blah-blah = n
Seems like working fine now.
Best regards.This is what I had to do as well for just one box.. All my others upgraded just fine.
-
Shouldn't the 'smart' upgrade process take care of this and anything else 'needed'?
And also disable packages like Snort/Suricata/pfBlockerNG/etc before the reboot .
-
I've never disabled my packages either (snort, pfblockerng) and never had an issue with an upgrade.
-
The idea is to prevent anything blocking while doing the update.
