2.3.3 is live!

juruteknik

repo is down now?

i've try it about 10 times

**** WARNING ****
Reboot will be required!!
Proceed with upgrade? (y/N) y

Downloading upgrade packages…
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.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
pfSense-kernel-pfSense: 2.3.2_1 -> 2.3.3 [pfSense-core]

Number of packages to be upgraded: 1

15 MiB to be downloaded.
Fetching pfSense-kernel-pfSense-2.3.3.txz: . done
pkg: https://pkg.pfsense.org/pfSense_v2_3_3_amd64-core/All/pfSense-kernel-pfSense-2.3.3.txz: Operation timed out

Locking package pfSense-kernel-pfSense…
Locking pfSense-kernel-pfSense-2.3.2_1

Chucko

No issues here with an Atom D525 based system.

sparklyballs

Updated and cloud flare dynamic dns is no longer working

0.0.0.0 showing in widget

NOYB

Upgrade took about 40 minutes to extract everything and bootup.
Python and perl each took a really long time.

2.3.3-RELEASE (i386)
built on Thu Feb 16 06:59:50 CST 2017
FreeBSD 10.3-RELEASE-p16

Intel(R) Pentium(R) 4 CPU 2.66GHz
2015 MiB

Couple questions re: console messages during upgrade.

Manually remove if no longer needed: /usr/local/etc/ssl/cert.pem
Is this file still needed by pfSense? Don't think I have any need for it if pfSense doesn't.

What's are these makewhatis not found messages about?
[4/92] Extracting perl5…
makewhatis: not found
makewhatis: not found
[5/92] upgrading pcre…

openvpn-2.3.11: missing file /usr/local/man/man8/openvpn.8.gz
and a whole bunch of others for one of the lib* some things.
Would be nice if those could be suppressed if they are expected and not a problem. Believe they are just manual files that are being exclude in pfSense builds.

Jailer

Just successfully upgraded. I like the new traffic graph.

sgw

@chpalmer:

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?

phil.davis

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.

sgw

@phil.davis:

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!

doktornotor

@phil.davis:

I am not sure if that sequence should really be needed

Yeah I'm pretty sure the pkg thing urgently needs a brain transplant.

johnpoz

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 ;)

graphrealshort.png_thumb

normallooking.png_thumb

mudmanc4

Spectacular job once again pfsense team!

securityconscious

Everything appears to have gone ok.

kpa

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.

BIGGRIMTIM

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.

Speed831

@BIGGRIMTIM:

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)

chpalmer

@BIGGRIMTIM:

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.

slimypizza

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.

BIGGRIMTIM

@chpalmer:

@BIGGRIMTIM:

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.

doktornotor

@BIGGRIMTIM:

@chpalmer:

@BIGGRIMTIM:

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.

chpalmer

@BIGGRIMTIM:

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 2016

Tried "Pkg Upgrade" with this end response-

pkg: Cannot get an advisory lock on a database, it is locked by another process