2.3.4-RELEASE-p1 => 2.4.0 "system update failed" please help!



  • Using Web UI got "system update failed" error
    "pkg-static: cached package php56-5.6.31: size mismatch, cannot continue
    Failed
    Failed"

    See full stack here https://pastebin.com/LXZ6jEJJ

    Any help appreciated!



  • Did you try it 2x?

    Got the same error, reboot and tried again and it was fine.



  • @kejianshi:

    Did you try it 2x?

    Got the same error, reboot and tried again and it was fine.

    2x did not help, but reboot did !
    Upgrading as we speak ….

    And after a couple of reboots, my version say 2.4.1 and all packages seem updated

    So far see no regressions.



  • My system will not show an update availble. I'm currently on 2.3.4 RELEASE p1 i386. I believe I saw in a form elsewhere that you can't upgrade from x86/i386 to 2.4 or 2.4.1 as it is no longer being supported. Is this true? Do I have to do a complete fresh install on the 2.4.1? Will by backup config from 2.3.4p1 i386 work?

    Thanks,

    Matt



  • @darklogic:

    I believe I saw in a form elsewhere that you can't upgrade from x86/i386 to 2.4 or 2.4.1 as it is no longer being supported. Is this true?

    https://forum.pfsense.org/index.php?topic=121255.0



  • My system will not show an update availble.

    Ok, thtis can be based on the not availability of the 32Bit OS based pfSense code. Since version 2.4.0/2.4.1
    the x86 pfSense is only 64Bit based.

    I'm currently on 2.3.4 RELEASE p1 i386.

    • If this is installed on a 32Bit hardware system, you need to get new hardware to install pfSense 2.4.0/2.4.1 on it
      As mentioned above, since version 2.4.x pfSense is only 64Bit based and without any NanoBSD support!
    • If this is installed on a 64Bit hardware capable to run 32Bit software too, you might be only changing the OS
      Do a fresh and full install and play back the configuration backup.xml

    I believe I saw in a form elsewhere that you can't upgrade from x86/i386 to 2.4 or 2.4.1 as it is no longer being supported.

    Hardware based it is likes you say, software only based it might be able to realize without any issues.
    Many users are installing also on 64Bit their beloved 32Bit OS and it might be running some faster then
    they though, but now you will be "pressed" or better forced to install on that 64Bit hardware also 64Bit software
    (pfSense), because of the lag of 31Bit support since the version 2.4.x

    Is this true?

    If you own 32Bit hardware you can´t upgrade to 2.4.x, but if this is 64Bit hardware you can do it with ease!

    Do I have to do a complete fresh install on the 2.4.1? Will by backup config from 2.3.4p1 i386 work?

    a.) Yes you should do a fresh and full install of pfSense 64Bit.
    b.) Yes it will be working without any issues like before also too.

    • 32Bit OS support is gone, by getting instead of this ARM support and ARM 64Bit support its on his way too!!!
    • NanoBSD is gone completely because the version 3.0 will be totally written new from the "scratch"

    If the version 3.0 is written and the ARM64 change is done well too, it might be happen, or in other words it could
    be that the NanoBSD is coming at one day, but not yet and not before both systems named above are fully done.



  • With that all being said will my config backup work on a fresh install to a 64bit system when the config was based from x86 i386?



  • Yep - minus the rdd data.  At least it always has for me.



  • With that all being said will my config backup work on a fresh install to a 64bit system when the config was based from x86 i386?

    Be sure it will be running well and working and if not, I mean if something goes wrong for you, you may be also
    able to reinstall the older verison and play it back there, if needed.



  • Ok, I will make sure I have an older copy just in case I have to revert back. My config is rather extensive. Thanks for the feedback guys.



  • I'm getting no where with updating. I believe I have 64bit hardware– but I still get "System Update Failed".

    I'm on version:
    2.3.4-RELEASE-p1 (amd64)
    built on Fri Jul 14 14:52:43 CDT 2017
    FreeBSD 10.3-RELEASE-p19

    My hardware is:
    Platform pfSense
    CPU Type Intel(R) Xeon(R) CPU X3470 @ 2.93GHz
    Current: 2933 MHz, Max: 2934 MHz
    8 CPUs: 1 package(s) x 4 core(s) x 2 SMT threads
    8GB RAM

    Any ideas? I'm using hardware I bought online, and from my research this CPU is 64bit



  • I'm getting no where with updating. I believe I have 64bit hardware– but I still get "System Update Failed".

    Was this over the webgui or over a memstick image on an USB pen drive? And when USB pen drive what image
    you were using for this update?

    CPU Type  Intel(R) Xeon(R) CPU X3470 @ 2.93GHz

    It is a real 64Bit CPU!

    Any ideas? I'm using hardware I bought online, and from my research this CPU is 64bit

    If you will be able to get the amd64 memstick serial image to download, I woudl do so and then you might be
    preparing an USB pen drive for the upgrade. Save your config backup image and then do a fresh and full install.
    Play back the config backup and see what is going on.



  • Just reinstall…  You can spend forever on this.



  • @kejianshi:

    Just reinstall…  You can spend forever on this.

    Is there a quick way to re-install via the web gui? I have my box mounted in a peculiar spot and getting a monitor, keyboard and mouse would be a huge pain.

    Thanks



  • I thought you already had a huge pain?  Sorry.  I have no easy answer.



  • I got the dreaded “System update failed!” message back when I tried upgrading one of my pfSense 2.3.4 boxes to 2.4.0, and I got it again today when I tried upgrading another 2.3.4 box to 2.4.2. I'm really surprised it still has this problem in 2.4.2, and even more surprised that none of the pfSense upgrade documentation mentions this problem.

    Here's what I had to do both times: SSH into your pfSense machine and run the following three commands as root:

    pkg-static install -f pkg
    mv /usr/local/etc/pkg.conf /usr/local/etc/pkg.conf.old
    pfSense-upgrade -d

    Detail:

    When you run “pkg-static install -f pkg” you’ll see the following:

    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 REINSTALLED:
    pkg-1.10.1_1 [pfSense]

    Number of packages to be reinstalled: 1

    After you select “y” and it upgrades the “pkg” package it will tell you the following:

    You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.

    Instead, I renamed it to pkg.conf.old, just in case.

    After you run “pfSense-upgrade -d” to complete the upgrade it will automatically reboot. The reboot will take longer than normal because it will continue upgrading packages after it boots. Eventually, though, the Web interface will load again and you'll see the new Web GUI design.

    Hope that helps.
    –Dan



  • Thanks, this helped me get upgraded.



  • @fluidmindorg Thanks Mate, that worked. It was a very slow process though.



  • I was very hopeful this would fix me, but it did not. Same issue trying to go from 2.3.4 to current. Doing this actually made the issue slightly worse in that before I could at least check for updates and now I cannot. Sounds like I might be stuck with a config backup/fresh install/config restore situation now unless someone has a better suggestion.