Upgrade from 2.3.1-RELEASE-p5 (i386) to 2.3.2 Fails



  • Greetings,

    Thank you in advance for your support!

    We had numerous failed 2.3.1-RELEASE-p5 (i386) to 2.3.2 upgrade attempts using the GUI (Failed), pfSense-upgrade -d (failed, same output as below), and from the console (see output below).

    System Details:
    Version 2.3.1-RELEASE-p5 (i386)
    built on Thu Jun 16 12:53:31 CDT 2016
    FreeBSD 10.3-RELEASE-p3
    Version 2.3.2 is available.
    Platform nanobsd (4g)
    NanoBSD Boot Slice pfsense0 pfsense1 / ada0s1(ro)
    CPU Type Intel(R) Atom(TM) CPU D525 @ 1.80GHz
    4 CPUs: 1 package(s) x 2 core(s) x 2 HTT threads

    Before upgrade:
    pkg update -f
    Updating pfSense-core repository catalogue…
    Fetching meta.txz: 100%    944 B  0.9kB/s    00:01   
    Fetching packagesite.txz: 100%    2 KiB  2.2kB/s    00:01   
    Processing entries: 100%
    pfSense-core repository update completed. 13 packages processed.
    Updating pfSense repository catalogue...
    Fetching meta.txz: 100%    944 B  0.9kB/s    00:01   
    Fetching packagesite.txz: 100%  110 KiB 112.6kB/s    00:01   
    Processing entries: 100%
    pfSense repository update completed. 406 packages processed.
    [2.3.1-RELEASE][root@fw-nog]/root: 13

    *** Welcome to pfSense 2.3.1-RELEASE-p5 (i386 nanobsd) on fw-nog ***

    WAN_EM0 (wan)  -> em0        -> v4: 50.0.18.55/24
    LAN_EM1 (lan)  -> em1        -> v4: 192.168.30.254/24
    VLAN20_RE1 (opt1) -> re1_vlan20 -> v4: 192.168.20.254/24
    VLAN2_RE2 (opt2) -> re2        -> v4: 192.168.2.254/24
    VLAN21_RE1 (opt3) -> re1_vlan21 -> v4: 192.168.21.254/24
    VLAN22_RE1 (opt4) -> re1_vlan22 -> v4: 192.168.22.254/24

    1. Logout (SSH only)                  9) pfTop
    2. Assign Interfaces                10) Filter Logs
    3. Set interface(s) IP address      11) Restart webConfigurator
    4. Reset webConfigurator password    12) pfSense Developer Shell
    5. Reset to factory defaults        13) Update from console
    6. Reboot system                    14) Disable Secure Shell (sshd)
    7. Halt system                      15) Restore recent configuration
    8. Ping host                        16) Restart PHP-FPM
    9. Shell

    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... ydone.
    Restoring slice label... done.
    Testing duplicated partition integrity... done.
    Mounting second partition to run upgrade... done.
    Unlocking package pfSense-kernel-pfSense_wrap_vga... 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.
    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_vga' 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... done.
    Upgrade is complete.  Rebooting in 10 seconds.

    Broadcast Message from root@fw-nog                   
            (/dev/pts/0) at 9:30 PDT...

    Upgrade is complete.  Rebooting in 10 seconds.

    Locking package pfSense-kernel-pfSense_wrap_vga... done.
    *** Welcome to pfSense 2.3.1-RELEASE-p5 (i386 nanobsd) on fw-nog ***

    It boots as
    *** Welcome to pfSense 2.3.1-RELEASE-p5 (i386 nanobsd) on fw-nog ***

    Respectfully,


  • Netgate

    Probably this:

    https://redmine.pfsense.org/issues/6557

    Set your DNS forwarder to listen on localhost - at least temporarily - and run the upgrade again.



  • Hi Derelict,

    Thank you for the link and tip, unfortunately even with localhost in resolv.conf the upgraded had the same errors:
    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_vga' 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

    Respectfully


  • Rebel Alliance Developer Netgate

    But is your forwarder or resolver actually listening on Localhost? Check the selected interfaces on whichever one you're running.



  • That did the trick! Thank you for your support.