Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    [solved] pfSense + 25.07.1 check_upgrade: "Updating repositories metadata" returned error code 1 @ 2025-12-10 07:23:47

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    29 Posts 4 Posters 3.5k Views 4 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.
    • luckman212L Offline
      luckman212 LAYER 8 @Gertjan
      last edited by luckman212

      Well, in my case:

      • I do use IPv6 (but via an HENET GIF tunnel, since my ISP does not provide native v6)
      • I do have "Prefer to use IPv4 even if IPv6 is available" checked
      • I do have System Patches installed, and all recommended patches applied
      • I don't use Service Watchdog
      • I do get this error message on every boot

      edit: I've been poking around in /usr/local/libexec/pfSense-upgrade and I think I know what's going on now. Will post back shortly.

      1 Reply Last reply Reply Quote 0
      • luckman212L Offline
        luckman212 LAYER 8 @stephenw10
        last edited by

        Well,
        After messing around a bit thinking this was an IPv6 problem (it wasn't) I'm still puzzled.

        Still getting this on each boot:

        5b8b5bc9-3ecb-4d89-b83e-1cbd168f0cd8-image.png

        This is on a fully patched 25.11 with System Patches 2.2.26 + all patches applied:

        07e98bba-ac16-4427-9dd1-f70293e29b79-image.png

        I note that after a reboot, the config.xml has this earlyshellcmd removed:

        <earlyshellcmd>/usr/local/bin/php-cgi -f /usr/local/bin/apply_patches.php</earlyshellcmd>
        

        4e6d87c5-d15e-40cc-80ef-3e822404daf0-image.png

        Is that normal/expected?

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

          Yes that's generated by the system patches package if you have any applied patches to auto-reapply any that are set to do so.

          luckman212L 1 Reply Last reply Reply Quote 0
          • luckman212L Offline
            luckman212 LAYER 8 @stephenw10
            last edited by

            @stephenw10 Ok, so it's normal for that shellcmd to be removed even though I have System Patches installed and in use?

            GertjanG 1 Reply Last reply Reply Quote 0
            • GertjanG Offline
              Gertjan @luckman212
              last edited by

              @luckman212
              You mean you haven't
              d17857b6-c6c1-4c54-bfb9-3865e48d6ff1-image.png

              right now ?
              That's doesn't seem normal to me.
              If the System patcher package is installed, in put this in (the GUI part of the config file shown above) place :

              5199a86e-05b0-4300-8d84-87e928010cd3-image.png

              No "help me" PM's please. Use the forum, the community will thank you.

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

                Hmm, yeah, I wouldn't expect it to be removed. 🤔

                Are you seeing it added and removed repeatedly?

                luckman212L 1 Reply Last reply Reply Quote 0
                • luckman212L Offline
                  luckman212 LAYER 8 @stephenw10
                  last edited by

                  @stephenw10 Yes, correct. If I go to Packages and click reinstall on System Patches, I can see that the apply_patches.php earlyshellcmd gets (re)added. BUT, on my next reboot, it gets removed again.

                  GertjanG 1 Reply Last reply Reply Quote 0
                  • GertjanG Offline
                    Gertjan @luckman212
                    last edited by

                    @luckman212

                    Euh .... you have a patch that does this ? ;)

                    The only place where the "earlyshellcmd" gets removed is ( see /usr/local/pkg/systempatches.xml )

                    I image, if for some reason the current "config.xml" gets discarded by pfSense because it found an issue with it, it takes the previous config.xml - the one where "Patches" packages wasn't installed (yet), so it uninstall's it ? (?!) ( I know, a wild shot).
                    pfSense uninstalling packages without user GUI interaction, that's wild.

                    No "help me" PM's please. Use the forum, the community will thank you.

                    luckman212L 1 Reply Last reply Reply Quote 0
                    • luckman212L Offline
                      luckman212 LAYER 8 @Gertjan
                      last edited by

                      Looking at my config.xml backups, I noticed that around 2025-07-20 the following node "disappeared" and is no longer found in any subsequent backups:

                      <shellcmdsettings>
                      	<config>
                      		<cmd>/usr/local/bin/php-cgi -f /usr/local/bin/apply_patches.php</cmd>
                      		<cmdtype>earlyshellcmd</cmdtype>
                      		<description><![CDATA[System Patches default earlyshellcmd. DO NOT EDIT/DELETE!]]></description>
                      	</config>
                      </shellcmdsettings>
                      

                      Comparing the XML, it seems to be when the base pfSense on this unit was upgraded from config ver 22.7 (pfSense 22.05.1) to 24.0 (25.07 probably beta/rc at that time). Not sure if that's a clue or not.

                      luckman212L 1 Reply Last reply Reply Quote 0
                      • luckman212L Offline
                        luckman212 LAYER 8 @luckman212
                        last edited by luckman212

                        This appears to be a rare bug. What I did to "fix" it:

                        1. hand edit config.xml to remove references to the apply_patches.php earlyshellcmd
                        2. rm /tmp/config.cache
                        3. manually added back the following shellcmd definition:

                        34166ad8-59ec-4e94-b31d-25e6cca71c1b-image.png

                        After that, everything seems to be kosher and is surviving reboots.

                        7cbbb35c-bd97-432f-83c0-a57c671d862a-CleanShot 2025-12-22 at 08.56.11.png

                        Now back to the original bug reported in this thread which is still occurring...

                        61039688-c833-42a3-acab-9da205dc5de2-image.png

                        1 Reply Last reply Reply Quote 1
                        • luckman212L luckman212 referenced this topic on
                        • First post
                          Last post
                        Copyright 2026 Rubicon Communications LLC (Netgate). All rights reserved.