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.
    • 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 Offline
              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 Offline
                        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
                          • stephenw10S Offline
                            stephenw10 Netgate Administrator
                            last edited by

                            Just for reference do you have DNS set to local only or can it fall back to external?

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