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

    Unable to check for updates from dashboard

    Scheduled Pinned Locked Moved General pfSense Questions
    51 Posts 7 Posters 12.5k 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.
    • N
      Nibblet @stephenw10
      last edited by Nibblet

      @stephenw10 Really weirdly, it has all started working again. Nothing changed from the perspective of DNS/proxy settings - very strange.

      Also, running the update -d command would have worked, except of course that these servers were already updated..

      Of note - these are in production with around 40-50 people actively connecting through them so I REALLY don't like running arbitrary commands that update packages. Hopefully this will put to bed that whatever pkg (and pkg-static) and the 'check of updates' widget are doing is different, and the widget is not calling the pkg (or pkg-static) command but rather doing its own thing - do you know where the source code for this widget would be? is there a specific package I can look the sources up for?

      DBG(1)[33734]> pkg initialized
      Updating pfSense-core repository catalogue...
      DBG(1)[33734]> PkgRepo: verifying update for pfSense-core
      DBG(1)[33734]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
      DBG(1)[33734]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/meta.conf
      DBG(1)[33734]> opening libfetch fetcher
      DBG(1)[33734]> Fetch > libfetch: connecting
      DBG(1)[33734]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/meta.conf with opts "i"
      DBG(1)[33734]> Fetch: fetcher chosen: https
      DBG(1)[33734]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/packagesite.pkg
      DBG(1)[33734]> opening libfetch fetcher
      DBG(1)[33734]> Fetch > libfetch: connecting
      DBG(1)[33734]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/packagesite.pkg with opts "i"
      DBG(1)[33734]> Fetch: fetcher chosen: https
      DBG(1)[33734]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core/packagesite.txz
      DBG(1)[33734]> opening libfetch fetcher
      DBG(1)[33734]> Fetch > libfetch: connecting
      DBG(1)[33734]> Fetch: fetching from: https://pkg01-atx.netgate.com/pfSense_v2_7_0_amd64-core/packagesite.txz with opts "i"
      DBG(1)[33734]> Fetch: fetcher chosen: https
      pfSense-core repository is up to date.
      Updating pfSense repository catalogue...
      DBG(1)[33734]> PkgRepo: verifying update for pfSense
      DBG(1)[33734]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
      DBG(1)[33734]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/meta.conf
      DBG(1)[33734]> opening libfetch fetcher
      DBG(1)[33734]> Fetch > libfetch: connecting
      DBG(1)[33734]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/meta.conf with opts "i"
      DBG(1)[33734]> Fetch: fetcher chosen: https
      DBG(1)[33734]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.pkg
      DBG(1)[33734]> opening libfetch fetcher
      DBG(1)[33734]> Fetch > libfetch: connecting
      DBG(1)[33734]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.pkg with opts "i"
      DBG(1)[33734]> Fetch: fetcher chosen: https
      DBG(1)[33734]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz
      DBG(1)[33734]> opening libfetch fetcher
      DBG(1)[33734]> Fetch > libfetch: connecting
      DBG(1)[33734]> Fetch: fetching from: https://pkg00-atx.netgate.com/pfSense_v2_7_0_amd64-pfSense_v2_7_0/packagesite.txz with opts "i"
      DBG(1)[33734]> Fetch: fetcher chosen: https
      pfSense repository is up to date.
      All repositories are up to date.

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

        Huh, weird.

        The pkg update command only updates the local cached list against the repo. pkg upgrade is required to actually upgrade anything. pkg update gets run every time it checks so everytime you visit the dashboard for example. It is generally safe to run.

        Anyway glad you're back up and running.

        1 Reply Last reply Reply Quote 0
        • W
          walidbz
          last edited by

          i run pfsense 2.7.0 and i want to upgrade pkg from 1.19.1 to 1.20.6 but an error occurs :
          ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"
          if anyone knows how can i fix this please help me .
          thank you

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

            You have to use pkg-static if you are already using a newer version of pkg. But in 2.7 you should be running 1.19.1_2 unless you had the dev branch set at some point.

            Steve

            W 1 Reply Last reply Reply Quote 0
            • W
              walidbz @stephenw10
              last edited by

              @stephenw10 thank you
              But i did not undrestand what i am supposed to do !!

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

                If you have a newer version of pkg installed than the base you have to use pkg-static instead of pkg.

                So for example:

                [2.7.0-RELEASE][admin@pfsense.fire.box]/root: pkg-static info -x pkg
                pfSense-pkg-Shellcmd-1.0.5_3
                pfSense-pkg-Status_Traffic_Totals-2.3.2_3
                pfSense-pkg-System_Patches-2.2.4
                pfSense-pkg-iperf-3.0.3
                pfSense-pkg-nmap-1.4.4_7
                pfSense-pkg-openvpn-client-export-1.9
                pkg-1.19.1_2
                

                But as you can see there you should have pkg version 1.19.1_2 in 2.7. Why are you trying to install 1.20.6? What version do you have now?

                W 1 Reply Last reply Reply Quote 0
                • W
                  walidbz @stephenw10
                  last edited by

                  @stephenw10 you are right i have pkg 1.19.1_2 .
                  i want to install wazuh-agent 4.5.0 and when i run pkg-static install wazuh-agent-4.5.0 , this is what i have :
                  Sans titre.png
                  Sans titre2.png

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

                    Where are you installing that from? That's not the CE pkg repo so it;s pulling in some unknown version of pkg.

                    W 2 Replies Last reply Reply Quote 0
                    • W
                      walidbz @stephenw10
                      last edited by

                      @stephenw10 i want to install wazuh-agent on my psfense VMware virtual machine
                      pfsense 2.7.0 release
                      freeBSD 14

                      1 Reply Last reply Reply Quote 0
                      • W
                        walidbz @stephenw10
                        last edited by

                        @stephenw10 now i got this
                        Sans titre3.png

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

                          Where are you installing that from?

                          What version of pkg do you have now?

                          If you have installed a new version of pkg that the running base/kernel you must use pkg-static instead of pkg. So:

                          pkg-static update
                          

                          However if you have changed the update repo to point at something else then it could have pulled in other packages. pfSense has a number of custom pkgs that are required for correct running.

                          W 2 Replies Last reply Reply Quote 0
                          • W
                            walidbz @stephenw10
                            last edited by

                            @stephenw10 the version of pkg is 1.19.1_2

                            1 Reply Last reply Reply Quote 0
                            • W
                              walidbz @stephenw10
                              last edited by

                              @stephenw10 i install from : https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core
                              this is the url mentionned in pfsense.conf

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

                                @walidbz said in Unable to check for updates from dashboard:

                                i install from : https://pkg.pfsense.org/pfSense_v2_7_0_amd64-core

                                That isn't where you're installing from. Neither wazuh-agent nor pkg-1.20.6 are in that repo.

                                Also if you have pkg-1.19.1_2 installed you would not need to run pkg-static:

                                [2.7.0-RELEASE][admin@pfsense.fire.box]/root: pkg search wazuh-agent
                                [2.7.0-RELEASE][admin@pfsense.fire.box]/root:
                                

                                What repo do you see in?: pkg-static -d update
                                What version do you in? :pkg-static info pkg

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