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

    Post update, 6100 having issues with package repo / missing package DB

    Scheduled Pinned Locked Moved
    Official Netgate® Hardware
    3
    8
    377
    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.
    • V
      virtualuk
      last edited by

      Hi folks,

      Happy 6100 customer here for the past couple of years, has been working flawlessly since day one. This week I updated both the firmware and software versions after noticing I had been tardy about updating the firmware. Here are my particulars:

      System: Netgate 6100
      BIOS: Vendor: INSYDE Corp.
      Version: CORDOBA-03.00.00.03t
      Release Date: Fri Mar 17 2023
      Version: 23.09.1-RELEASE (amd64)
      built on Mon Dec 11 10:24:00 PST 2023
      FreeBSD 14.0-CURRENT
      Current Base System23.09.1
      Latest Base System23.09.1
      Firmware Current Firmware Version03.00.00.03t-uc-18
      Firmware Latest Firmware Version03.00.00.03t-uc-18

      On the software update page it shows that I'm on the current version and shows status in green as "Up to date.", however here's where I'm seeing issues:

      1, In the Messages field of the update page it shows "pfSense-repoc: failed to fetch the repo data"
      2, I'm also unable to remove pfSense packages that have been installed as it waits for a while and then shows "Another instance of pfSense-upgrade is running. Try again later".
      3, There are no available pfSense packages showing up at all now

      I'm not sure if it's related or not, but I've also started to get a bunch of intermittent connectivity issues across the WAN interface since the upgrade too. No problems on internal LAN & VLANs but connectivity between the WAN interface and my fiber router (Arris) has started to get flakey. If I connect direct to the fiber router no such connectivity problems happen. Could be purely coincidental timing, but started after the update so I'm thinking if I can figure out how to fix the state of my 6100, fingers crossed the connectivity issues get resolved too.

      I tried to clean up the OS packages with "pkg-static clean -ay" but that gives the following:
      pkg-static: Repository pfSense-core missing. 'pkg update' required
      pkg-static: No package database installed. Nothing to do!

      Not sure where to go from here though, any suggestions / help would be greatly appreciated!

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Rebel Alliance @virtualuk
        last edited by

        @virtualuk said in Post update, 6100 having issues with package repo / missing package DB:

        Another instance of pfSense-upgrade is running

        If it doesn't clear up after a while, try restarting pfSense.

        Try changing branches, and back again:
        https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

        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!

        V 1 Reply Last reply Reply Quote 0
        • V
          virtualuk @SteveITS
          last edited by

          @SteveITS Thanks - I have tried rebooting (both hard and soft) with no impact, as well as the actions on the link about library errors.

          When you say changing branches, just want to check you mean from stable to snapshot and then back to stable?

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

            Something I just noticed which I thought was curious, I'm not sure if this has anything to do with the current issue or not. When I get shell access, if I try to ping certain addresses I get different responses. I had been receiving messages after the update about backup not being able to get to acb.netgate.com.

            [23.09.1-RELEASE][@Netgate6100..]/root: ping -c 3 google.com
            PING google.com (172.217.12.110): 56 data bytes
            ping: sendto: Permission denied
            ping: sendto: Permission denied
            ping: sendto: Permission denied

            --- google.com ping statistics ---
            3 packets transmitted, 0 packets received, 100.0% packet loss
            [23.09.1-RELEASE][@Netgate6100..]/root: ping -c 3 bing.com
            PING bing.com (13.107.21.200): 56 data bytes
            64 bytes from 13.107.21.200: icmp_seq=0 ttl=112 time=5.316 ms
            64 bytes from 13.107.21.200: icmp_seq=1 ttl=112 time=5.284 ms
            64 bytes from 13.107.21.200: icmp_seq=2 ttl=112 time=5.336 ms

            --- bing.com ping statistics ---
            3 packets transmitted, 3 packets received, 0.0% packet loss
            round-trip min/avg/max/stddev = 5.284/5.312/5.336/0.021 ms
            [23.09.1-RELEASE][@Netgate6100..]/root: ping -c 3 acb.netgate.com
            PING acb.netgate.com (208.123.73.212): 56 data bytes
            ping: sendto: Permission denied
            ping: sendto: Permission denied
            ping: sendto: Permission denied

            --- acb.netgate.com ping statistics ---
            3 packets transmitted, 0 packets received, 100.0% packet loss

            1 Reply Last reply Reply Quote 0
            • V
              virtualuk @virtualuk
              last edited by

              @SteveITS - never mind the question about switching branches, I tried and it gives similar errors about missing repo. I think at this point I'm looking at a full reset unless anyone has any ideas.

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

                Putting this here for anyone else who finds them in a similar predicament. I'm kicking myself for this because many moons ago I knew there was a reason I didn't use suricata on my 6100. I neglected to mention that around the time of the update (not sure if before or after, I think moments before) I installed suricata. I'd had issues with it in the past but sufficient time had passed that I'd forgotten about the headaches.

                The intermittent connectivity issues I was seeing stopped as soon as a I removed suricata (ssh'ing into the unit pkg-static remove -yf pfSense-pkg-suricata). I'm now able to ping the addresses above without issue.

                Then I went to perform a clean with "pkg-static clean -ay" and got the following
                pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended
                pkg-static: Repository pfSense-core missing. 'pkg update' required
                pkg-static: No package database installed. Nothing to do!

                So I ran the bootstrap and got this using "pkg bootstrap -f"
                The package management tool is not yet installed on your system.
                Do you want to fetch and install it now? [y/N]: y
                Bootstrapping pkg from pkg+https://pfsense-plus-pkg-devel.netgate.com/pfSense_plus-master_amd64-pfSense_plus-devel, please wait...
                Verifying signature with trusted certificate beta.pfsense.org.20151223... done
                Installing pkg-1.20.9...
                Newer FreeBSD version for package pkg:
                To ignore this error set IGNORE_OSVERSION=yes

                • package: 1500006
                • running kernel: 1400094
                  Ignore the mismatch and continue? [y/N]: n
                  package pkg is already installed, forced install
                  Extracting pkg-1.20.9: 100%
                  Scanning /usr/share/certs/untrusted for certificates...
                  Scanning /usr/share/certs/trusted for certificates...
                  .....

                After that ran successfully I ran this and the available packages showed back in pfSense using this "pkg-static install -fy pkg pfSense-repo pfSense-upgrade"
                Updating pfSense-core repository catalogue...
                Fetching meta.conf: 100% 163 B 0.2kB/s 00:01
                Fetching packagesite.pkg: 100% 2 KiB 1.6kB/s 00:01
                Processing entries: 100%
                pfSense-core repository update completed. 5 packages processed.
                Updating pfSense repository catalogue...
                Fetching meta.conf: 0%
                pfSense repository is up to date.
                All repositories are up to date.
                Updating database digests format: 100% 1 B 0.0kB/s 00:01
                The following 3 package(s) will be affected (of 0 checked):

                Installed packages to be UPGRADED:
                pfSense-repo: 23.09.1 -> 24.03.a.20231221.0600 [pfSense]
                pfSense-upgrade: 1.2.1 -> 1.2.1_1 [pfSense]

                Installed packages to be REINSTALLED:
                pkg-1.20.9 [pfSense]

                Number of packages to be upgraded: 2
                Number of packages to be reinstalled: 1

                11 MiB to be downloaded.
                [1/3] Fetching pfSense-repo-24.03.a.20231221.0600.pkg: 100% 6 KiB 6.6kB/s 00:01
                [2/3] Fetching pkg-1.20.9.pkg: 100% 10 MiB 11.0MB/s 00:01
                [3/3] Fetching pfSense-upgrade-1.2.1_1.pkg: 100% 21 KiB 21.4kB/s 00:01
                Checking integrity... done (0 conflicting)
                [1/3] Upgrading pfSense-repo from 23.09.1 to 24.03.a.20231221.0600...
                [1/3] Extracting pfSense-repo-24.03.a.20231221.0600: 100%
                [2/3] Reinstalling pkg-1.20.9...
                [2/3] Extracting pkg-1.20.9: 100%
                Scanning /usr/share/certs/untrusted for certificates...
                Scanning /usr/share/certs/trusted for certificates...
                ....
                Scanning /usr/local/share/certs for certificates...
                [3/3] Upgrading pfSense-upgrade from 1.2.1 to 1.2.1_1...
                [3/3] Extracting pfSense-upgrade-1.2.1_1: 100%
                You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.

                It looks like I'm back in business without having to hit the nuke button. Just gotta remember that suricata and my setup for some reason aren't friends :)

                S 1 Reply Last reply Reply Quote 0
                • S
                  SteveITS Rebel Alliance @virtualuk
                  last edited by

                  @virtualuk Nice, yeah was going to say that sounds like something was blocking the pings. Was Suricata running on WAN? That would scan traffic from pfSense, plus sees everything coming from the WAN IP because of NAT. Try it on LAN instead.

                  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!

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

                    It does look like you upgraded to the 24.03 dev snapshot though.

                    If you're running ZFS you might consider rolling back to an earlier BE snapshot and re-upgrading to reach 23.09.1.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post