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

    Upgraded Package before Upgrading to 2.7.1 - System screwed!

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    11 Posts 5 Posters 2.4k 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.
    • K
      Kidder 0
      last edited by stephenw10

      Hi Everyone,

      I unfortunately went and upgraded a package (pfblockerng) before I saw there was a system upgrade from 2.7.0 to 2.7.1

      When I upgraded pfblocker, I can see it upgraded a bunch of packages:

      Nov 28 08:44:33	pkg-static	56221	gettext-runtime upgraded: 0.21.1 -> 0.22_1
Nov 28 08:44:34	pkg-static	56221	libxml2 upgraded: 2.10.4 -> 2.10.4_1
Nov 28 08:44:47	pkg-static	56221	python311 upgraded: 3.11.3 -> 3.11.6
Nov 28 08:44:48	pkg-static	56221	nettle upgraded: 3.8.1 -> 3.9.1
Nov 28 08:44:48	pkg-static	56221	lua54 upgraded: 5.4.4 -> 5.4.6
Nov 28 08:44:49	pkg-static	56221	py311-setuptools upgraded: 63.1.0 -> 63.1.0_1
Nov 28 08:44:50	pkg-static	56221	icu upgraded: 73.1,1 -> 73.2,1
Nov 28 08:44:50	pkg-static	56221	xxhash upgraded: 0.8.1_2 -> 0.8.2
Nov 28 08:44:51	pkg-static	56221	php82 upgraded: 8.2.6 -> 8.2.11
Nov 28 08:44:51	pkg-static	56221	zstd upgraded: 1.5.4_2 -> 1.5.5
Nov 28 08:44:51	pkg-static	56221	sqlite3 upgraded: 3.41.2,1 -> 3.43.1,1
Nov 28 08:44:51	pkg-static	56221	libmaxminddb upgraded: 1.7.1 -> 1.7.1_1
Nov 28 08:44:51	pkg-static	56221	py311-sqlite3 upgraded: 3.11.3_8 -> 3.11.6_8
Nov 28 08:44:52	pkg-static	56221	lighttpd upgraded: 1.4.70 -> 1.4.72
Nov 28 08:44:52	pkg-static	56221	jq upgraded: 1.6 -> 1.7_1
Nov 28 08:44:52	pkg-static	56221	php82-intl upgraded: 8.2.6 -> 8.2.11
Nov 28 08:44:52	pkg-static	56221	py311-maxminddb upgraded: 2.3.0 -> 2.4.0
Nov 28 08:44:52	pkg-static	56221	pfSense-pkg-pfBlockerNG-devel upgraded: 3.2.0_5 -> 3.2.0_6

      This has left my system in a state where I can now NOT start pfblocker nor can I upgrade the system to 2.7.1.

      When I try to upgrade to 2.7.1 from the GUI I get:

      >>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: . done
Processing entries: . done
pfSense-core repository update completed. 4 packages processed.
Updating pfSense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.pkg: .... done
Processing entries: 
Processing entries............. done
pfSense repository update completed. 549 packages processed.
All repositories are up to date.
>>> Upgrading -upgrade... failed.

      When I log into console and try and upgrade from there (ie. item 13) I get:

      /bin/sh: cannot open /usr/local/sbin/-upgrade: No such file or directory
