2.3.3 is live!
-
@ajm:
Thanks for the quick response.
I just re-read the relevant note on the DHCP server config page; "Leave blank to use the system default DNS servers: this interface's IP if DNS Forwarder or Resolver is enabled, otherwise the servers configured on the System / General Setup page."
I had been running BIND since the initial setup, but for a week or so prior to the 2.3.3 upgrade had switched to Unbound in an attempt to identify the cause of a general 'lock-up' after ~1-3 weeks running. Disabling BIND did not fix this, and I've reverted to BIND after the upgrade.
It seems that enabling then disabling Unbound may have set a flag somewhere that caused what I'm seeing ?
Update: panic over, I just backed-out of my workaround and it's behaving fine now. Possibly the sequence of changes I made to disable Unbound and re-enable BIND may have a required a restart of DHCP which I didn't do, so it got its knickers in a twist..
Apologies for the noise. I'm a happy camper for now :)
-
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. -
I was skeptical given the numerous upgrade problem threads compounded with my own past experiences of upgrade problems, always having to manually reinstall packages and etc to get things going again.
Performed a CLI (option 13) update to v2.3.3 and much to my astonishment, it just worked.
-
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.
