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

    Cannot upgrade from 22.09.a.20220729.0600 to another version

    Scheduled Pinned Locked Moved Plus 23.01 Development Snapshots (Retired)
    6 Posts 2 Posters 1.5k 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.
    • S
      ssppcc
      last edited by ssppcc

      Hi all,

      I'm trying to upgrade my instance of pfSense from 22.09.a.20220729.0600 to a newer version, but I cannot because the system says that I'm in the newest version

      mVclNOf.png

      I was following this threat in order to solve the problem, but I'm in the same position without luck.

      This is my /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf

      FreeBSD: { enabled: no }
      
      pfSense-core: {
        url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core",
        mirror_type: "srv",
        signature_type: "fingerprints",
        fingerprints: "/usr/local/share/pfSense/keys/pkg",
        enabled: yes
      }
      
      pfSense: {
        url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05",
        mirror_type: "srv",
        signature_type: "fingerprints",
        fingerprints: "/usr/local/share/pfSense/keys/pkg",
        enabled: yes
      }
      

      and this is my /usr/local//etc/pkg/repos/pfSense.conf

      FreeBSD: { enabled: no }
      
      pfSense-core: {
        url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-core",
        mirror_type: "srv",
        signature_type: "fingerprints",
        fingerprints: "/usr/local/share/pfSense/keys/pkg",
        enabled: yes
      }
      
      pfSense: {
        url: "pkg+https://firmware.netgate.com/pkg/pfSense_plus-v22_05_amd64-pfSense_plus_v22_05",
        mirror_type: "srv",
        signature_type: "fingerprints",
        fingerprints: "/usr/local/share/pfSense/keys/pkg",
        enabled: yes
      }
      

      the output of pkg-static info -x pfSense-upgrade is:

      pkg-static: Invalid ABI
      pkg-static: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
      pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
      pfSense-upgrade-1.0_29
      

      and the output of pkg bootstrap -f is :

      pkg: Invalid ABI
      pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
      pkg(8) is already installed. Forcing reinstallation through pkg(7).
      pkg: Invalid ABI
      pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
      pkg(8) is already installed. Forcing reinstallation through pkg(7).
      pkg: Invalid ABI
      pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended
      pkg(8) is already installed. Forcing reinstallation through pkg(7).
      pkg: Invalid ABI
      

      Those are the logs that I can see in the GUI

      pkg-static	98471	pfSense-upgrade upgraded: 1.0_29 -> 1.0_33
      pkg-static	38045	pfSense-upgrade downgraded: 1.0_33 -> 1.0_29
      pkg-static	29742	pfSense-upgrade upgraded: 1.0_29 -> 1.0_33
      pkg-static	58543	pfSense-upgrade downgraded: 1.0_33 -> 1.0_29
      pkg-static	43714	pfSense-upgrade upgraded: 1.0_29 -> 1.0_33
      

      Any help would be much appreciated
      Thanks in advance

      S 1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        I would first try switching the repo from Dev to Stable and back. The symlink at /usr/local/etc/pkg/repos/pfSense.conf should be referencing /usr/local/share/pfSense/pkg/repos/pfSense-repo-devel.conf when you have Dev selected.

        However coming from 22.09 you will hit the the ABI change issue described in the CE snapshot blog post: https://www.netgate.com/blog/ce-snapshots-on-php-8.1-and-freebsd-main

        So first try running pkg-static -d update and see what errors it reports. If it is the ABI mismatch run:

        pkg-static -o ABI=FreeBSD:14:amd64 -o IGNORE_OSVERSION=yes update
        pkg-static -o ABI=FreeBSD:14:amd64 -o IGNORE_OSVERSION=yes upgrade -fy pkg
        pkg-static -o ABI=FreeBSD:14:amd64 -o IGNORE_OSVERSION=yes upgrade -fy pfSense-upgrade
        

        Then retry the update.

        Steve

        1 Reply Last reply Reply Quote 1
        • S
          ssppcc @ssppcc
          last edited by

          @stephenw10

          Now I'm in a looop, when I try to upgrade using pfsense-upgrade the system enter in a loop trying to upgrade from 1.0_29 -> 1.0_33 and then make a downgrade from pfSense-upgrade: 1.0_33 -> 1.0_29 [pfSense]

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Hmm, do you have logs showing that?

            If you're using ZFS and have a snapshot from 22.05 you might just roll back to that and wait for the upgrade issues to be fixed. That should be imminent.

            S 1 Reply Last reply Reply Quote 0
            • S
              ssppcc @stephenw10
              last edited by

              @stephenw10

              After few days, that's my current log:

              [22.05-RELEASE][root@pfSense.mydomain.tld]/boot: pfSense-upgrade
              >>> Creating automatic rollback boot environment... done.
              >>> Updating repositories metadata...
              Updating pfSense-core repository catalogue...
              Fetching meta.conf: . done
              Fetching packagesite.pkg: . done
              Processing entries: .. done
              pfSense-core repository update completed. 15 packages processed.
              Updating pfSense repository catalogue...
              Fetching meta.conf: . done
              Fetching packagesite.pkg: .......... done
              Processing entries: .......... done
              pfSense repository update completed. 551 packages processed.
              All repositories are up to date.
              >>> Locking package pkg... done.
              >>> Upgrading pfSense-upgrade... done.
              >>> Unlocking package pkg... done.
              ERROR: It was not possible to determine pkg remote version
              >>> Setting vital flag on pfSense-upgrade... done.
              ERROR: It was not possible to determine pkg remote version
              >>> Updating repositories metadata...
              Updating pfSense-core repository catalogue...
              pkg-static: Repository pfSense-core has a wrong packagesite, need to re-create database
              Fetching meta.conf: . done
              Fetching packagesite.pkg: . done
              Processing entries:
              pkg-static: wrong architecture: FreeBSD:12:amd64 instead of FreeBSD:14:amd64
              pkg-static: repository pfSense-core contains packages with wrong ABI: FreeBSD:12:amd64
              Processing entries... done
              Unable to update repository pfSense-core
              Updating pfSense repository catalogue...
              pkg-static: Repository pfSense has a wrong packagesite, need to re-create database
              Fetching meta.conf: . done
              Fetching packagesite.pkg: .......... done
              Processing entries:
              pkg-static: wrong architecture: FreeBSD:12:amd64 instead of FreeBSD:14:amd64
              pkg-static: repository pfSense contains packages with wrong ABI: FreeBSD:12:amd64
              Processing entries... done
              Unable to update repository pfSense
              Error updating repositories!
              >>> Locking package pkg... done.
              ERROR: It was not possible to determine pfSense-upgrade remote version
              ERROR: It was not possible to determine pfSense-upgrade remote version
              >>> Upgrading pfSense-upgrade... failed.
              >>> Unlocking package pkg... done.
              
              1 Reply Last reply Reply Quote 0
              • R rcoleman-netgate moved this topic from General pfSense Questions on
              • S
                ssppcc
                last edited by

                My solution was delete de ifsentence at line 720 from /user/local/libexec/pfSense-upgrade

                Then:

                rm /usr/local/etc/pkg/repos/pfSense.conf 
                ln /usr/local/share/pfSense/pkg/repos/pfSense-repo-devel.conf /usr/local/etc/pkg/repos/pfSense.conf
                pfSense-upgrade -fy
                

                I find the solution in this threat
                https://forum.netgate.com/topic/176064/attempting-to-update-to-23-01-devel-corrupts-my-pfsense-installation/41

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