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

    Errors Updating via Console

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    7 Posts 2 Posters 1.4k 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.
    • P
      Paint
      last edited by

      I am on the latest snapshot and I am getting the following errors when updating via the console. Can you please advise? Thank you

       0) Logout (SSH only)                  9) pfTop
       1) Assign Interfaces                 10) Filter Logs
       2) Set interface(s) IP address       11) Restart webConfigurator
       3) Reset webConfigurator password    12) PHP shell + pfSense tools
       4) Reset to factory defaults         13) Update from console
       5) Reboot system                     14) Disable Secure Shell (sshd)
       6) Halt system                       15) Restore recent configuration
       7) Ping host                         16) Restart PHP-FPM
       8) Shell
      
      Enter an option: 13
      
      >>> Updating repositories metadata...
      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://beta.pfsense.org/packages/pfSense_master_amd64-core/meta.txz: No address record
      repository pfSense-core has no meta file, using default settings
      pkg: https://beta.pfsense.org/packages/pfSense_master_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://beta.pfsense.org/packages/pfSense_master_amd64-pfSense_devel/meta.txz: No address record
      repository pfSense has no meta file, using default settings
      pkg: https://beta.pfsense.org/packages/pfSense_master_amd64-pfSense_devel/packagesite.txz: No address record
      Unable to update repository pfSense
      Error updating repositories!
      

      pfSense i5-4590
      940/880 mbit Fiber Internet from FiOS
      BROCADE ICX6450 48Port L3-Managed Switch w/4x 10GB ports
      Netgear R8000 AP (DD-WRT)

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

        Dns works? Using a dns provider that supports SRV records?

        1 Reply Last reply Reply Quote 0
        • P
          Paint
          last edited by

          @PiBa:

          Dns works? Using a dns provider that supports SRV records?

          yes, no unbound issues. dns is working correctly on my pfSense box and on my LAN.

          No dns forwarder is setup, neither:

          Capture.JPG
          Capture.JPG_thumb

          pfSense i5-4590
          940/880 mbit Fiber Internet from FiOS
          BROCADE ICX6450 48Port L3-Managed Switch w/4x 10GB ports
          Netgear R8000 AP (DD-WRT)

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

            having 127.0.0.1 configured manually looks strange..? And surely wont be reachable over the wan connection.

            Do you allow dhcp to override your dns settings.?. Perhaps try putting 8.8.8.8 in the manual setting.?

            1 Reply Last reply Reply Quote 0
            • P
              Paint
              last edited by

              @PiBa:

              having 127.0.0.1 configured manually looks strange..? And surely wont be reachable over the wan connection.

              Do you allow dhcp to override your dns settings.?. Perhaps try putting 8.8.8.8 in the manual setting.?

              I can dns resolve and ping any other address via console/cli/ssh.

              My pfSense box is running Unbound as my DNS server, so using 127.0.0.1 as a DNS entry is perfectly acceptable.

              Using Google's DNS does not resolve the problem.

              pfSense i5-4590
              940/880 mbit Fiber Internet from FiOS
              BROCADE ICX6450 48Port L3-Managed Switch w/4x 10GB ports
              Netgear R8000 AP (DD-WRT)

              1 Reply Last reply Reply Quote 0
              • P
                Paint
                last edited by

                @PiBa:

                having 127.0.0.1 configured manually looks strange..? And surely wont be reachable over the wan connection.

                Do you allow dhcp to override your dns settings.?. Perhaps try putting 8.8.8.8 in the manual setting.?

                removed the 127.0.0.1 DNS line in my general settings. pfSense defaults to the localhost if nothing is set via the General Settings.

                After reboot, everything is working again. Thanks!

                pfSense i5-4590
                940/880 mbit Fiber Internet from FiOS
                BROCADE ICX6450 48Port L3-Managed Switch w/4x 10GB ports
                Netgear R8000 AP (DD-WRT)

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

                  Yep the system widget will still show 127.0.0.1 as the first dns server, that is perfectly fine. Also when configuring other dns servers in general settings it will still use localhost, its just the manual setting of 127.0.0.1 that seemed strange :) , good its resolved now.  8)

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