ld-elf.so.1: Shared object "libcrypto.so.30" not found, required by "php-cgi"
ld-elf.so.1: Shared object "libcrypto.so.30" not found, required by "php"
ld-elf.so.1: Shared object "libcrypto.so.30" not found, required by "php"

      I have scoured the internet to try and figure out a fix ... but haven't seen anything that makes much sense. Does anyone have any suggestions other then to rebuild my system?

      I DID TAKE A BACKUP before I went to update pfblocker - so if I have to a do a whole rebuild - it won't be as painful .... but still not something I want to do.

      Thanks,
      C

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

        It may well be fastest to install 2.7.1 clean and restore your config.

        However you may be able to switch the update repo back to 2.7.0 and force reinstall the correct pkgs from there:
        https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#forced-pkg-reinstall

        Steve

        D 1 Reply Last reply Reply Quote 0
        • D
          datanet @stephenw10
          last edited by

          @stephenw10

          I have 2 remote systems that I simultaneously did the same exact thing to and now stuck in the same boat. Since I am connected remotely to both firewalls performing a clean install and restoring is not an option.

          When you say to "switch the update repo back to 2.7.0" are you talking about in the System>Update>System Update and choosing the "Previous Stable Release (2.7.0)" in the Branch selection?

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

            Yes, set it back to 2.7.0 there and see if it can force update at least the pkg package.

            D 3 Replies Last reply Reply Quote 0
            • D
              datanet @stephenw10
              last edited by

              @stephenw10

              I changed it to 2.7.0 and then ran the following command from a putty shell session:

              pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade

              and then

              pkg-static upgrade -f

              I was a bit afraid to reboot the firewall since this is a remote system. So I changed the repo back to 2.7.1 after running the above commands and was able to install the upgrade to 2.7.1.

              In the process of rebooting now. Fingers crossed it comes back up.

              K 1 Reply Last reply Reply Quote 2
              • D
                datanet @stephenw10
                last edited by

                @stephenw10

                System came back up and had to reinstall a couple of the packages from the Installed Packages page before those particular package services would start properly. But all appears to be OK.

                Won't make that mistake again to update packages before updating to the latest pfSense version.

                1 Reply Last reply Reply Quote 0
                • D
                  datanet @stephenw10
                  last edited by

                  @stephenw10

                  On the second system I had to also run the following command since i was getting an error about "no active remote repositories configured"

                  ln /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf /usr/local/etc/pkg/repos/pfSense.conf

                  I had changed and saved a couple times between the 2.7.0 and 2.7.1 repo and only running the above command allowed me to continue with the above steps.

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

                    Nice result. Going forward the upgrade system should prevent this happening.

                    1 Reply Last reply Reply Quote 0
                    • R
                      Robert42 @Kidder 0
                      last edited by

                      @Kidder-0
                      I had a bit worse result. I was still running 23_05 and tried to upgrade pfBlockerNG and the result was an unbootable router. Grrrr..., I had a memstick image of 2.7.0 on my harddrive, no internet access to pull 2.7.1 so install 2.7.0 is what I had to do and upgrade from there. Fun, fun! Oh well, I needed to update to 2.7.1 anyway with the change in licensing terms... but not a fun way to start the morning.

                      S 1 Reply Last reply Reply Quote 2
                      • K
                        Kidder 0 @datanet
                        last edited by

                        @datanet said in Upgraded Package before Upgrading to 2.7.1 - System screwed!:

                        @stephenw10

                        I changed it to 2.7.0 and then ran the following command from a putty shell session:

                        pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade

                        and then

                        pkg-static upgrade -f

                        I was a bit afraid to reboot the firewall since this is a remote system. So I changed the repo back to 2.7.1 after running the above commands and was able to install the upgrade to 2.7.1.

                        In the process of rebooting now. Fingers crossed it comes back up.

                        Hi Everyone,

                        I just wanted to let everyone know this worked PERFECTLY. Followed the exact same steps above, but once I did the

                        pkg-static upgrade -f

                        I went back to the gui and reset the upgrade version to 2.7.1. Did a refresh on the main page and then went back to update .... hit confirm and the system updated NO PROBLEM.

                        Came right back up after reboot and life is good.

                        Always awesome when you have people help you solve problems like this ...Thanks @stephenw10 and @datanet

                        Cheers,
                        C

                        1 Reply Last reply Reply Quote 1
                        • S
                          sengork @Robert42
                          last edited by

                          @Robert42 I've also been hit with the same boot issue you describe

                          1 Reply Last reply Reply Quote 0
                          • C CyclonePF referenced this topic on
                          • K Kidder 0 referenced this topic on
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.