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

23.01 -> 23.05 upgrade failed

Problems Installing or Upgrading pfSense Software
26
84
41.9k
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.
  • C
    constantin @SteveITS
    last edited by Jun 2, 2023, 6:09 PM

    @SteveITS I did tried all those option without success.

    P 1 Reply Last reply Jun 3, 2023, 2:10 PM Reply Quote 0
    • P
      pete @constantin
      last edited by Jun 3, 2023, 2:10 PM

      @constantin

      On a rebuild here from scratch waited a day to update from 23.01 to 23.05 via the console. All repositories / updates worked after a day.

      • Pete

      Auto mater
      23.09.1-RELEASE (amd64)
      built on Mon Dec 11 12:24:00 CST 2023
      FreeBSD 14.0-CURRENT
      PFSense + Qotom - Master
      PFSense + Jetway - Backup
      PFSense + Jetway - Backup
      PFSense + Generic - Backup

      N 1 Reply Last reply Jun 3, 2023, 2:17 PM Reply Quote 0
      • N
        netblues @pete
        last edited by netblues Jun 3, 2023, 2:26 PM Jun 3, 2023, 2:17 PM

        Something isn't right.
        Downloads seems to stall at various points

        Have tried rebooting.
        No internet issues too.

         pkg-static clean -ay ; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
        The following package files will be deleted:
        	/var/cache/pkg/pfSense-repo-23.05~9076a69f3e.pkg
        	/var/cache/pkg/pkg-1.19.1_1~6eedfbfed3.pkg
        	/var/cache/pkg/pfSense-repo-23.05.pkg
        The cleanup will free 9 MiB
        Deleting files: 100%
        All done
        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 4 package(s) will be affected (of 0 checked):
        
        New packages to be INSTALLED:
        	pfSense-repoc: 20230530_2 [pfSense]
        
        Installed packages to be UPGRADED:
        	pfSense-repo: 23.01 -> 23.05 [pfSense]
        	pfSense-upgrade: 1.0_58 -> 1.0_66 [pfSense]
        
        Installed packages to be REINSTALLED:
        	pkg-1.19.1_1 [pfSense]
        
        Number of packages to be installed: 1
        Number of packages to be upgraded: 2
        Number of packages to be reinstalled: 1
        
        The process will require 17 MiB more space.
        14 MiB to be downloaded.
        [1/4] Fetching pfSense-repo-23.05.pkg: 100%    6 KiB   6.0kB/s    00:01    
        [2/4] Fetching pkg-1.19.1_1.pkg:  70%    6 MiB   6.0MB/s    00:00 ETA
        
        

        and

        pkg-static clean -ay ; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
        The following package files will be deleted:
        	/var/cache/pkg/pfSense-repo-23.05~9076a69f3e.pkg
        	/var/cache/pkg/pkg-1.19.1_1~6eedfbfed3.pkg
        	/var/cache/pkg/pfSense-repo-23.05.pkg
        	/var/cache/pkg/pkg-1.19.1_1.pkg
        	/var/cache/pkg/pfSense-upgrade-1.0_66~c47029f80d.pkg
        	/var/cache/pkg/pfSense-upgrade-1.0_66.pkg
        	/var/cache/pkg/pfSense-repoc-20230530_2~16eda60f02.pkg
        The cleanup will free 14 MiB
        Deleting files: 100%
        All done
        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 4 package(s) will be affected (of 0 checked):
        
        New packages to be INSTALLED:
        	pfSense-repoc: 20230530_2 [pfSense]
        
        Installed packages to be UPGRADED:
        	pfSense-repo: 23.01 -> 23.05 [pfSense]
        	pfSense-upgrade: 1.0_58 -> 1.0_66 [pfSense]
        
        Installed packages to be REINSTALLED:
        	pkg-1.19.1_1 [pfSense]
        
        Number of packages to be installed: 1
        Number of packages to be upgraded: 2
        Number of packages to be reinstalled: 1
        
        The process will require 17 MiB more space.
        14 MiB to be downloaded.
        [1/4] Fetching pfSense-repo-23.05.pkg: 100%    6 KiB   6.0kB/s    00:01    
        [2/4] Fetching pkg-1.19.1_1.pkg:  80%    7 MiB   6.3MB/s    00:00 ETA^C
        
        

        Are netgate servers under attack?

        1 Reply Last reply Reply Quote 0
        • C
          constantin
          last edited by Jun 6, 2023, 2:37 PM

          I am using AWS pfsense plus, there no internet issues.
          and very strange that after running that command the upgrade worked. Last week that didn't worked.

          Here are my output of

          pkg-static clean -ay ; pkg-static install -fy pkg pfSense-repo pfSense-upgrade
          
          pkg-static: Repository pfSense-core has a wrong packagesite, need to re-create database
          pkg-static: Repository pfSense-core cannot be opened. 'pkg update' required
          The following package files will be deleted:
                  /var/cache/pkg/pfSense-repo-23.01~6ab0bb83bb.pkg
                  /var/cache/pkg/pkg-1.18.4_4~e5964fbef2.pkg
                  /var/cache/pkg/pfSense-repo-23.01.pkg
                  /var/cache/pkg/pkg-1.18.4_4.pkg
                  /var/cache/pkg/pfSense-upgrade-1.0_61~4c43becbfa.pkg
                  /var/cache/pkg/pkg-1.19.1_1~6eedfbfed3.pkg
                  /var/cache/pkg/pfSense-upgrade-1.0_61.pkg
                  /var/cache/pkg/pfSense-pkg-sudo-0.3_8~c582a59d93.pkg
                  /var/cache/pkg/pfSense-pkg-sudo-0.3_8.pkg
                  /var/cache/pkg/pkg-1.19.1_1.pkg
                  /var/cache/pkg/pfSense-upgrade-1.0_66~c47029f80d.pkg
                  /var/cache/pkg/pfSense-upgrade-1.0_66.pkg
          The cleanup will free 18 MiB
          Deleting files: 100%
          All done
          Updating pfSense-core repository catalogue...
          pkg-static: Repository pfSense-core has a wrong packagesite, need to re-create database
          Fetching meta.conf: 100%    163 B   0.2kB/s    00:01    
          Fetching packagesite.pkg: 100%    2 KiB   2.3kB/s    00:01    
          Processing entries: 100%
          pfSense-core repository update completed. 15 packages processed.
          Updating pfSense repository catalogue...
          pfSense repository is up to date.
          All repositories are up to date.
          The following 3 package(s) will be affected (of 0 checked):
          Installed packages to be DOWNGRADED:
                  pfSense-upgrade: 1.0_66 -> 1.0_61 [pfSense]
                  pkg: 1.19.1_1 -> 1.18.4_4 [pfSense]
          
          Installed packages to be REINSTALLED:
                  pfSense-repo-23.01 [pfSense]
          
          Number of packages to be reinstalled: 1
          Number of packages to be downgraded: 2
          
          9 MiB to be downloaded.
          [1/3] Fetching pfSense-repo-23.01.pkg: 100%    6 KiB   6.0kB/s    00:01    
          [2/3] Fetching pkg-1.18.4_4.pkg: 100%    9 MiB   9.5MB/s    00:01    
          [3/3] Fetching pfSense-upgrade-1.0_61.pkg: 100%   22 KiB  22.5kB/s    00:01    
          Checking integrity... done (0 conflicting)
          [1/3] Reinstalling pfSense-repo-23.01...
          [1/3] Extracting pfSense-repo-23.01: 100%
          [2/3] Downgrading pkg from 1.19.1_1 to 1.18.4_4...
          [2/3] Extracting pkg-1.18.4_4: 100%
          [3/3] Downgrading pfSense-upgrade from 1.0_66 to 1.0_61...
          [3/3] Extracting pfSense-upgrade-1.0_61: 100%
          You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.
          

          I don't have an explanation why that worked today and didn't last week.

          thanks.

          1 Reply Last reply Reply Quote 0
          • pfsense16vP
            pfsense16v @SteveITS
            last edited by Jun 6, 2023, 10:14 PM

            @SteveITS said in 23.01 -> 23.05 upgrade failed:

            https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

            I toggled back to the previous branch (23.01)...waited...and then toggled back to (23.05)....waited... and it worked. I can see the upgrade button again. I will try to upgrade this weekend

            Thanks!

            N 1 Reply Last reply Jun 23, 2023, 9:27 PM Reply Quote 0
            • N
              netboy @pfsense16v
              last edited by Jun 23, 2023, 9:27 PM

              @pfsense16v I am bumped into this discussion on google search - Can I upgrade from 23.01-RELEASE (arm64) to Version 23.05 without any issues? Are all the kinks worked out. I do not want to stuck by issues. Kindly advice

              S 1 Reply Last reply Jun 23, 2023, 9:42 PM Reply Quote 0
              • S
                SteveITS Galactic Empire @netboy
                last edited by Jun 23, 2023, 9:42 PM

                @netboy Not sure if you mean issues with the software, or issues with the upgrade process. There seem to be a stretch of people having "certificate" or other issues starting the upgrade. If you see that there are a few workarounds in this and other threads, basically getting it to update its repo info or certs or whatnot and proceed.

                There are pre-release release notes for a 23.05.1 version, indicating that's coming in the relatively near future. That fixes a bad bug with importing aliases, though there is also a patch to fix it in the System Patches package after upgrading to 23.05.

                Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                Upvote πŸ‘ helpful posts!

                N 1 Reply Last reply Jun 23, 2023, 9:49 PM Reply Quote 0
                • N
                  netboy @SteveITS
                  last edited by Jun 23, 2023, 9:49 PM

                  @SteveITS Thanks as always.
                  I am talking about upgrade issues.
                  From your reply there seems to be something on the works to fix this
                  I get a sense I should wait for the upgrade.
                  I like my pfsense and help in this forum BUT why are there issues (mostly) during upgrade process.
                  I am a bit concerned of late pfsene upgrades always have some problems. Last upgrade was a problem too. Now this.
                  Would you advice for me to wait for the fix?

                  S 1 Reply Last reply Jun 23, 2023, 11:10 PM Reply Quote 0
                  • S
                    SteveITS Galactic Empire @netboy
                    last edited by Jun 23, 2023, 11:10 PM

                    @netboy It’s up to you really. I generally try to wait a week before our first/test upgrade and another week or two before upgrading any clients just to watch the forums. Generally have had no serious issues as a result.

                    Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                    When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                    Upvote πŸ‘ helpful posts!

                    N 1 Reply Last reply Jun 27, 2023, 2:10 AM Reply Quote 1
                    • N
                      netboy @SteveITS
                      last edited by Jun 27, 2023, 2:10 AM

                      @SteveITS I upgraded from 23.01 to 23.05 without a hitch! FYI

                      1 Reply Last reply Reply Quote 1
                      • D
                        driise
                        last edited by Jul 7, 2023, 5:01 PM

                        Putting this out there in case it helps others.

                        I kept dorking at this, tried again when 23.05.1 came out, but still couldn't get the upgrade to work. I opened a support case online, truthfully not expecting a lot of help (I have the free home-lab style license, no support).

                        Netgate TAC responded very quickly to the ticket (maybe 15 minutes), reviewed my notes, and requested remote access if I was ok with that. I didn't have an issue with it, provided them access, and after some digging, they found an issue with how I was loading my Solarflare 10gbe NIC.

                        I found two ways to do this, one using /conf/config.xml with <earlyshellcmd> and the other was in /boot/loader.conf.local. I chose to use config.xml because I used that for something else, it was easy enough.

                        The issue was in how the NDI was being calculated; the 10gbe NICs were not being included in the calculation.

                        TAC stated that the proper way to load the NIC driver was with loader.conf.local. They made that change, I rebooted, and had a new NDI. I already had a reg key I created a month ago because I thought it was a license key issue. I stuck that on, and upgrade was good to go.

                        This was my first exposure to Netgate TAC, and I was really impressed. They were very quick to respond, even though it was limited to the ticket (not live/phone/chat, because, I don't have a support contract). Also taking into account, this was my hardware (Dell R210ii), not a Netgate box.

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