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

    Unable to retrieve package information after update to 2.3.4

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    6 Posts 4 Posters 5.6k 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.
    • T Offline
      toyinal
      last edited by

      After updating pfsense from 2.3.3 to 2.3.4, everything worked, after a few days, I get the message
      Unable to retrieve package information after update to 2.3.4

      I have trolled the various posts on the forum, no luck, I have re-installed pfsense 2.3.4 still having the same issue

      Typing on the shell,

      pkg update -f
      I get the following errors

      [2.3.4-RELEASE][root@gate.federalpolyilaro.org]/root: pkg update -f
      Updating pfSense-core repository catalogue...
      pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or directory
      pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/meta.txz: Network is unreachable
      repository pfSense-core has no meta file, using default settings
      pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/packagesite.txz: Network is unreachable
      Unable to update repository pfSense-core
      Updating pfSense repository catalogue...
      pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
      pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4/meta.txz: Network is unreachable
      repository pfSense has no meta file, using default settings
      pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4/packagesite.txz: Network is unreachable
      Unable to update repository pfSense
      Error updating repositories!
      
      

      Thanks

      1 Reply Last reply Reply Quote 0
      • P Offline
        PiBa
        last edited by

        pfSense itself has proper internet access i presume? It might be that preferring IPv4 will help. (or disabling IPv6) This can be done from the System/Advanced/Networking screen.

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

          I have the exact same error occurring as toyinal.  I had a drive failure on my old box, so re-installed 2.1.2 (only CD I had on hand without an internet connection) on a new box, restored my old config, then ran the update to get to 2.3.4.  Had no packages installed.  Ran the package update and got the message that it was unable to retrieve package information.

          pkg update -f gives the same results shown by toyinal.

          I have an internet connection, and IPv6 is disabled on both the WAN and LAN interfaces.

          I have read through this post https://forum.pfsense.org/index.php?topic=109690.0 that is frequently referred to, but no solution yet.

          Still looking for help interpreting the output to understand what is going on.

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

            Don't know if this will help the OP, but I systematically rolled back to older backup config.xml files.  I found one from yesterday morning that works for package updates.  Not sure what it is in the config file that would cause this particular issue though.  The only system change that I made between a config that worked and more recent ones that did not work was installing the CRON package.  Before I updated my system from 2.1.2 to 2.3.4 this morning I removed the CRON package.

            I hope someone can explain what might have happened.  I don't want to sidetrack the original thread here, but can someone recommend an easy way to see the differences between config files.  I am new to doing diffs.

            Jeff

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

              Hi
              I have the same problem.
              Any one can help me?
              Thanks

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

                Hey mbi,  I was out of the office for a few days so I have not investigated this fully, but I did find one thing that fixed my issue.  I do not know if it will help your situation, but is something to consider.

                The order of the DNS servers I had listed seemed to create the problem for me (I haven't looked into why yet).

                The following order of DNS servers DID cause this package update issue.
                  internal lan dns server
                  isp dns server 1
                  isp dns server 2
                  google dns server

                The following order immediately resolved the package update issue.
                  isp dns server 1
                  isp dns server 2
                  google dns server
                  internal lan dns server

                So for me, just moving my internal lan dns server to the bottom of the list made the error go away.  I tested this back and forth a couple of times to make sure it was the only change I made to resolve my issue.  As I mentioned, I haven't investigated this further to understand why, and the rest of my configuration may be way different from yours.  But it may give you help.

                Jeff

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