2.3.2 upgrade to 2.3.2_1 fails



  • I clean installed a pfSense i368 4gb nanoBSD. And I tried to upgrade it to 2.3.2_1.

    Any ideas why?

    $ sudo pfSense-upgrade -d
    >>> 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.
    **** WARNING ****
    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.
    
    Proceed with upgrade? (y/N) y
    >>> Cleaning secondary partition... 
    1+0 records in
    1+0 records out
    1048576 bytes transferred in 0.065087 secs (16110415 bytes/sec)
    >>> Duplicating current slice... 
    30034+1 records in
    30034+1 records out
    1968349696 bytes transferred in 384.859288 secs (5114466 bytes/sec)
    >>> Restoring slice label... 
    >>> Testing duplicated partition integrity... 
    ** /dev/ufs/pfsense1
    ** Last Mounted on /
    ** Phase 1 - Check Blocks and Sizes
    ** Phase 2 - Check Pathnames
    ** Phase 3 - Check Connectivity
    ** Phase 4 - Check Reference Counts
    ** Phase 5 - Check Cyl groups
    16095 files, 879904 used, 2900124 free (2524 frags, 362200 blocks, 0.1% fragmentation)
    
    ***** FILE SYSTEM IS CLEAN *****
    >>> Mounting second partition to run upgrade... 
    >>> Copying resolv.conf to upgrade partition... 
    cp: /tmp/nanobsd_upgrade/etc/resolv.conf and /var/etc/resolv.conf are identical (not copied).
    >>> Unlocking package pfSense-kernel-pfSense_wrap... 
    Unlocking pfSense-kernel-pfSense_wrap-2.3.2
    >>> 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.
    pkg: Repository pfSense-core cannot be opened. 'pkg update' required
    pkg: Repository pfSense cannot be opened. 'pkg update' required
    pkg: No packages available to upgrade matching 'pfSense-kernel-pfSense_wrap' have been found in the repositories
    pkg: Repository pfSense-core cannot be opened. 'pkg update' required
    pkg: Repository pfSense cannot be opened. 'pkg update' required
    pkg: Repository pfSense-core cannot be opened. 'pkg update' required
    pkg: Repository pfSense cannot be opened. 'pkg update' required
    >>> Setting secondary partition as active... 
    active set on ada0s2
    Upgrade is complete.  Rebooting in 10 seconds.
    
    Broadcast Message from l33tname@pandora.l33t.network                           
            (/dev/pts/0) at 13:50 CET...                                           
    
    Upgrade is complete.  Rebooting in 10 seconds.                                 
    
    >>> Locking package pfSense-kernel-pfSense_wrap... 
    Locking pfSense-kernel-pfSense_wrap-2.3.2
    

  • Rebel Alliance Developer Netgate

    Try it again from the GUI or from root/admin directly and not called via sudo. I'm not sure we've ever tested that. In theory it should work, but you're introducing unnecessary variables there.



  • I have also some kind of problem with the upgrade. Before i have done an upgrade from 2.0.1 to 2.3.2, worked fine.

    Now the update from 2.3.2 to 2.3.2_1 looks like below, but after the reboot i'm still on 2.3.2.

    I'm on pfSense i386 4gb nanoBSD on alix board.

    
    Enter an option: 13
    
    >>> 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.
    **** WARNING ****
    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.
    
    Proceed with upgrade? (y/N) y
    >>> 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.
    >>> Unlocking package pfSense-kernel-pfSense_wrap... done.
    >>> 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 (5 candidates): ..... done
    Processing candidates (5 candidates): ..... done
    The following 4 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
    	pfSense-rc: 2.3.2 -> 2.3.2_1 [pfSense-core]
    	pfSense-kernel-pfSense_wrap: 2.3.2 -> 2.3.2_1 [pfSense-core]
    	pfSense-default-config-serial: 2.3.2 -> 2.3.2_1 [pfSense-core]
    	pfSense-base-nanobsd: 2.3.2 -> 2.3.2_1 [pfSense-core]
    
    Number of packages to be upgraded: 4
    
    38 MiB to be downloaded.
    Fetching pfSense-rc-2.3.2_1.txz: . done
    Fetching pfSense-kernel-pfSense_wrap-2.3.2_1.txz: .......... done
    Fetching pfSense-default-config-serial-2.3.2_1.txz: . done
    Fetching pfSense-base-nanobsd-2.3.2_1.txz: .......... done
    Checking integrity... done (0 conflicting)
    >>> Upgrading pfSense kernel... 
    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 integrity... done (0 conflicting)
    The following 1 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
    	pfSense-kernel-pfSense_wrap: 2.3.2 -> 2.3.2_1 [pfSense-core]
    
    Number of packages to be upgraded: 1
    [1/1] Upgrading pfSense-kernel-pfSense_wrap from 2.3.2 to 2.3.2_1...
    [1/1] Extracting pfSense-kernel-pfSense_wrap-2.3.2_1: .......... done
    ===> Keeping a copy of current kernel in /boot/kernel.old
    >>> Upgrading necessary 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 (4 candidates): .... done
    Processing candidates (4 candidates): .... done
    Checking integrity... done (0 conflicting)
    The following 3 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
    	pfSense-rc: 2.3.2 -> 2.3.2_1 [pfSense-core]
    	pfSense-default-config-serial: 2.3.2 -> 2.3.2_1 [pfSense-core]
    	pfSense-base-nanobsd: 2.3.2 -> 2.3.2_1 [pfSense-core]
    
    Number of packages to be upgraded: 3
    [1/3] Upgrading pfSense-rc from 2.3.2 to 2.3.2_1...
    [1/3] Extracting pfSense-rc-2.3.2_1: .... done
    [2/3] Upgrading pfSense-default-config-serial from 2.3.2 to 2.3.2_1...
    [2/3] Extracting pfSense-default-config-serial-2.3.2_1: ..... done
    [3/3] Upgrading pfSense-base-nanobsd from 2.3.2 to 2.3.2_1...
    [3/3] Extracting pfSense-base-nanobsd-2.3.2_1: ..... done
    ===> Keeping a copy of current version mtree
    ===> Removing schg flag from base files
    ===> Extracting new base tarball
    ===> Removing static obsoleted files
    >>> Setting secondary partition as active... done.
    Upgrade is complete.  Rebooting in 10 seconds.
    
    Broadcast Message from root@router1
            (/dev/pts/0) at 12:28 UTC...                                           
    
    Upgrade is complete.  Rebooting in 10 seconds.                                 
    
    >>> Locking package pfSense-kernel-pfSense_wrap... done.
    
    

  • Banned

    @pki:

    I have also some kind of problem with the upgrade. Before i have done an upgrade from 2.0.1 to 2.3.2, worked fine.

    Eeeeh? What exactly did not work, considering the log shows perfectly completed upgrade?



  • The dashboard still show:
    2.3.2-RELEASE (i386)
    built on Tue Jul 19 13:09:39 CDT 2016
    FreeBSD 10.3-RELEASE-p5

    Version 2.3.2_1 is available.



  • same for me

    tried manual/ gui/ cli

    Version 2.3.2-RELEASE (i386)
    built on Tue Jul 19 13:09:39 CDT 2016
    FreeBSD 10.3-RELEASE-p3

    Version 2.3.2_1 is available.
    Platform nanobsd (4g)



  • I just tested this again as root still the same problem

    >>> Updating repositories metadata... 
    Updating pfSense-core repository catalogue...
    pfSense-core repository is up-to-date.
    Updating pfSense repository catalogue...
    Fetching meta.txz: . done
    Fetching packagesite.txz: .......... done
    Processing entries: .......... done
    pfSense repository update completed. 405 packages processed.
    **** WARNING ****
    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.
    
    Proceed with upgrade? (y/N) >>> 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.
    >>> Unlocking package pfSense-kernel-pfSense_wrap... 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.
    >>> Setting secondary partition as active... done.
    Upgrade is complete.  Rebooting in 10 seconds.
    >>> Locking package pfSense-kernel-pfSense_wrap... done.
    >>> Removing unnecessary packages... done.
    >>> Cleanup pkg cache... done.
    

    After the reboot it's not upgraded and shows me that I could upgrade.



  • @l33tname:

    I just tested this again as root still the same problem

    >>> Updating repositories metadata... 
    Updating pfSense-core repository catalogue...
    pfSense-core repository is up-to-date.
    Updating pfSense repository catalogue...
    Fetching meta.txz: . done
    Fetching packagesite.txz: .......... done
    Processing entries: .......... done
    pfSense repository update completed. 405 packages processed.
    **** WARNING ****
    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.
    
    Proceed with upgrade? (y/N) >>> 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.
    >>> Unlocking package pfSense-kernel-pfSense_wrap... 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.
    >>> Setting secondary partition as active... done.
    Upgrade is complete.  Rebooting in 10 seconds.
    >>> Locking package pfSense-kernel-pfSense_wrap... done.
    >>> Removing unnecessary packages... done.
    >>> Cleanup pkg cache... done.
    

    After the reboot it's not upgraded and shows me that I could upgrade.

    Did you try switching partitions/slices?



  • @Nullity:

    Did you try switching partitions/slices?

    Not manually but it switches partitions after every upgrade.

    At the moment I just upgraded it with pkg update && pkg upgrade not sure what side effects this has but it worked.



  • Same here.
    nanobsd (2g)
    Upgrade fail with "pkg cannot open …"
    Booting the other slice don't change anything.
    Tryiln from GUI or console is the same.

    pkg update && pkg upgrade

    From console works. Dashboard now display :

    2.3.2-RELEASE-p1 (i386)
    built on Tue Sep 27 12:13:32 CDT 2016
    FreeBSD 10.3-RELEASE-p5



  • Same here, worked with some comments, do I need to do anything or is this fine now?

    It took about 2,5 hours on the alix board…. :-/

    
    pkg upgrade
    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 (44 candidates):  84%
    
    pfSense-kernel-pfSense_wrap-2.3.2 is locked and may not be modified
    Checking for upgrades (44 candidates): 100%
    Processing candidates (44 candidates): 100%
    The following 43 package(s) will be affected (of 0 checked):
    
    Installed packages to be UPGRADED:
    	php56-zlib: 5.6.23 -> 5.6.26 [pfSense]
    	php56-xmlwriter: 5.6.23 -> 5.6.26 [pfSense]
    	php56-xmlreader: 5.6.23 -> 5.6.26 [pfSense]
    	php56-xml: 5.6.23 -> 5.6.26 [pfSense]
    	php56-tokenizer: 5.6.23 -> 5.6.26 [pfSense]
    	php56-sysvshm: 5.6.23 -> 5.6.26 [pfSense]
    	php56-sysvsem: 5.6.23 -> 5.6.26 [pfSense]
    	php56-sysvmsg: 5.6.23 -> 5.6.26 [pfSense]
    	php56-sqlite3: 5.6.23 -> 5.6.26 [pfSense]
    	php56-sockets: 5.6.23 -> 5.6.26 [pfSense]
    	php56-simplexml: 5.6.23 -> 5.6.26 [pfSense]
    	php56-shmop: 5.6.23 -> 5.6.26 [pfSense]
    	php56-session: 5.6.23 -> 5.6.26 [pfSense]
    	php56-readline: 5.6.23 -> 5.6.26 [pfSense]
    	php56-posix: 5.6.23 -> 5.6.26 [pfSense]
    	php56-pdo_sqlite: 5.6.23 -> 5.6.26 [pfSense]
    	php56-pdo: 5.6.23 -> 5.6.26 [pfSense]
    	php56-pcntl: 5.6.23 -> 5.6.26 [pfSense]
    	php56-openssl: 5.6.23 -> 5.6.26 [pfSense]
    	php56-opcache: 5.6.23_1 -> 5.6.26_1 [pfSense]
    	php56-mcrypt: 5.6.23 -> 5.6.26 [pfSense]
    	php56-mbstring: 5.6.23 -> 5.6.26 [pfSense]
    	php56-ldap: 5.6.23 -> 5.6.26 [pfSense]
    	php56-json: 5.6.23 -> 5.6.26 [pfSense]
    	php56-hash: 5.6.23 -> 5.6.26 [pfSense]
    	php56-gettext: 5.6.23 -> 5.6.26 [pfSense]
    	php56-filter: 5.6.23 -> 5.6.26 [pfSense]
    	php56-dom: 5.6.23 -> 5.6.26 [pfSense]
    	php56-curl: 5.6.23 -> 5.6.26 [pfSense]
    	php56-ctype: 5.6.23 -> 5.6.26 [pfSense]
    	php56-bz2: 5.6.23 -> 5.6.26 [pfSense]
    	php56-bcmath: 5.6.23 -> 5.6.26 [pfSense]
    	php56: 5.6.23 -> 5.6.26 [pfSense]
    	pfSense-rc: 2.3.2 -> 2.3.2_1 [pfSense-core]
    	pfSense-pkg-openvpn-client-export: 1.3.13 -> 1.3.15_1 [pfSense]
    	pfSense-default-config-serial: 2.3.2 -> 2.3.2_1 [pfSense-core]
    	pfSense-base-nanobsd: 2.3.2 -> 2.3.2_1 [pfSense-core]
    	pfSense: 2.3.2 -> 2.3.2_1 [pfSense]
    	perl5: 5.20.3_13 -> 5.20.3_15 [pfSense]
    	libxml2: 2.9.3 -> 2.9.4 [pfSense]
    	libidn: 1.31 -> 1.33_1 [pfSense]
    	curl: 7.49.1 -> 7.50.3 [pfSense]
    
    Installed packages to be REINSTALLED:
    	scponly-4.8.20110526_2 [pfSense] (options changed)
    
    Number of packages to be upgraded: 42
    Number of packages to be reinstalled: 1
    
    41 MiB to be downloaded.
    
    Proceed with this action? [y/N]: y
    Fetching scponly-4.8.20110526_2.txz: 100%   18 KiB  18.5kB/s    00:01    
    Fetching php56-zlib-5.6.26.txz: 100%   13 KiB  13.3kB/s    00:01    
    Fetching php56-xmlwriter-5.6.26.txz: 100%   11 KiB  10.8kB/s    00:01    
    Fetching php56-xmlreader-5.6.26.txz: 100%   12 KiB  11.8kB/s    00:01    
    Fetching php56-xml-5.6.26.txz: 100%   18 KiB  18.1kB/s    00:01    
    Fetching php56-tokenizer-5.6.26.txz: 100%    8 KiB   7.7kB/s    00:01    
    Fetching php56-sysvshm-5.6.26.txz: 100%    7 KiB   7.2kB/s    00:01    
    Fetching php56-sysvsem-5.6.26.txz: 100%    6 KiB   6.2kB/s    00:01    
    Fetching php56-sysvmsg-5.6.26.txz: 100%    8 KiB   8.0kB/s    00:01    
    Fetching php56-sqlite3-5.6.26.txz: 100%   16 KiB  16.2kB/s    00:01    
    Fetching php56-sockets-5.6.26.txz: 100%   32 KiB  32.4kB/s    00:01    
    Fetching php56-simplexml-5.6.26.txz: 100%   20 KiB  20.7kB/s    00:01    
    Fetching php56-shmop-5.6.26.txz: 100%    6 KiB   6.6kB/s    00:01    
    Fetching php56-session-5.6.26.txz: 100%   28 KiB  28.7kB/s    00:01    
    Fetching php56-readline-5.6.26.txz: 100%   12 KiB  12.4kB/s    00:01    
    Fetching php56-posix-5.6.26.txz: 100%   10 KiB  10.1kB/s    00:01    
    Fetching php56-pdo_sqlite-5.6.26.txz: 100%   11 KiB  11.6kB/s    00:01    
    Fetching php56-pdo-5.6.26.txz: 100%   41 KiB  41.6kB/s    00:01    
    Fetching php56-pcntl-5.6.26.txz: 100%   12 KiB  11.8kB/s    00:01    
    Fetching php56-openssl-5.6.26.txz: 100%   44 KiB  45.2kB/s    00:01    
    Fetching php56-opcache-5.6.26_1.txz: 100%   59 KiB  60.9kB/s    00:01    
    Fetching php56-mcrypt-5.6.26.txz: 100%   14 KiB  14.5kB/s    00:01    
    Fetching php56-mbstring-5.6.26.txz: 100%  701 KiB  32.6kB/s    00:22    
    Fetching php56-ldap-5.6.26.txz: 100%   19 KiB  19.2kB/s    00:01    
    Fetching php56-json-5.6.26.txz: 100%   16 KiB  16.6kB/s    00:01    
    Fetching php56-hash-5.6.26.txz: 100%  116 KiB  39.7kB/s    00:03    
    Fetching php56-gettext-5.6.26.txz: 100%    6 KiB   6.4kB/s    00:01    
    Fetching php56-filter-5.6.26.txz: 100%   19 KiB  19.2kB/s    00:01    
    Fetching php56-dom-5.6.26.txz: 100%   50 KiB  51.3kB/s    00:01    
    Fetching php56-curl-5.6.26.txz: 100%   25 KiB  26.0kB/s    00:01    
    Fetching php56-ctype-5.6.26.txz: 100%    6 KiB   6.1kB/s    00:01    
    Fetching php56-bz2-5.6.26.txz: 100%   10 KiB  10.4kB/s    00:01    
    Fetching php56-bcmath-5.6.26.txz: 100%   17 KiB  17.6kB/s    00:01    
    Fetching php56-5.6.26.txz: 100%    2 MiB  32.2kB/s    00:58    
    Fetching pfSense-rc-2.3.2_1.txz: 100%    6 KiB   6.2kB/s    00:01    
    Fetching pfSense-pkg-openvpn-client-export-1.3.15_1.txz: 100%   18 KiB  18.3kB/s    00:01    
    Fetching pfSense-default-config-serial-2.3.2_1.txz: 100%    4 KiB   3.7kB/s    00:01    
    Fetching pfSense-base-nanobsd-2.3.2_1.txz: 100%   24 MiB  31.8kB/s    12:58    
    Fetching pfSense-2.3.2_1.txz: 100%    3 KiB   3.4kB/s    00:01    
    Fetching perl5-5.20.3_15.txz: 100%   13 MiB  34.1kB/s    06:28    
    Fetching libxml2-2.9.4.txz: 100%  771 KiB  31.6kB/s    00:25    
    Fetching libidn-1.33_1.txz: 100%  182 KiB  37.4kB/s    00:05    
    Fetching curl-7.50.3.txz: 100%  900 KiB  32.9kB/s    00:28    
    Checking integrity... done (0 conflicting)
    [1/43] Upgrading perl5 from 5.20.3_13 to 5.20.3_15...
    [1/43] Extracting perl5-5.20.3_15: 100%
    makewhatis: not found
    makewhatis: not found
    [2/43] Upgrading libxml2 from 2.9.3 to 2.9.4...
    [2/43] Extracting libxml2-2.9.4: 100%
    [3/43] Upgrading php56 from 5.6.23 to 5.6.26...
    [3/43] Extracting php56-5.6.26: 100%
    [4/43] Upgrading curl from 7.49.1 to 7.50.3...
    [4/43] Extracting curl-7.50.3: 100%
    [5/43] Upgrading php56-session from 5.6.23 to 5.6.26...
    [5/43] Extracting php56-session-5.6.26: 100%
    [6/43] Upgrading php56-pdo from 5.6.23 to 5.6.26...
    [6/43] Extracting php56-pdo-5.6.26: 100%
    [7/43] Upgrading php56-dom from 5.6.23 to 5.6.26...
    [7/43] Extracting php56-dom-5.6.26: 100%
    [8/43] Upgrading libidn from 1.31 to 1.33_1...
    [8/43] Extracting libidn-1.33_1: 100%
    [9/43] Reinstalling scponly-4.8.20110526_2...
    [9/43] Extracting scponly-4.8.20110526_2: 100%
    
    To setup chroot cage, run the following commands:
      1) cd /usr/local/share/examples/scponly/ && /bin/sh setup_chroot.sh
      2) Set scponlyc_enable="YES" in /etc/rc.conf
      3) Run /usr/local/etc/rc.d/scponly start
    [10/43] Upgrading php56-zlib from 5.6.23 to 5.6.26...
    [10/43] Extracting php56-zlib-5.6.26: 100%
    [11/43] Upgrading php56-xmlwriter from 5.6.23 to 5.6.26...
    [11/43] Extracting php56-xmlwriter-5.6.26: 100%
    [12/43] Upgrading php56-xmlreader from 5.6.23 to 5.6.26...
    [12/43] Extracting php56-xmlreader-5.6.26: 100%
    [13/43] Upgrading php56-xml from 5.6.23 to 5.6.26...
    [13/43] Extracting php56-xml-5.6.26: 100%
    [14/43] Upgrading php56-tokenizer from 5.6.23 to 5.6.26...
    [14/43] Extracting php56-tokenizer-5.6.26: 100%
    [15/43] Upgrading php56-sysvshm from 5.6.23 to 5.6.26...
    [15/43] Extracting php56-sysvshm-5.6.26: 100%
    [16/43] Upgrading php56-sysvsem from 5.6.23 to 5.6.26...
    [16/43] Extracting php56-sysvsem-5.6.26: 100%
    [17/43] Upgrading php56-sysvmsg from 5.6.23 to 5.6.26...
    [17/43] Extracting php56-sysvmsg-5.6.26: 100%
    [18/43] Upgrading php56-sqlite3 from 5.6.23 to 5.6.26...
    [18/43] Extracting php56-sqlite3-5.6.26: 100%
    [19/43] Upgrading php56-sockets from 5.6.23 to 5.6.26...
    [19/43] Extracting php56-sockets-5.6.26: 100%
    [20/43] Upgrading php56-simplexml from 5.6.23 to 5.6.26...
    [20/43] Extracting php56-simplexml-5.6.26: 100%
    [21/43] Upgrading php56-shmop from 5.6.23 to 5.6.26...
    [21/43] Extracting php56-shmop-5.6.26: 100%
    [22/43] Upgrading php56-readline from 5.6.23 to 5.6.26...
    [22/43] Extracting php56-readline-5.6.26: 100%
    [23/43] Upgrading php56-posix from 5.6.23 to 5.6.26...
    [23/43] Extracting php56-posix-5.6.26: 100%
    [24/43] Upgrading php56-pdo_sqlite from 5.6.23 to 5.6.26...
    [24/43] Extracting php56-pdo_sqlite-5.6.26: 100%
    [25/43] Upgrading php56-pcntl from 5.6.23 to 5.6.26...
    [25/43] Extracting php56-pcntl-5.6.26: 100%
    [26/43] Upgrading php56-openssl from 5.6.23 to 5.6.26...
    [26/43] Extracting php56-openssl-5.6.26: 100%
    [27/43] Upgrading php56-opcache from 5.6.23_1 to 5.6.26_1...
    [27/43] Extracting php56-opcache-5.6.26_1: 100%
    [28/43] Upgrading php56-mcrypt from 5.6.23 to 5.6.26...
    [28/43] Extracting php56-mcrypt-5.6.26: 100%
    [29/43] Upgrading php56-mbstring from 5.6.23 to 5.6.26...
    [29/43] Extracting php56-mbstring-5.6.26: 100%
    [30/43] Upgrading php56-ldap from 5.6.23 to 5.6.26...
    [30/43] Extracting php56-ldap-5.6.26: 100%
    [31/43] Upgrading php56-json from 5.6.23 to 5.6.26...
    [31/43] Extracting php56-json-5.6.26: 100%
    [32/43] Upgrading php56-hash from 5.6.23 to 5.6.26...
    [32/43] Extracting php56-hash-5.6.26: 100%
    [33/43] Upgrading php56-gettext from 5.6.23 to 5.6.26...
    [33/43] Extracting php56-gettext-5.6.26: 100%
    [34/43] Upgrading php56-filter from 5.6.23 to 5.6.26...
    [34/43] Extracting php56-filter-5.6.26: 100%
    [35/43] Upgrading php56-curl from 5.6.23 to 5.6.26...
    [35/43] Extracting php56-curl-5.6.26: 100%
    [36/43] Upgrading php56-ctype from 5.6.23 to 5.6.26...
    [36/43] Extracting php56-ctype-5.6.26: 100%
    [37/43] Upgrading php56-bz2 from 5.6.23 to 5.6.26...
    [37/43] Extracting php56-bz2-5.6.26: 100%
    [38/43] Upgrading php56-bcmath from 5.6.23 to 5.6.26...
    [38/43] Extracting php56-bcmath-5.6.26: 100%
    [39/43] Upgrading pfSense-rc from 2.3.2 to 2.3.2_1...
    [39/43] Extracting pfSense-rc-2.3.2_1: 100%
    [40/43] Upgrading pfSense-pkg-openvpn-client-export from 1.3.13 to 1.3.15_1...
    [40/43] Extracting pfSense-pkg-openvpn-client-export-1.3.15_1: 100%
    Removing openvpn-client-export components...
    Loading package instructions...
    Saving updated package information...
    overwrite!
    Loading package configuration... done.
    Configuring package components...
    Loading package instructions...
    Custom commands...
    Writing configuration... done.
    [41/43] Upgrading pfSense-default-config-serial from 2.3.2 to 2.3.2_1...
    [41/43] Extracting pfSense-default-config-serial-2.3.2_1: 100%
    [42/43] Upgrading pfSense-base-nanobsd from 2.3.2 to 2.3.2_1...
    [42/43] Extracting pfSense-base-nanobsd-2.3.2_1: 100%
    ===> Keeping a copy of current version mtree
    ===> Removing schg flag from base files
    ===> Extracting new base tarball
    ===> Removing static obsoleted files
    [43/43] Upgrading pfSense from 2.3.2 to 2.3.2_1...
    [43/43] Extracting pfSense-2.3.2_1: 100%
    Message from perl5-5.20.3_15:
    The /usr/bin/perl symlink has been removed starting with Perl 5.20.
    For shebangs, you should either use:
    
    #!/usr/local/bin/perl
    
    or
    
    #!/usr/bin/env perl
    
    The first one will only work if you have a /usr/local/bin/perl,
    the second will work as long as perl is in PATH.
    
    

  • Banned

    If it takes hours, get a less shitty CF…



  • OK, but the remaining part, the messages during the upgrade, it is all ok?