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

    check_upgrade: "Updating repositories metadata" returned error code 1

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    96 Posts 27 Posters 23.6k Views 28 Watching
    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.
    • 7 Offline
      753951 @stephenw10
      last edited by

      @stephenw10
      [24.11-RELEASE][root@pfsense.stanar.info]/root: pkg -d update
      DBG(1)[92284]> pkg initialized
      pkg: Unable to open '/usr/local/etc/pkg/repos//pfSense.conf':No such file or directory
      No active remote repositories configured.

      As for pfSense-repoc -ND

      Messages:
      Your device has not been registered for pfSense+. Please purchase a pfSense+ subscription to receive future updates. <a href="https://shop.netgate.com/products/pfsense-software-subscription" target="_blank" rel="noopener noreferrer">Netgate store</a>

      Don't get it. I made no changes in months.

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

        Ok send me your NDI in chat and I'll check it.

        B 1 Reply Last reply Reply Quote 0
        • R Offline
          renanlofiego
          last edited by

          Me too, after the update, I started receiving the message "check_upgrade: "updating repositories metadata" returned error code 1".

          I ran the command "pkg -d update" and it returned the following: "DBG(1)[56533]> pkg initialized
          pkg: Unable to open '/usr/local/etc/pkg/repos//pfSense.conf': No such file or directory
          No active remote repositories configured.
          "

          I don't know if it has to do with the license. Is there still a free pfSense+ license for labs?

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

            So same as above; run pfSense-repoc -ND and see what error that returns.

            Send me your NDI in chat and I'll check it.

            A 1 Reply Last reply Reply Quote 0
            • M Offline
              mrpon8
              last edited by

              check_upgrade: "Updating repositories metadata" returned error code 1
              for resolve this problem only need update the pkg
              into the "Diagnostics, then Command Prompt" run "pkg update -f"

              R 1 Reply Last reply Reply Quote 0
              • R Offline
                renanlofiego @mrpon8
                last edited by

                @mrpon8 When I run this command "pkg update -f" it returns this message "pkg: Unable to open '/usr/local/etc/pkg/repos//pfSense.conf': No such file or directory
                No active remote repositories configured.
                "

                1 Reply Last reply Reply Quote 0
                • B Offline
                  benhamou.ahmed
                  last edited by

                  i have same issue

                  1 Reply Last reply Reply Quote 0
                  • B Offline
                    benhamou.ahmed @stephenw10
                    last edited by

                    @stephenw10 i have same issue

                    1 Reply Last reply Reply Quote 0
                    • H Offline
                      hbbn
                      last edited by

                      I had same issue for a long time.

                      Then I tried pkg update -f and got an error for SunnyVally repository
                      I figured that I had a old version of zenarmor installed that matches the FreeBSD 14 and not 15.
                      Upgraded the zenarmor to the latest version.

                      Haven't had any of the error messages for some time now. hopefully that was it.

                      Maybe this can be helpfull to someone.

                      1 Reply Last reply Reply Quote 0
                      • J Offline
                        JonnyQuest @JonnyQuest
                        last edited by

                        I did a fresh install of 2.8.0 and do not get the error anymore.

                        C 1 Reply Last reply Reply Quote 1
                        • C Offline
                          Cre8or @JonnyQuest
                          last edited by

                          @JonnyQuest

                          im on 2.8.0 and i also had no problems

                          Shell Output - pkg update -f

                          Updating ntop repository catalogue...
                          Fetching meta.conf: . done
                          Fetching data.pkg: . done
                          Processing entries: . done
                          ntop repository update completed. 6 packages processed.
                          Updating pfSense-core repository catalogue...
                          Fetching meta.conf: . done
                          Fetching data.pkg: . done
                          Processing entries: . done
                          pfSense-core repository update completed. 4 packages processed.
                          Updating pfSense repository catalogue...
                          Fetching meta.conf: . done
                          Fetching data.pkg: ......... done
                          Processing entries: .......... done
                          pfSense repository update completed. 541 packages processed.
                          All repositories are up to date.

                          1 Reply Last reply Reply Quote 1
                          • L Offline
                            lutel
                            last edited by lutel

                            Same problem here, i'm running 2.8.0 updated from 2.7.2. It also takes much longer to login to dashboard than in previous version.

                            1 Reply Last reply Reply Quote 0
                            • S Offline
                              SuperTypeGuy
                              last edited by

                              I am also encountering the (check_upgrade: "Updating repositories metadata" returned error code 1) Upgrade Notice after updating from 2.8.0 => 2.8.1

                              The notice timestamp updates on every reboot even with the dashboard auto-update check disabled. Even if I wait 10 minutes after the reboot before logging into the gui, the notice timestamp is when the system rebooted and not at time of log in.

                              Also, no repository errors when checking from the cli or the System Update gui. Other than the notice message, everything seems fine.

                              S F 2 Replies Last reply Reply Quote 0
                              • stephenw10S Online
                                stephenw10 Netgate Administrator
                                last edited by

                                Yup the check that fails is during boot. The alert should be there however long you wait to login. But, yes, it's just ugly. It shouldn't actually be a problem.

                                1 Reply Last reply Reply Quote 0
                                • S Offline
                                  SuperTypeGuy @SuperTypeGuy
                                  last edited by

                                  fwiw, after checking a few other systems I am seeing this exact notice on several other 2.8.0 systems. Now I am geussing the above system had the notice before upgrading to 2.8.1.

                                  1 Reply Last reply Reply Quote 0
                                  • A Offline
                                    ag0s @stephenw10
                                    last edited by

                                    This post is deleted!
                                    1 Reply Last reply Reply Quote 0
                                    • F Offline
                                      f1d094 @SuperTypeGuy
                                      last edited by

                                      @SuperTypeGuy said in check_upgrade: "Updating repositories metadata" returned error code 1:

                                      Also, no repository errors when checking from the cli or the System Update gui. Other than the notice message, everything seems fine.

                                      Just chiming in. I came here to report this "check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-10-01 17:41:46" which is reported on each boot This was for a new host, installed fresh via USB. The config was then updated from backup of the (failed) host it was replacing.

                                      Everything works...but we get this message on every reboot.

                                      F 1 Reply Last reply Reply Quote 0
                                      • F Offline
                                        f1d094 @f1d094
                                        last edited by f1d094

                                        Point of interest: This may be related to my other issue/unbound. It seems that unbound is taking an inordinately long time to load now on v2.8.1 (1-2 minutes). @Gertjan pointed out that I am running an archaic config with pfBlocker in unbound mode and should update that to "python mode" for speed...

                                        Is there something new with 2.8.2 / unbound / pfBlocker that causes DNS to take too long and therefore isn't available to "pkg update" when it is first run?

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

                                          Hmm, it would certainly hit an error if it's unable to resolve.

                                          Do you have the DNS behaviour set to local DNS only in System > General Setup?

                                          F 1 Reply Last reply Reply Quote 0
                                          • F Offline
                                            f1d094 @stephenw10
                                            last edited by f1d094

                                            @stephenw10 The slow-boot issue I fixed. Not interesting. I fat-fingered an entry in DNS TLS resolver names while working on other issue...

                                            The "check_upgrade" errors on boot persist. However, I've tested every aspect of package management and can identify zero functional issues. Since the firewalls get rebooted on average of once a year, I'll just click "Mark as Read" and call it good. 🕶

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