Version 2.3.3_1 is available

mifronte

I upgraded via the web GUI dashboard and also received the update failed message in my browser. However, the router rebooted itself before I can get to the console and came up with the new update and all seems fine.

phil.davis

@mifronte:

I upgraded via the web GUI dashboard and also received the update failed message in my browser. However, the router rebooted itself before I can get to the console and came up with the new update and all seems fine.

Note for readers: This is the "normal" behavior. The webGUI code that "monitors" how the upgrade is progressing (showing the log messages coming out…) is a bit too stupid and sometimes gets the idea that something in the upgrade output indicates that the upgrade has failed. But actually the upgrade process is happily detached and running in the background. Eventually the upgrade finishes its processing and kicks off a reboot.

So don't be in a panic when that happens - make yourself a cup of coffee, get a command line somewhere and run "top" to see that some interesting looking things are running, be happy when it reboots.

And yes, the webGUI needs to be made smarter at "guessing" if the upgrade failed.

AWeidner

@phil.davis:

Note for readers: This is the "normal" behavior. The webGUI code that "monitors" how the upgrade is progressing (showing the log messages coming out…) is a bit too stupid and sometimes gets the idea that something in the upgrade output indicates that the upgrade has failed. But actually the upgrade process is happily detached and running in the background. Eventually the upgrade finishes its processing and kicks off a reboot.

So don't be in a panic when that happens - make yourself a cup of coffee, get a command line somewhere and run "top" to see that some interesting looking things are running, be happy when it reboots.

And yes, the webGUI needs to be made smarter at "guessing" if the upgrade failed.

