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

    Attempting to update to 23.01 DEVEL corrupts my pfSense installation

    Scheduled Pinned Locked Moved Plus 23.01 Development Snapshots (Retired)
    156 Posts 24 Posters 48.6k 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.
    • G
      gabacho4 Rebel Alliance @cloudroot
      last edited by

      @cloudroot I’d forgotten about the snapshots!!!! That’s a great idea!

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

        Yes rolling back using BE is always an option. It works well between 22.05 and 23.01.

        It doesn't work between 22.05 and 22.01, should you find yourself trying that!

        Steve

        1 Reply Last reply Reply Quote 0
        • V
          Viper_Rus
          last edited by

          Thanks to all. Fixed it like this: Saved the settings without packages. Deployed the old 22.05 image that I received immediately after the update from 2.6. Restored settings. Downloaded and configured the missing packages. If I tried to recover with package settings, I got a broken system. Now everything is ok.

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

            22.09 -> 23.01.a.20221207.0600: Failed with

            Another instance of pfSense-upgrade is running.  Try again later
            

            But it did take longer for this to appear than the previous error (pfSense.conf).

            Edit:
            Let me know if the upgrade path from 22.09 is considered irrelevant. And I'll stop reporting on it.

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

              It is, it's an obsolete path. Because the 22.09 public snapshots were built on FreeBSD 12 the upgrade to 23.01 requires an ABI change. But since both were considered the same branch a the time the upgrade system doesn't see that. So coming from 22.09 will always require some manual intervention.

              Steve

              C 2 Replies Last reply Reply Quote 0
              • C
                cloudroot @stephenw10
                last edited by

                @stephenw10 Ok, thanks for clarifying this. I'll halt my progress reports regarding upgrading from 22.09 then. And I'll patiently wait for 23.01 stable to be released.

                1 Reply Last reply Reply Quote 1
                • C
                  cloudroot @stephenw10
                  last edited by

                  @stephenw10
                  FWIW: Tried an upgrade from 22.05-stable that I have as a BE-backup. To 23.01.a.20221209.1528

                  But still received

                  Another instance of pfSense-upgrade is running.  Try again later
                  
                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    That's more likely another instance really is running but an upgrade issue still exists. It has proven more complex to fix correctly than originally though but should be done shortly.

                    Steve

                    G 1 Reply Last reply Reply Quote 1
                    • G
                      gabacho4 Rebel Alliance @stephenw10
                      last edited by

                      @stephenw10 According to the Redmine task, the issue has been fixed by Luiz Sousa. I'm testing to provide feedback. Now when I try to update, my pfsense box at least doesn't break. However, when I try to update via console after setting the 23.01 repo, I get a "failed to upgrade the repository settings!!!" message. When I try via the GUI, it spins for an eternity and then I just get a white screen. I have no idea what went broke on the backend but man, this is a fun one.

                      T 1 Reply Last reply Reply Quote 0
                      • T
                        tedquade @gabacho4
                        last edited by

                        @gabacho4 Me too, same message and same GUI outcome.

                        Ted Quade

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

                          Yes, as I said above there is still an outstanding issue we are working on there.

                          I will update here when that has been cleared.

                          1 Reply Last reply Reply Quote 0
                          • S ssppcc referenced this topic on
                          • S ssppcc referenced this topic on
                          • pitchforkP
                            pitchfork @stephenw10
                            last edited by

                            @stephenw10 it says resolved there, but still seems to be an issue here.

                            1 Reply Last reply Reply Quote 0
                            • mtarboxM
                              mtarbox
                              last edited by

                              Same. Borked it so bad I needed to submit a ticket and reinstall.
                              4100 base.

                              Si vis pacem, para pactum.

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

                                What errors were you seeing?

                                What version were you upgrading from?

                                If you are coming from a 23.01 snapshot from Dec 6th or earlier you may need to manually upgrade the pfSense-upgrade and pfSense-base pkgs before upgrading.

                                Steve

                                mtarboxM pitchforkP 2 Replies Last reply Reply Quote 0
                                • mtarboxM
                                  mtarbox @stephenw10
                                  last edited by

                                  @stephenw10
                                  I was coming from 22.05 on a brand new 4100.
                                  "Another instance of pfSense-upgrade is running. Try again later" in the GUI.
                                  When I switch to cli, I get "unable to update repositories".
                                  So then I go through the troubleshooting from here:[https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html](link url)
                                  And from there, I borked the install and had to submit a ticket for the image.

                                  Si vis pacem, para pactum.

                                  S 1 Reply Last reply Reply Quote 1
                                  • S
                                    serzyfritz @mtarbox
                                    last edited by

                                    @mtarbox I am also having the exact same errors on my install. Installed pfSense a month ago from the community edition, and upgraded to plus 22.05. A few days ago I switched up to try the Beta, can't get the update to go (same errors). I am also having issues where no packages will install or update either when switched back to 22.05 production listings.

                                    1 Reply Last reply Reply Quote 0
                                    • pitchforkP
                                      pitchfork @stephenw10
                                      last edited by

                                      @stephenw10 coming from 22.05 and switched the upgrade path from stable to beta two days ago.

                                      already tried to run pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade twice. after the 1st run I tried to upgrade via GUI, 2nd time via console. same error messages reported in this thread (they diff whether it's GUI or console)

                                      1 Reply Last reply Reply Quote 1
                                      • Y
                                        yellowRain
                                        last edited by

                                        Netgate 6100
                                        
                                        22.05-RELEASE (amd64)
                                        built on Wed Jun 22 18:56:13 UTC 2022
                                        FreeBSD 12.3-STABLE
                                        

                                        No way to update to 23.01 20221226 :

                                        Another instance of pfSense-upgrade is running.  Try again later
                                        
                                        lawrencesystemsL Y 2 Replies Last reply Reply Quote 0
                                        • lawrencesystemsL
                                          lawrencesystems @yellowRain
                                          last edited by

                                          @yellowrain said in Attempting to update to 23.01 DEVEL corrupts my pfSense installation:

                                          Another instance of pfSense-upgrade is running. Try again later

                                          I am getting the same error as well using virtualzied pfsense plus 22.05.

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

                                            The Another instance of pfSense-upgrade is running. error?

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