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

    Package database getting deleted

    Scheduled Pinned Locked Moved pfSense Packages
    8 Posts 3 Posters 1.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.
    • R
      rickym
      last edited by rickym

      pfsense 2.4.4-RELEASE-p1

      I've trying to add any package to my system, but repo-pfSense-core.sqlite and repo-pfSense.sqlite are missing from /var/db/pkg.
      I can get these back by running pkg update -f in the Diagnostics Command Prompt.
      This command does not work in an ssh command prompt or the console command prompt?
      I can even install packages in the Diagnostics Command Prompt, but these aren't available to me in the GUI.

      System/Package Manager/Available Packages is only available when the sqlite files are present. When I try to install a package from here it hangs at Package Installation and says "Please wait while the update system initializes". Both sqlite files are deleted at this point.

      Can anyone help me solve this please?

      Output from trying to run pkg update -f in an ssh command prompt:

      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_4_4_amd64-core/meta.txz: No address record
      repository pfSense-core has no meta file, using default settings
      pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/packagesite.txz: No address record
      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_4_4_amd64-pfSense_v2_4_4/meta.txz: No address record
      repository pfSense has no meta file, using default settings
      pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-pfSense_v2_4_4/packagesite.txz: No address record
      Unable to update repository pfSense
      Error updating repositories!

      Thanks,
      Ricky

      S 1 Reply Last reply Reply Quote 0
      • S
        surinameclubcard @rickym
        last edited by

        @rickym check System>Routing>Gateways. Do you have a default GW configured? I once had the same problem you described. After configuring a default gateway all my troubles went away. Turned out deleted/reconfigured one of my default GWs and consequently I had none left.

        R 1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by Derelict

          DNS issue:

          pkg: https://pkg.pfsense.org/pfSense_v2_4_4_amd64-core/meta.txz: No address record

          Run these at the ssh prompt:

          dig _https._tcp.pkg.pfsense.org SRV
          dig files00.netgate.com A
          dig files01.netgate.com A

          All of those should return something meaningful. (using +short for short responses.)

          [2.4.4-RELEASE][root@fw]/root: dig +short _https._tcp.pkg.pfsense.org SRV
          10 10 443 files00.netgate.com.
          10 10 443 files01.netgate.com.
          [2.4.4-RELEASE][root@fw]/root: dig +short files00.netgate.com A
          162.208.119.41
          [2.4.4-RELEASE][root@fw]/root: dig +short files01.netgate.com A
          162.208.119.40
          

          If those do not work, try these:

          dig @8.8.8.8 _https._tcp.pkg.pfsense.org SRV
          dig @8.8.8.8 files00.netgate.com A
          dig @8.8.8.8 files01.netgate.com A

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 1
          • R
            rickym
            last edited by

            @derelict said in Package database deleting:

            dig +short files01.netgate.com A

            All responses are exactly the same as yours:

            [2.4.4-RELEASE][root@fw-b]/var/db/pkg: dig +short _https._tcp.pkg.pfsense.org SRV
            10 10 443 files01.netgate.com.
            10 10 443 files00.netgate.com.
            [2.4.4-RELEASE][root@fw-b]/var/db/pkg: dig +short files00.netgate.com A
            162.208.119.41
            [2.4.4-RELEASE][root@fw-b]/var/db/pkg: dig +short files01.netgate.com A
            162.208.119.40

            It does seem as if DNS works in all instances except with the package manager though.

            Ricky

            1 Reply Last reply Reply Quote 0
            • R
              rickym @surinameclubcard
              last edited by

              @surinameclubcard

              Tried to delete my gateways and gateway groups.
              Tested with and without recreating my gateway groups but no luck.

              Thanks,
              Ricky

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                When you are in the shell are you root or a different user you created?

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                R 1 Reply Last reply Reply Quote 0
                • R
                  rickym @Derelict
                  last edited by

                  @derelict
                  It's root in both the Diagnostics command prompt and the ssh command prompt, so why the Diagnositcs one works with pgk update -f and the ssh one doesn't really doesn't make sense.

                  thanks,
                  ricky

                  1 Reply Last reply Reply Quote 0
                  • R
                    rickym
                    last edited by

                    My bad.
                    I had a proxy URL configured. Removing it has solved my problem.

                    Thanks for you help everyone.

                    Ricky

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