2.3.3 is live!



  • Who's going to be the first guinea pig?  ;D

    I'd install but the fam is using the connection right now…....



  • Just did the upgrade and everything seems to be working, but the dashboard is still reporting:

    2.3.2-RELEASE (amd64)
    built on Tue Sep 27 12:13:07 CDT 2016
    FreeBSD 10.3-RELEASE-p16

    Not sure if this is correct as I am pretty new to pfsense.



  • Did you reboot?



  • If you were on RC before you might want to wait.

    I got it to work but it took some extra steps.



  • Any issues going from 2.3.2_p1 to 2.3.3?

    Like to pull the trigger, but would like to see release notes and any caveats first.



  • @damienmci:

    Any issues going from 2.3.2_p1 to 2.3.3?

    Like to pull the trigger, but would like to see release notes and any caveats first.

    https://doc.pfsense.org/index.php/2.3.3_New_Features_and_Changes



  • @damienmci:

    Any issues going from 2.3.2_p1 to 2.3.3?

    Like to pull the trigger, but would like to see release notes and any caveats first.

    All my 2.3.2 boxes upgraded with no issues whatsoever..  Since I had a couple others running on 2.3.3RC before this Im pretty optimistic that everything is good.



  • Done the upgrade to 2.3.3-RELEASE. No issues. Many thanks to the pfsense team for a wonderful product.



  • @damienmci:

    Done the upgrade to 2.3.3-RELEASE. No issues. Many thanks to the pfsense team for a wonderful product.

    Upgraded my main and backup 2.3.2p1 to 2.3.3 without issues.
    I did see some warnings during the upgrade. Mostly about a couple of config files not being used anymore, but would like to see the full log
    to make sure all my config went through. I am sure that log file is somewhere, but I took a video of the upgrade, so I'll go over it later.

    I do like the new upgrade process. Kudos to the pfSense Team + Testers!



  • Another hand up for a smooth upgrade if anyone is still on the fence about pulling the trigger.

    ;)



  • @Jailer:

    Did you reboot?

    I did reboot twice just to make sure.  When I check for updates it reports that I am up to date.



  • SWEET!  :-*



  • 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



  • No issues here with an Atom D525 based system.



  • Updated and cloud flare dynamic dns is no longer working

    0.0.0.0 showing in widget



  • 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.



  • Just successfully upgraded. I like the new traffic graph.



  • @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?



  • 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:

    1. switched to development on GUI Update Settings
    2. used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
    3. switched back to stable on GUI update settings
    4. 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.



  • @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:

    1. switched to development on GUI Update Settings
    2. used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
    3. switched back to stable on GUI update settings
    4. 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!


  • Banned

    @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.


  • LAYER 8 Global Moderator

    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.



  • @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)



  • @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:

    1. switched to development on GUI Update Settings
    2. used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
    3. switched back to stable on GUI update settings
    4. 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.



  • @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:

    1. switched to development on GUI Update Settings
    2. used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
    3. switched back to stable on GUI update settings
    4. 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.


  • Banned

    @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:

    1. switched to development on GUI Update Settings
    2. used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
    3. switched back to stable on GUI update settings
    4. 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.



  • @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



  • @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:

    1. switched to development on GUI Update Settings
    2. used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
    3. switched back to stable on GUI update settings
    4. 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.


  • Galactic Empire

    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 2017

    19 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.



  • @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:

    1. switched to development on GUI Update Settings
    2. used console option 13 to make it look for the development package database, and when it asked to upgrade I said N
    3. switched back to stable on GUI update settings
    4. 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.

    Did the same to get the WebGUI to offer 2.3.3-RELEASE (i386), I updated with the WebGUI, it rebooted, updated and then I got a double fault crash after starting the package.

    2017-02-21 16:20:11	System4.Info	172.x.x.254	Feb 21 16:20:13 kernel: Starting syslog...done.
    2017-02-21 16:20:11	System4.Info	172.x.x.254	Feb 21 16:20:13 kernel: Starting CRON... done.
    2017-02-21 16:20:11	Cron.Info	172.x.x.254	Feb 21 16:20:13 /usr/sbin/cron[57535]: (CRON) DEATH (cron already running, pid: 25377)
    2017-02-21 16:20:11	Daemon.Error	172.x.x.254	Feb 21 16:20:13 php-fpm[483]: /rc.start_packages: Restarting/Starting all packages.
    2017-02-21 16:20:11	System4.Info	172.x.x.254	Feb 21 16:20:13 kernel: Starting package Backup...done.
    2017-02-21 16:20:11	System4.Info	172.x.x.254	Feb 21 16:20:13 kernel: Starting package Cron...done.
    2017-02-21 16:20:11	System4.Info	172.x.x.254	Feb 21 16:20:13 kernel: Starting package System Patches...done.
    2017-02-21 16:20:11	Daemon.Notice	172.x.x.254	Feb 21 16:20:13 php-fpm[483]: [pfBlockerNG] Starting cron process.
    2017-02-21 16:20:15	User.Notice	172.x.x.254	Feb 21 16:20:17 check_reload_status: Syncing firewall
    2017-02-21 16:20:15	Daemon.Error	172.x.x.254	Feb 21 16:20:17 php-fpm[483]: /rc.start_packages: Beginning https://portal.pfsense.org configuration backup.
    2017-02-21 16:20:28	Daemon.Error	172.x.x.254	Feb 21 16:20:30 php-fpm[483]: /rc.start_packages: End of portal.pfsense.org configuration backup (success).
    
    **** Crash & Reboot ****
    
    2017-02-21 16:22:46	System4.Info	172.x.x.254	Feb 21 16:22:48 kernel: Configuring LAN interface...done.
    2017-02-21 16:22:46	System4.Info	172.x.x.254	Feb 21 16:22:48 kernel: Configuring TEST interface...done.
    ```After rebooting system seems fine.
    
    I had a similar double fault crash last week after switching from Development to Stable in order to get 2.3.3-RC, but I didn't update before the system crashed while saving an alias and applying change.


  • Tried Phil's option and still not working.  Last night I was prompted to update via the GUI so I did and it said it completed successfully.  My dashboard is still reporting 2.3.2, however when I go to the update page it reports 2.3.3 as my pics from my previous post shows.  Should I try to update to the 2.3.4 development build?  If I do can I go back to the stable channel?



  • Name xxx.xxx.xxx
    System PC Engines APU2
    Serial: –------------------------
    Version 2.3.3-RELEASE (amd64)
    built on Thu Feb 16 06:59:53 CST 2017
    FreeBSD 10.3-RELEASE-p16

    Obtaining update status
    Platform pfSense
    CPU Type AMD GX-412TC SOC
    4 CPUs: 1 package(s) x 4 core(s)
    Uptime 02 Hours 09 Minutes 27 Seconds
    Current date/time
    Wed Feb 22 1:20:42 CET 2017

    Humble home user here. All good so far.


Log in to reply