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

    System is on a later version than the official release / Latest 0.18_1

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    49 Posts 27 Posters 16.1k 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.
    • jimpJ
      jimp Rebel Alliance Developer Netgate
      last edited by

      N.B.: I merged several identical threads together, so if it appears that people didn't see/read earlier responses, it's likely because they were not originally part of this thread, so be kind in replies.

      If you are seeing this and still experience the issue, please re-read this post starting from the first page.

      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
      • C
        cosmoxl
        last edited by

        @jimp:

        N.B.: I merged several identical threads together, so if it appears that people didn't see/read earlier responses, it's likely because they were not originally part of this thread, so be kind in replies.

        If you are seeing this and still experience the issue, please re-read this post starting from the first page.

        all fixed now, thanks for merging the threads.

        1 Reply Last reply Reply Quote 0
        • RonpfSR
          RonpfS
          last edited by

          seeing 0.20 now

          020.JPG
          020.JPG_thumb

          2.4.5-RELEASE-p1 (amd64)
          Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
          Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

          1 Reply Last reply Reply Quote 0
          • S
            SkyNET
            last edited by

            I just applied patch 0.20 to my systems.

            System rebooted afterwards and looking healthy again.
            To be clear, the update is valid right? Not a cosmetic bug.
            I thought the update was part of the new patch-system.
            Thanks for the great work!

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

              There was an update for pfSense-upgrade, not the whole system. That update is good/legitimate.

              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
              • C
                Cybdex
                last edited by

                Yeah.. since i pressed the update key in the notion of "nothing bad will happen", i was NOT expecting a full reboot…....

                But well.. A couple of unhappy faces can be survived on a late friday i guess  ::)

                C

                1 Reply Last reply Reply Quote 0
                • RonpfSR
                  RonpfS
                  last edited by

                  @Renato:

                  I've pushed a fix, it's on pfSense-upgrade 0.19.

                  pfSense-upgrade was considering its new version as a new firmware version. The issue is harmless and if you finish the upgrade nothing bad will happen.

                  Fix is on version 0.19. As soon as it's available it's safe to manually run 'pkg upgrade pfSense-upgrade' on console to go to latest verssion.

                  This issue is being tracked at https://redmine.pfsense.org/issues/7343

                  Sorry for the inconvenience

                  So the only way to fix this "issue" is to run pkg upgrade pfSense-upgrade from the console?
                  And it won't reboot the box ?

                  2.4.5-RELEASE-p1 (amd64)
                  Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                  Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                  1 Reply Last reply Reply Quote 0
                  • C
                    Cybdex
                    last edited by

                    Dunno about the console command, but running the upgrade on the web-gui updated AND rebooted… But showing "you are on the latest version" now, so its "good" :)

                    C

                    1 Reply Last reply Reply Quote 0
                    • P
                      phil.davis
                      last edited by

                      Mine also showed the "upgrade" to 0.20 and after pressing Confirm to let it do it, all is well reporting 2.3.3

                      The issue is that there are multiple "parts/packages" that make up "pfSense". Normally "parts" would be released along with actual new code that has a "proper" release version. So it would find the "main" version to display and say that "2.3.4" (for example) is available. But in this case there have been some changes/fixes to the bit called pfsense-upgrade going from about 0.16 to 0.20. The GUI code sees that 0.20<2.3.3 and thus says that the system 2.3.3 is newer than what it thinks is the release version (0.20).

                      I guess the code that parses the results of checking for upgrades needs to be smarter, and understand what pieces might come separately from the complete release. Then it needs to work out how to explain to the user that the "main" version is still 2.3.3 but that some component(s) upgrade is available.

                      As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                      If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                      1 Reply Last reply Reply Quote 0
                      • K
                        kpa
                        last edited by

                        The proper solution to this would be to present two types of updates to the user, one that is the "firmware" level update and one that only updates the individual packages within a version of the firmware.

                        1 Reply Last reply Reply Quote 0
                        • J
                          java007md
                          last edited by

                          @RonpfS:

                          @Renato:

                          I've pushed a fix, it's on pfSense-upgrade 0.19.

                          pfSense-upgrade was considering its new version as a new firmware version. The issue is harmless and if you finish the upgrade nothing bad will happen.

                          Fix is on version 0.19. As soon as it's available it's safe to manually run 'pkg upgrade pfSense-upgrade' on console to go to latest verssion.

                          This issue is being tracked at https://redmine.pfsense.org/issues/7343

                          Sorry for the inconvenience

                          So the only way to fix this "issue" is to run pkg upgrade pfSense-upgrade from the console?
                          And it won't reboot the box ?

                          Using the GUI upgrade button will fix this, but will reboot.

                          Using the console 'pkg upgrade pfSense-upgrade' will fix this and does not require a reboot.

                          1 Reply Last reply Reply Quote 0
                          • RonpfSR
                            RonpfS
                            last edited by

                            [2.3.3-RELEASE][root@somewhere.local]/root: pkg upgrade pfSense-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.
                            The following 1 package(s) will be affected (of 0 checked):
                            
                            Installed packages to be UPGRADED:
                                    pfSense-upgrade: 0.17 -> 0.20 [pfSense]
                            
                            Number of packages to be upgraded: 1
                            
                            11 KiB to be downloaded.
                            
                            Proceed with this action? [y/N]: y
                            Fetching pfSense-upgrade-0.20.txz: 100%   11 KiB  11.5kB/s    00:01
                            Checking integrity... done (0 conflicting)
                            [1/1] Upgrading pfSense-upgrade from 0.17 to 0.20...
                            [1/1] Extracting pfSense-upgrade-0.20: 100%
                            [2.3.3-RELEASE][root@somewhere.local]/root:
                            
                            

                            2.3.3.JPG
                            2.3.3.JPG_thumb

                            2.4.5-RELEASE-p1 (amd64)
                            Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
                            Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

                            1 Reply Last reply Reply Quote 0
                            • JSmoradaJ
                              JSmorada
                              last edited by

                              I'm seeing the same thing as well but am showing the latest base system as 0.20. Looked at the issue tracking and saw I'm not the only one who sees 0.20.

                              1 Reply Last reply Reply Quote 0
                              • P
                                phil.davis
                                last edited by

                                @nipstech:

                                I'm seeing the same thing as well but am showing the latest base system as 0.20. Looked at the issue tracking and saw I'm not the only one who sees 0.20.

                                That is true. Just do the suggested "upgrade". It will install that component that is v0.20. Then it will understand that the system as a whole is up-to-date running 2.3.3.

                                The logic there just needs to know that components might be needing an update, not the "system as a whole", and have a way to "explain" that to the user.

                                As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                                If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                                1 Reply Last reply Reply Quote 0
                                • A
                                  aGeekhere
                                  last edited by

                                  The system is on a later version than
                                  the official release.

                                  Current Base System
                                  2.3.3
                                  Latest Base System
                                  0.20
                                  Confirm Update

                                  Going to try the update

                                  Strange, it just fixed itself before I could run the update
                                  The system is on the latest version.

                                  Never Fear, A Geek is Here!

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    JMarch
                                    last edited by

                                    If you don't have console access just go to Diagnostics –> Command Prompt and in "Execute Shell Command" type

                                    pkg upgrade --yes pfsense-upgrade

                                    This will upgrade you from 0.17 to 0.20 without needing console access or to reboot.

                                    1 Reply Last reply Reply Quote 0
                                    • H
                                      HardChargin
                                      last edited by

                                      Thanks all.  I too was caught by this and in System/Update seeing current base system 2.3.3, latest base system .20.  After reading the posts here, got the confidence to hit the confirm button, let it do it's thing, it rebooted, and now I'm back up and working along with showing 2.3.3 and system is on the latest version.

                                      1 Reply Last reply Reply Quote 0
                                      • johnpozJ
                                        johnpoz LAYER 8 Global Moderator
                                        last edited by

                                        "System rebooted afterwards"

                                        You mean you rebooted - that update pfsense-upgrade wouldn't cause a reboot.

                                        An intelligent man is sometimes forced to be drunk to spend time with his fools
                                        If you get confused: Listen to the Music Play
                                        Please don't Chat/PM me for help, unless mod related
                                        SG-4860 24.11 | Lab VMs 2.8, 24.11

                                        1 Reply Last reply Reply Quote 0
                                        • B
                                          bimmerdriver
                                          last edited by

                                          @java007md:

                                          @RonpfS:

                                          @Renato:

                                          I've pushed a fix, it's on pfSense-upgrade 0.19.

                                          pfSense-upgrade was considering its new version as a new firmware version. The issue is harmless and if you finish the upgrade nothing bad will happen.

                                          Fix is on version 0.19. As soon as it's available it's safe to manually run 'pkg upgrade pfSense-upgrade' on console to go to latest verssion.

                                          This issue is being tracked at https://redmine.pfsense.org/issues/7343

                                          Sorry for the inconvenience

                                          So the only way to fix this "issue" is to run pkg upgrade pfSense-upgrade from the console?
                                          And it won't reboot the box ?

                                          Using the GUI upgrade button will fix this, but will reboot.

                                          Using the console 'pkg upgrade pfSense-upgrade' will fix this and does not require a reboot.

                                          The console command worked for me. It did not require a reboot, as you said.

                                          1 Reply Last reply Reply Quote 0
                                          • J
                                            jwt Netgate
                                            last edited by

                                            fixed in 2.3.3_p1

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