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

    Error upgrading from 22.05 Release to 22.11 Development

    Scheduled Pinned Locked Moved Plus 23.01 Development Snapshots (Retired)
    32 Posts 7 Posters 3.9k 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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      Hmm, well if it's still not showing you any branches it's because the server doesn't recognise the NDI for some reason. Has it changed?

      w0wW 1 Reply Last reply Reply Quote 0
      • w0wW
        w0w @stephenw10
        last edited by

        @stephenw10
        Perhaps I should clarify that the original version was CE 2.6, updated to 22.05, as you know, you have to update twice on 22.01 and then to 22.05. If now, for example, you have installed the latest CE 2.7 and trying to upgrade it to Plus version, you will get a downgrade effect like on the picture

        adc579fa-cfb5-4a32-8c16-39a57b8be14a-изображение.png

        If you try to do the such an upgrade, it will break your installation completely.

        If you try to update the version 22.05 in console, you end with 23.01 version, but no branch appearing after upgrade.
        NDI is still the same, and I can install packages and check for updates,
        6adf2c88-233b-4959-b539-065535e4b58d-изображение.png

        That make me think that some internal branch is selected somehow.

        K stephenw10S 2 Replies Last reply Reply Quote 0
        • K
          kevindd992002 @w0w
          last edited by

          @stephenw10

          I'm trying to do a webgui upgrade now (I still haven't went thru it since two weeks ago when we were talking about this) but all I see now when I go to System -> Update is "unable to check for updates". Do you know what's causing this?

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

            @kevindd992002
            Run pkg-static -d update at the command line and see what error it returns.

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

              @w0w said in Error upgrading from 22.05 Release to 22.11 Development:

              If now, for example, you have installed the latest CE 2.7 and trying to upgrade it to Plus version, you will get a downgrade effect like on the picture

              Yes, upgrading from CE 2.7 to Plus is not supported. Yet.

              1 Reply Last reply Reply Quote 1
              • w0wW
                w0w
                last edited by w0w

                5f9cae22-7b06-4a73-ac89-8aaeb823eb42-image.png
                Yep. Something new today.
                Installed this build and was able to install pfBlockerNG-devel...

                1 Reply Last reply Reply Quote 1
                • K
                  kevindd992002 @stephenw10
                  last edited by

                  @stephenw10 said in Error upgrading from 22.05 Release to 22.11 Development:

                  @kevindd992002
                  Run pkg-static -d update at the command line and see what error it returns.

                  e7f2f24e-d3df-46f5-85b6-81b9e636609f-image.png

                  Ahh, I thought the wrong OS version fix was already incorporated in the GUI update process. So I run these?

                  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
                  
                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Yes, since you still appear to be running a 12.3 kernel you will need to run those first to allow it.

                    Steve

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      kevindd992002 @stephenw10
                      last edited by kevindd992002

                      @stephenw10 said in Error upgrading from 22.05 Release to 22.11 Development:

                      Yes, since you still appear to be running a 12.3 kernel you will need to run those first to allow it.

                      Steve

                      Ok, so I just upgraded everything and reinstalled the packages (uninstalled before the upgrade and reinstall after the upgrade) and now I'm having issues with freeradius. The settings are all intact but my clients cannot connect anymore. I see these in the logs:

                      2b10c361-3ce0-46ae-a504-cd089216e324-image.png

                      Any ideas? Before the upgrade freeradius3 was at 0.15.7_33 and now it's at 0.15.8_1

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

                        There are a number of known issues with the Freeradius package. You're probably hitting this:
                        https://redmine.pfsense.org/issues/13631

                        Steve

                        K 1 Reply Last reply Reply Quote 0
                        • K
                          kevindd992002 @stephenw10
                          last edited by

                          @stephenw10 said in Error upgrading from 22.05 Release to 22.11 Development:

                          There are a number of known issues with the Freeradius package. You're probably hitting this:
                          https://redmine.pfsense.org/issues/13631

                          Steve

                          Oh crap, you're right. I can see that /usr/local/etc/raddb/users is empty.

                          K 1 Reply Last reply Reply Quote 0
                          • K
                            kevindd992002 @kevindd992002
                            last edited by

                            @stephenw10
                            It looks like this is the cause of the issue:

                            https://redmine.pfsense.org/issues/13642

                            Since it already has a commit, does that mean it's aleady deployed in the 2.7 snapshots?

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

                              That is in current 2.7 snapshots, yes.
                              https://github.com/pfsense/FreeBSD-ports/commits/devel/net/pfSense-pkg-frr/files/usr/local/pkg/frr.inc

                              Steve

                              K 1 Reply Last reply Reply Quote 0
                              • K
                                kevindd992002 @stephenw10
                                last edited by

                                @stephenw10 then that means it is not the cause of the issue. I just upgraded to today's snapshot and it still did not fix my credentials issue with freeradius.

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

                                  Right, I wouldn't expect it to. 13642 is just tat specific PHP error. Like I said it looks like you're hitting 13631, which is actually a duplicate of: https://redmine.pfsense.org/issues/13628 and that's still open.

                                  Steve

                                  K 1 Reply Last reply Reply Quote 0
                                  • K
                                    kevindd992002 @stephenw10
                                    last edited by

                                    @stephenw10 I understand but @jimp mentioned 13628's root cause "might be" the same to that of 13642's and 13642 is solved already so I thought they have the same solution. But yeah, 13628 is still open so I guess I'm out of luck.

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