2.3.3 is live!
-
If you were on RC before you might want to wait.
I got it to work but it took some extra steps.
I am on 2.3.3-RC as well and console update doesn't find anything to update.
Seems I have to wait as well?
I'd like to go to stable now (instead of development), is that possible now without a reinstall? -
On my 2.3.3-RC that was on "Stable" (because that is what was done when 2.3.3-DEVELOPMENT became 2.3.3-RC - to avoid ending up on 2.3.4-DEVELOPMENT), I:
- switched to development on GUI Update Settings
- used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
- switched back to stable on GUI update settings
- used console option 13 again, and it found the "right" stable stuff, said "y" to upgrade
I am not sure if that sequence should really be needed, but for me it got the system recognize the "new stable" and upgrade to it.
-
On my 2.3.3-RC that was on "Stable" (because that is what was done when 2.3.3-DEVELOPMENT became 2.3.3-RC - to avoid ending up on 2.3.4-DEVELOPMENT), I:
- switched to development on GUI Update Settings
- used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
- switched back to stable on GUI update settings
- used console option 13 again, and it found the "right" stable stuff, said "y" to upgrade
I am not sure if that sequence should really be needed, but for me it got the system recognize the "new stable" and upgrade to it.
worked for me as well, thank you!
-
I am not sure if that sequence should really be needed
Yeah I'm pretty sure the pkg thing urgently needs a brain transplant.
-
just upgraded my self.. took a bit but not all that long if you take into account all the changes. Pretty sure it said something like 89 packages to be upgraded..
Sofar all looks good…
The graphs scaling seems to be off? Pretty thin graphs.. Am I missing something here?
edit: Cleared cache - now looks normal.. Duhhh ;)
-
Spectacular job once again pfsense team!
-
Everything appears to have gone ok.
-
I had to switch to development branch once and then back to stable until I was offered the update to final 2.3.3 over the 2.3.3-RC I previously had. There were some error messages (the update page outright showed "Upgrade failed" after starting the update), the update progress indicators and the output didn't quite match what was actually done, the system rebooted before the output indicated a succesful install of the required packages. The update worked fine though after the reboot.
-
Am I the only one who is still showing 2.3.2 on the system info, but 2.3.3 in the update tab? I am not sure if this is a big deal.
-
Am I the only one who is still showing 2.3.2 on the system info, but 2.3.3 in the update tab? I am not sure if this is a big deal.
My dashboard is updated with 2.3.3-RELEASE (amd64)
-
Am I the only one who is still showing 2.3.2 on the system info, but 2.3.3 in the update tab? I am not sure if this is a big deal.
Try what Phil said above-
On my 2.3.3-RC that was on "Stable" (because that is what was done when 2.3.3-DEVELOPMENT became 2.3.3-RC - to avoid ending up on 2.3.4-DEVELOPMENT), I:
- switched to development on GUI Update Settings
- used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
- switched back to stable on GUI update settings
- used console option 13 again, and it found the "right" stable stuff, said "y" to upgrade
I am not sure if that sequence should really be needed, but for me it got the system recognize the "new stable" and upgrade to it.
Ive got one box that seems to want to stick to 2.3.2 as well.. Fought with it several times yesterday. Its nano and really slow.. Im trying this now. Ill update if this works for this one. All my others upgraded without a hitch.
-
I got the 2.3.3 Upgrade notification and after confirming, it seemed to go through the gyrations to do so but after my dual-Atom pfsense box automatically rebooted (and subsequent manual reboots by me), the version shows to be 2.3.2 RELEASE-P1 and "Unable to check for updates". Will keep trying but unsure how to proceed.
-
Am I the only one who is still showing 2.3.2 on the system info, but 2.3.3 in the update tab? I am not sure if this is a big deal.
Try what Phil said above-
On my 2.3.3-RC that was on "Stable" (because that is what was done when 2.3.3-DEVELOPMENT became 2.3.3-RC - to avoid ending up on 2.3.4-DEVELOPMENT), I:
- switched to development on GUI Update Settings
- used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
- switched back to stable on GUI update settings
- used console option 13 again, and it found the "right" stable stuff, said "y" to upgrade
I am not sure if that sequence should really be needed, but for me it got the system recognize the "new stable" and upgrade to it.
Ive got one box that seems to want to stick to 2.3.2 as well.. Fought with it several times yesterday. Its nano and really slow.. Im trying this now. Ill update if this works for this one. All my others upgraded without a hitch.
As far as I can tell the system has been updated but the dashboard is still reporting 2.3.2 as my picture shows.
-
Am I the only one who is still showing 2.3.2 on the system info, but 2.3.3 in the update tab? I am not sure if this is a big deal.
Try what Phil said above-
On my 2.3.3-RC that was on "Stable" (because that is what was done when 2.3.3-DEVELOPMENT became 2.3.3-RC - to avoid ending up on 2.3.4-DEVELOPMENT), I:
- switched to development on GUI Update Settings
- used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
- switched back to stable on GUI update settings
- used console option 13 again, and it found the "right" stable stuff, said "y" to upgrade
I am not sure if that sequence should really be needed, but for me it got the system recognize the "new stable" and upgrade to it.
Ive got one box that seems to want to stick to 2.3.2 as well.. Fought with it several times yesterday. Its nano and really slow.. Im trying this now. Ill update if this works for this one. All my others upgraded without a hitch.
As far as I can tell the system has been updated but the dashboard is still reporting 2.3.2 as my picture shows.
Do
cat /etc/version*and check what's there.
-
As far as I can tell the system has been updated but the dashboard is still reporting 2.3.2 as my picture shows.
Nah- Im seeing the same thing on my only "nano" box..
Duplicate slice required!! Before starting the upgrade process, the currently mounted nanobsd partition needs to be cloned to the secondary partition, where the update will happen After installation a reboot will be required to switch partition. >>> Cleaning secondary partition... done. >>> Duplicating current slice... done. >>> Restoring slice label... done. >>> Testing duplicated partition integrity... done. >>> Mounting second partition to run upgrade... done. >>> Copying resolv.conf to upgrade partition... done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... Unable to update repository pfSense-core Updating pfSense repository catalogue... Unable to update repository pfSense All repositories are up-to-date. pkg: Repository pfSense-core cannot be opened. 'pkg update' required pkg: Repository pfSense cannot be opened. 'pkg update' required Checking for upgrades (0 candidates): . done Processing candidates (0 candidates): . done Checking integrity... done (0 conflicting) Your packages are up to date. >>> Locking package pfSense-pkg-Shellcmd... done. >>> Locking package pfSense-pkg-routed... done. >>> Unlocking package pfSense-pkg-Shellcmd... done. >>> Unlocking package pfSense-pkg-routed... done. >>> Setting secondary partition as active... done. Upgrade is complete. Rebooting in 10 seconds. >>> Locking package pfSense-kernel-pfSense_wrap... done. Success[2.3.2-RELEASE][admin@x0x0x]/root: cat /etc/version*
2.3.2-RELEASE
Tue Sep 27 12:13:32 CDT 2016Tried "Pkg Upgrade" with this end response-
pkg: Cannot get an advisory lock on a database, it is locked by another process
-
Am I the only one who is still showing 2.3.2 on the system info, but 2.3.3 in the update tab? I am not sure if this is a big deal.
Try what Phil said above-
On my 2.3.3-RC that was on "Stable" (because that is what was done when 2.3.3-DEVELOPMENT became 2.3.3-RC - to avoid ending up on 2.3.4-DEVELOPMENT), I:
- switched to development on GUI Update Settings
- used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
- switched back to stable on GUI update settings
- used console option 13 again, and it found the "right" stable stuff, said "y" to upgrade
I am not sure if that sequence should really be needed, but for me it got the system recognize the "new stable" and upgrade to it.
Ive got one box that seems to want to stick to 2.3.2 as well.. Fought with it several times yesterday. Its nano and really slow.. Im trying this now. Ill update if this works for this one. All my others upgraded without a hitch.
As far as I can tell the system has been updated but the dashboard is still reporting 2.3.2 as my picture shows.
Do
cat /etc/version*and check what's there.
Thanks for the help. Here is the output from the command:
"2.3.2-RELEASE
Tue Sep 27 12:13:07 CDT 2016
e936f18c1ad0b847cc1133d376f9950f4770c360
0"So my upgrade didn't complete, if this info is correct.
-
Name xxx.xxx.xxx
System Netgate SG-4860
Serial: 1116160595
Version 2.3.3-RELEASE (amd64)
built on Thu Feb 16 06:59:53 CST 2017
FreeBSD 10.3-RELEASE-p16
Platform pfSense
CPU Type Intel(R) Atom(TM) CPU C2558 @ 2.40GHz
4 CPUs: 1 package(s) x 4 core(s)
Hardware crypto AES-CBC,AES-XTS,AES-GCM,AES-ICM
Uptime 19 Hours 18 Minutes 08 Seconds
Current date/time
Tue Feb 21 18:40:56 GMT 201719 Hrs uptime all good here :)
-
Same here : all ok;
(but : I'm using the dyndns RFC 2136 - and something went wrong, what can be seen when you use the GUI 'DynDNS' widget. I found out what is was : the usage of the separators "|" and ":" are mixed up (/etc/inc/services.inc I guess) when assembling the IP cache files - so the 'explode' will fail later on. I'll post some more details later on.)
-
Successfully upgraded four stand-alone pfSense firewalls, three virtual, one physical, without incident.
Then, I successfully upgraded five pairs of redundant pfSense firewalls, handling production workloads, in the middle of the day, without incident.
The last three upgrades I have performed on our redundant Cisco firewalls were not as smooth. Great work guys, truly great work, thank you.
…v
-
No go 2.3.2_1 -> 2.3.3 from GUI, the current version remains, going to try console tomorrow.
