Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    [Solved] 2.3.5 is shown as 2.3.4-RELEASE (i386)

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    6 Posts 2 Posters 1.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Y
      yarick123
      last edited by

      Hi pfSense Team, thank you for the superior product!

      I have upgraded one of the firm firewalls from version 2.3.4-RELEASE-p1 (i386) to 2.3.5 (nanobsd 2g) several hours ago.

      The upgrade was not very straight. I needed to reset the firewall several times.

      At the end, all the packages and the kernel were successfully upgraded. Uname -a says:

      
      [2.3.4-RELEASE][admin@xxx.yyy.zzz]/root: uname -a
      FreeBSD xxx.yyy.zzz 10.3-RELEASE-p22 FreeBSD 10.3-RELEASE-p22 #0 352658d6e(RELENG_2_3): Tue Oct 24 05:16:13 CDT 2017     root@ce23-i386-builder:/builder/pfsense-235/tmp/obj/builder/pfsense-235/tmp/FreeBSD-src/sys/pfSense_wrap  i386
      
      

      but on the dashboard the version is shown as

      
      2.3.4-RELEASE (i386) 
      built on Fri Jul 14 14:53:03 CDT 2017 
      FreeBSD 10.3-RELEASE-p22
      
      

      In cli it is also shown as 2.3.4:

      
      *** Welcome to pfSense 2.3.4-RELEASE (i386 nanobsd) on xxx ***
      
      

      In the shell prompt the version is also shown as 2.3.4:

      
      [2.3.4-RELEASE][admin@xxx.yyy.zzz]/root:
      
      

      But on the "Update" tab it is everything ok, see attached image.

      Trying to upgrade from the console, I get a message, that the system uses the most recent version:

      
      >>> 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.
      >>> Unlocking package pfSense-kernel-pfSense_wrap... done.
      >>> Locking package pfSense-kernel-pfSense_wrap... done.
      Your packages are up to date
      
      

      Is it a correct behaviour, or there are problems by me? (I have rebooted the system several times.)

      Thank you,
      Best regards
      yarick123

      ![2017-12-12 15_09_22-xxx.yyy.zzz - System_ Update_ System Update.png](/public/imported_attachments/1/2017-12-12 15_09_22-xxx.yyy.zzz - System_ Update_ System Update.png)
      ![2017-12-12 15_09_22-xxx.yyy.zzz - System_ Update_ System Update.png_thumb](/public/imported_attachments/1/2017-12-12 15_09_22-xxx.yyy.zzz - System_ Update_ System Update.png_thumb)

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        There must be some portion of the upgrade that did not complete successfully. If you go to the console or ssh, start a shell and run "pfSense-upgrade" again. Does that show anything?

        What about "pkg version -vL="?

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • Y
          yarick123
          last edited by

          Hi jimp, thank you for the answer!

          There must be some portion of the upgrade that did not complete successfully.

          It is a pity. It seems, that I must reinstall the system…

          
          [2.3.4-RELEASE][admin@xxx.yyy.zzz]/root: pkg version -vL=
          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.
          pkg-1.10.2                         >   succeeds remote (remote has 1.10.1_1)
          [2.3.4-RELEASE][admin@xxx.yyy.zzz]/root:
          
          
          
          [2.3.4-RELEASE][admin@xxx.yyy.zzz]/root: pfSense-upgrade
          >>> 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.
          >>> Unlocking package pfSense-kernel-pfSense_wrap... done.
          >>> Locking package pfSense-kernel-pfSense_wrap... done.
          Your packages are up to date
          [2.3.4-RELEASE][admin@xxx.yyy.zzz]/root:
          
          
          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            Hmm, those appear to be OK, but something must have failed to write out properly.

            You could try one of a few things:

            1. For a reinstall of all packages (pkg-static upgrade -f)
            2. Reinstall pfSense
            3. Wait until 2.3.5-p1 drops later this week and attempt to update again then and see if it corrects itself.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • Y
              yarick123
              last edited by

              Hi jimp, thank you for the information.

              of course at first I will wait until 2.3.5-p1 !

              If it does not help, I will reinstall all the packages. And if it does not help either, then I will reinstall pfSense!

              Thank you
              best regards
              yarick123

              1 Reply Last reply Reply Quote 0
              • Y
                yarick123
                last edited by

                Hi jimp,

                thank you, the simplest solution #3 (

                3. Wait until 2.3.5-p1 drops later this week and attempt to update again then and see if it corrects itself.

                ) has succeeded!

                Now the correct version is shown everywhere! :)

                I noticed one strange thing during the upgrades (2.3.4_1 -> 2.3.5 and 2.3.5 -> 2.3.5_1). After the first upgrade, everything were upgraded except of the kernel. Rebooting did not help. The kernel was upgraded only after executing the upgrade process the second time. The disk slice was duplicated, and the possibility to go back to the previous version was lost. :(

                Best regards
                yarick123

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.