Uhm, that seems not always to be the case. Mine sat for three hours at step 6 of 7 (see my post #7), top showed nothing interesting and i rebooted after getting impatient. Also several users from the site where the updated pfSense box is installed, complained about "not having internet", due to squid being stopped during the unfinished update process.

kpa

The issue seems to be that the update/upgrade process is launched asynchronously from the GUI and the only monitoring the GUI does is the update log by parsing it in an ad-hoc manner and it doesn't pay any attention the status codes returned by the various sub-operations of the update/upgrade.

AWeidner

@kpa:

The issue seems to be that the update/upgrade process is launched asynchronously from the GUI and the only monitoring the GUI does is the update log by parsing it in an ad-hoc manner and it doesn't pay any attention the status codes returned by the various sub-operations of the update/upgrade.

Then maybe there should be an advice, at least for this update, to only use the console based updater until the issue is resolved ???
(no criticism, just asking).

Kamen

Initiated the update (from 2.3.3) via WebGUI and it gave me the failure message BUT it also stopped working (Internet, etc.) I reset the box and no service after that, either. I could not wait hours, so I reverted to my backup router. There is no monitor/keyboard on the pfSense computer, so I'll see when I can get to it.
Just FYI, but very disappointing.
Kamen

zizwiz

My GUI upgrade hung. System still running 2.3.2, GUI showing "unable to check for updates.

ssh update doesn't work:

pkg -v
1.9.4

pfSense-upgrade -d
pkg: No package(s) matching pfSense-kernel-*

Updating repositories metadata…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
ERROR: Unable to compare version of pfSense-repo

jimp

@zizwiz:

My GUI upgrade hung. System still running 2.3.2, GUI showing "unable to check for updates.

ssh update doesn't work:

pkg -v
1.9.4

pfSense-upgrade -d
pkg: No package(s) matching pfSense-kernel-*

Updating repositories metadata…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
ERROR: Unable to compare version of pfSense-repo

That looks like you have some major problem with your local pkg data. Please start a new thread, it is not related to this update.

Supay

@jimp:

@zizwiz:

My GUI upgrade hung. System still running 2.3.2, GUI showing "unable to check for updates.

ssh update doesn't work:

pkg -v
1.9.4

pfSense-upgrade -d
pkg: No package(s) matching pfSense-kernel-*

Updating repositories metadata…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
ERROR: Unable to compare version of pfSense-repo

That looks like you have some major problem with your local pkg data. Please start a new thread, it is not related to this update.

I'm not so sure.

I upgraded to 2.3.3 1 and saw masses of stuff break across my install. My package manager was the main problem, it could no longer connect to check for any updates and it claimed I had no installed packages and was unable to reinstall anything. I tried both from the GUI and command line, both continued to fail. I havecompletely scrubbed and reinstalled my box three times now and I keep getting the same issue. 2.3.3 works fine. Upgrading to 2.3.3 1 leaves it in a horribly broken state where it still routes and all the basic functions are fine, but the package manager appears to broken and unable to do anything. I'm going to have to scrub this again and refuse to upgrade to 2.3.3 1 as if it can't even manage to cleanly upgrade from a fresh install then there is something wrong in there.

Supay

@Kamen:

Initiated the update (from 2.3.3) via WebGUI and it gave me the failure message BUT it also stopped working (Internet, etc.) I reset the box and no service after that, either. I could not wait hours, so I reverted to my backup router. There is no monitor/keyboard on the pfSense computer, so I'll see when I can get to it.
Just FYI, but very disappointing.
Kamen

I had the same issue with my first upgrade. I lost both the package manager and saw breakage all over the place with loss of internet access which seemed DNS related as I could still directly ping IPs, but I couldn't find any reason for this in the logs. I tried a factory default reset but that actually made it worse a I lost even being able to reach the external internet even though again I could see no rules causing this and nothing in the logs. Three complete scrubs of the box and a fresh install leaves with me all routing functions working, but upgrading to 2.3.3 1 breaks the package manager everytime.

Uxorious

Same partial upgrade problem here.
Fixed by: pfSense-upgrade -d

(And as others have mentioned, the new update system is pretty flaky. This is the 2nd time I've had to manually fix it after updating)

Supay

@Uxorious:

Same partial upgrade problem here.
Fixed by: pfSense-upgrade -d

(And as others have mentioned, the new update system is pretty flaky. This is the 2nd time I've had to manually fix it after updating)

The new update system really is flaky. Since 2.3 I have never had so many issues with pfsense. Nearly every update completely breaks my system. I've already tried manually updating using pfSense-upgrade -d over ssh but it just hangs on updating the repositories and eventually states that it is unable to update them. This issue only affects 2.3.3 p1, so I'm going to have to revert back to 2.3.3 and refuse all upgrades until this is fixed. Or consider trying something other than pfsense as this level of breakage is concerning.

JorgeOliveira

Two things that pfSense needs to provide is:

An offline update system or way to mirror the updated packages to own network before the actual upgrade procedure.
Rebuild ISOs with the patch-level fixes.

Yet… I have no reasons for complaint as I have never faced any problems during upgrade. I usually don't update on the first day after updates got available, I normally wait a few days.

Also I have systems where I run 2.3.x development branch and breakage has only occurred in extreme situations. Running the pfSense virtualized and having snapshots to revert back to is a blessing.

happyqban

Updated from the GUI ok, the only issue being that after the first automatic reboot the VPN was still down, I had to manually restart the server pfSense to get it back up and running

bheinsius

Coming back to DNS forwarder not resolving local (fully-qualified) hostnames after upgrade from 2.3.2_1 to 2.3.3_1, it turns out this was caused by:

I had the same issue, not even long domain names worked in the DNS forwarder.
Turns out it is due to a setting in the General Setup "DNS Server override"

"If this option is set, pfSense will use DNS servers assigned by a DHCP/PPP server on WAN for its own purposes (including the DNS Forwarder/DNS Resolver). However, they will not be assigned to DHCP clients."

That was checked on my setup and as such none of my local - full domain forward overrides - worked anymore.
This was never a problem before pfSense 2.3.3_1.

Perhaps it makes sense, but at least unchecking that and manually setting the DNS server setting above that instead of getting it from DHCP immediately fixed the issue I was having.
After that I could query for any of the internal DNS entries again.

Thanks to @wila (https://forum.pfsense.org/index.php?action=profile;u=320599)