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

    package issues after upgrading hardware

    General pfSense Questions
    2
    10
    161
    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
      ncage
      last edited by

      So i just upgrade my hardware. I backed up current setup (had to change interface names in the xml file) & then applied it to my new hardware. Everything worked "except", i noticed i had a couple external services that weren't starting up:
      ccef5a28-5db3-4929-8638-1cb145789d4b-image.png

      I thought no problem i'll just go download those packages manually & this is what i'm getting:
      8f9a4cb1-fac8-4309-9a3c-b822810ce2b8-image.png

      I've been googling around & trying a bunch of different things to get this corrected & I haven't found anything that works yet. I have rebooted too. Any recommendations on where to go from here?

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

        Are you running Plus?

        If so then your NDI will probably have changed and you will have to migrate or renew it.

        Send me your NDI in chat and I can check it.

        Steve

        N 1 Reply Last reply Reply Quote 0
        • N
          ncage @stephenw10
          last edited by

          @stephenw10 said in package issues after upgrading hardware:

          Are you running Plus?

          If so then your NDI will probably have changed and you will have to migrate or renew it.

          Send me your NDI in chat and I can check it.

          Steve

          Unfortunately no i'm running the community edition. Does that still apply?

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

            No, in CE a change to the NDI should be no problem.

            Try running at the CLI: pkg-static -d update
            See what errors it returns.

            N 1 Reply Last reply Reply Quote 0
            • N
              ncage @stephenw10
              last edited by

              @stephenw10 said in package issues after upgrading hardware:

              pkg-static -d update

              I appreciate your help. Anyways here is what happens:

              DBG(1)[90297]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[90297]> PkgRepo: verifying update for pfSense-core
DBG(1)[90297]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[90297]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf
DBG(1)[90297]> curl_open
DBG(1)[90297]> Fetch: fetcher used: pkg+https
DBG(1)[90297]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf

DBG(1)[90297]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults
*   Trying [2610:160:11:18::209]:443...
* Connected to pkg01-atx.netgate.com (2610:160:11:18::209) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 28 00:00:00 2024 GMT
*  expire date: Apr 28 23:59:59 2025 GMT
*  subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-core/meta.conf HTTP/1.1
Host: pkg01-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Wed, 06 Dec 2023 21:23:59 GMT

< HTTP/1.1 200 OK
Fetching meta.conf: < Server: nginx
< Date: Tue, 11 Jun 2024 15:51:57 GMT
< Content-Type: application/octet-stream
< Content-Length: 163
< Last-Modified: Wed, 06 Dec 2023 21:23:58 GMT
< Connection: keep-alive
< ETag: "6570e66e-a3"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
<
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

DBG(1)[90297]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/packagesite.pkg
DBG(1)[90297]> curl_open
DBG(1)[90297]> Fetch: fetcher used: pkg+https
DBG(1)[90297]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/packagesite.pkg

DBG(1)[90297]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg01-atx.netgate.com in the .netrc file; using defaults
* Hostname pkg01-atx.netgate.com was found in DNS cache
*   Trying [2610:160:11:18::209]:443...
* Connected to pkg01-atx.netgate.com (2610:160:11:18::209) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 28 00:00:00 2024 GMT
*  expire date: Apr 28 23:59:59 2025 GMT
*  subjectAltName: host "pkg01-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-core/packagesite.pkg HTTP/1.1
Host: pkg01-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Wed, 06 Dec 2023 21:23:59 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg: < Server: nginx
< Date: Tue, 11 Jun 2024 15:51:58 GMT
< Content-Type: application/octet-stream
< Content-Length: 1496
< Last-Modified: Wed, 06 Dec 2023 21:23:59 GMT
< Connection: keep-alive
< ETag: "6570e66f-5d8"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
<
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[90297]> PkgRepo: verifying update for pfSense
DBG(1)[90297]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[90297]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf
DBG(1)[90297]> curl_open
DBG(1)[90297]> Fetch: fetcher used: pkg+https
DBG(1)[90297]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf

DBG(1)[90297]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults
*   Trying [2610:160:11:18::207]:443...
* Connected to pkg00-atx.netgate.com (2610:160:11:18::207) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 28 00:00:00 2024 GMT
*  expire date: Apr 28 23:59:59 2025 GMT
*  subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf HTTP/1.1
Host: pkg00-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Mon, 13 May 2024 19:08:35 GMT

< HTTP/1.1 200 OK
Fetching meta.conf: < Server: nginx
< Date: Tue, 11 Jun 2024 15:51:58 GMT
< Content-Type: application/octet-stream
< Content-Length: 178
< Last-Modified: Mon, 13 May 2024 19:08:35 GMT
< Connection: keep-alive
< ETag: "66426533-b2"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
<
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

DBG(1)[90297]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg
DBG(1)[90297]> curl_open
DBG(1)[90297]> Fetch: fetcher used: pkg+https
DBG(1)[90297]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg

DBG(1)[90297]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults
* Hostname pkg00-atx.netgate.com was found in DNS cache
*   Trying [2610:160:11:18::207]:443...
* Connected to pkg00-atx.netgate.com (2610:160:11:18::207) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 28 00:00:00 2024 GMT
*  expire date: Apr 28 23:59:59 2025 GMT
*  subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg HTTP/1.1
Host: pkg00-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Mon, 13 May 2024 19:08:35 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg: < Server: nginx
< Date: Tue, 11 Jun 2024 15:51:58 GMT
< Content-Type: application/octet-stream
< Content-Length: 160360
< Last-Modified: Mon, 13 May 2024 19:08:35 GMT
< Connection: keep-alive
< ETag: "66426533-27268"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
<
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

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

                Hmm well that looks OK.

                Try running: pkg-static -d upgrade
                See if it offers you any upgraded packages. You might see upgraded Unbound and curl packages if you have been on 2.7.2 for a while. Those are OK to upgrade.

                N 1 Reply Last reply Reply Quote 0
                • N
                  ncage @stephenw10
                  last edited by

                  @stephenw10 said in package issues after upgrading hardware:

                  pkg-static -d upgrade

                  Thanks a bunch that fixed it. Here is the log:

                  DBG(1)[67917]> pkg initialized
Updating pfSense-core repository catalogue...
DBG(1)[67917]> PkgRepo: verifying update for pfSense-core
DBG(1)[67917]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense-core.sqlite'
DBG(1)[67917]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf
DBG(1)[67917]> curl_open
DBG(1)[67917]> Fetch: fetcher used: pkg+https
DBG(1)[67917]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/meta.conf

DBG(1)[67917]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults
*   Trying [2610:160:11:18::207]:443...
* Connected to pkg00-atx.netgate.com (2610:160:11:18::207) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 28 00:00:00 2024 GMT
*  expire date: Apr 28 23:59:59 2025 GMT
*  subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-core/meta.conf HTTP/1.1
Host: pkg00-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Wed, 06 Dec 2023 21:23:59 GMT

< HTTP/1.1 200 OK
Fetching meta.conf: < Server: nginx
< Date: Tue, 11 Jun 2024 16:05:42 GMT
< Content-Type: application/octet-stream
< Content-Length: 163
< Last-Modified: Wed, 06 Dec 2023 21:23:58 GMT
< Connection: keep-alive
< ETag: "6570e66e-a3"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
<
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

DBG(1)[67917]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/packagesite.pkg
DBG(1)[67917]> curl_open
DBG(1)[67917]> Fetch: fetcher used: pkg+https
DBG(1)[67917]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-core/packagesite.pkg

DBG(1)[67917]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults
* Hostname pkg00-atx.netgate.com was found in DNS cache
*   Trying [2610:160:11:18::207]:443...
* Connected to pkg00-atx.netgate.com (2610:160:11:18::207) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 28 00:00:00 2024 GMT
*  expire date: Apr 28 23:59:59 2025 GMT
*  subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-core/packagesite.pkg HTTP/1.1
Host: pkg00-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Wed, 06 Dec 2023 21:23:59 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg: < Server: nginx
< Date: Tue, 11 Jun 2024 16:05:43 GMT
< Content-Type: application/octet-stream
< Content-Length: 1496
< Last-Modified: Wed, 06 Dec 2023 21:23:59 GMT
< Connection: keep-alive
< ETag: "6570e66f-5d8"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
<
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[67917]> PkgRepo: verifying update for pfSense
DBG(1)[67917]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[67917]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf
DBG(1)[67917]> curl_open
DBG(1)[67917]> Fetch: fetcher used: pkg+https
DBG(1)[67917]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf

DBG(1)[67917]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults
*   Trying [2610:160:11:18::207]:443...
* Connected to pkg00-atx.netgate.com (2610:160:11:18::207) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 28 00:00:00 2024 GMT
*  expire date: Apr 28 23:59:59 2025 GMT
*  subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-pfSense_v2_7_2/meta.conf HTTP/1.1
Host: pkg00-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Mon, 13 May 2024 19:08:35 GMT

< HTTP/1.1 200 OK
Fetching meta.conf: < Server: nginx
< Date: Tue, 11 Jun 2024 16:05:43 GMT
< Content-Type: application/octet-stream
< Content-Length: 178
< Last-Modified: Mon, 13 May 2024 19:08:35 GMT
< Connection: keep-alive
< ETag: "66426533-b2"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
<
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

DBG(1)[67917]> Request to fetch pkg+https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg
DBG(1)[67917]> curl_open
DBG(1)[67917]> Fetch: fetcher used: pkg+https
DBG(1)[67917]> curl> fetching https://pkg.pfsense.org/pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg

DBG(1)[67917]> CURL> attempting to fetch from , left retry 3

* Couldn't find host pkg00-atx.netgate.com in the .netrc file; using defaults
* Hostname pkg00-atx.netgate.com was found in DNS cache
*   Trying [2610:160:11:18::207]:443...
* Connected to pkg00-atx.netgate.com (2610:160:11:18::207) port 443
* ALPN: curl offers http/1.1
*  CAfile: none
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: CN=*.netgate.com
*  start date: Mar 28 00:00:00 2024 GMT
*  expire date: Apr 28 23:59:59 2025 GMT
*  subjectAltName: host "pkg00-atx.netgate.com" matched cert's "*.netgate.com"
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_v2_7_2_amd64-pfSense_v2_7_2/packagesite.pkg HTTP/1.1
Host: pkg00-atx.netgate.com
User-Agent: pkg/1.20.8
Accept: */*
If-Modified-Since: Mon, 13 May 2024 19:08:35 GMT

< HTTP/1.1 200 OK
Fetching packagesite.pkg: < Server: nginx
< Date: Tue, 11 Jun 2024 16:05:43 GMT
< Content-Type: application/octet-stream
< Content-Length: 160360
< Last-Modified: Mon, 13 May 2024 19:08:35 GMT
< Connection: keep-alive
< ETag: "66426533-27268"
< Strict-Transport-Security: max-age=31536000; preload
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< X-Robots-Tag: all
< X-Download-Options: noopen
< X-Permitted-Cross-Domain-Policies: none
< Accept-Ranges: bytes
<
* The requested document is not new enough
* Simulate an HTTP 304 response
* Closing connection

pfSense repository is up to date.
All repositories are up to date.
DBG(1)[67917]> want to get an advisory lock on a database
Checking for upgrades (84 candidates): .......... done
Processing candidates (84 candidates): .......... done
The following 93 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	boost-libs: 1.83.0 [pfSense]
	cpu-microcode-amd: 20230808 [pfSense]
	cpu-microcode-intel: 20230808 [pfSense]
	cpu-microcode-rc: 1.0 [pfSense]
	dhcpcd: 10.0.3 [pfSense]
	dhcpleases6: 0.1_3 [pfSense]
	kea: 2.4.0_1 [pfSense]
	log4cplus: 2.1.0 [pfSense]
	pfSense-composer-deps: 0.1 [pfSense]

Installed packages to be UPGRADED:
	bind-tools: 9.18.14 -> 9.18.19 [pfSense]
	ca_root_nss: 3.89.1 -> 3.93_2 [pfSense]
	curl: 8.1.0 -> 8.6.0 [pfSense]
	cyrus-sasl: 2.1.28 -> 2.1.28_1 [pfSense]
	dbus: 1.14.6,1 -> 1.14.10,1 [pfSense]
	devcpu-data: 20230513 -> 20230617_1 [pfSense]
	drm-510-kmod: 5.10.163_7 -> 5.10.163_8 [pfSense]
	filterlog: 0.1_9 -> 0.1_10 [pfSense]
	gettext-runtime: 0.21.1 -> 0.22_1 [pfSense]
	glib: 2.76.2,2 -> 2.78.0,2 [pfSense]
	gmp: 6.2.1 -> 6.3.0 [pfSense]
	hostapd: 2.10_5 -> 2.10_8 [pfSense]
	icu: 73.1,1 -> 73.2,1 [pfSense]
	isc-dhcp44-relay: 4.4.3P1 -> 4.4.3P1_4 [pfSense]
	isc-dhcp44-server: 4.4.3P1 -> 4.4.3P1_4 [pfSense]
	json-c: 0.16 -> 0.17 [pfSense]
	libedit: 3.1.20221030,1 -> 3.1.20230828,1 [pfSense]
	libgcrypt: 1.9.4_1 -> 1.10.2 [pfSense]
	libnghttp2: 1.52.0 -> 1.57.0 [pfSense]
	libssh2: 1.10.0_1,3 -> 1.11.0_1,3 [pfSense]
	libuv: 1.45.0 -> 1.46.0 [pfSense]
	libxml2: 2.10.4 -> 2.10.4_1 [pfSense]
	links: 2.29,1 -> 2.29_2,1 [pfSense]
	lua-resty-core: 0.1.26 -> 0.1.27 [pfSense]
	luajit-openresty: 2.1.20230410 -> 2.1.20230911_1 [pfSense]
	miniupnpd: 2.3.3,1 -> 2.3.3_1,1 [pfSense]
	mobile-broadband-provider-info: 20221107 -> 20230416 [pfSense]
	nginx: 1.24.0_6,3 -> 1.24.0_12,3 [pfSense]
	ntp: 4.2.8p15_5 -> 4.2.8p17_1 [pfSense]
	openldap26-client: 2.6.4 -> 2.6.6 [pfSense]
	openvpn: 2.6.4 -> 2.6.8_1 [pfSense]
	pcsc-lite: 1.9.9,2 -> 2.0.0,2 [pfSense]
	perl5: 5.32.1_3 -> 5.34.1_3 [pfSense]
	pfSense: 2.7.0 -> 2.7.2 [pfSense]
	pfSense-base: 2.7.0 -> 2.7.2 [pfSense-core]
	pfSense-boot: 2.7.0 -> 2.7.2 [pfSense-core]
	pfSense-default-config: 2.7.0 -> 2.7.2 [pfSense]
	pfSense-kernel-pfSense: 2.7.0 -> 2.7.2 [pfSense-core]
	pfSense-repo: 2.7.0 -> 2.7.2 [pfSense]
	pfSense-repoc: 20230616 -> 20230912 [pfSense]
	pfSense-upgrade: 1.0_33 -> 1.2.1 [pfSense]
	pftop: 0.8_2 -> 0.8_4 [pfSense]
	php82: 8.2.6 -> 8.2.11 [pfSense]
	php82-bcmath: 8.2.6 -> 8.2.11 [pfSense]
	php82-bz2: 8.2.6 -> 8.2.11 [pfSense]
	php82-ctype: 8.2.6 -> 8.2.11 [pfSense]
	php82-curl: 8.2.6 -> 8.2.11 [pfSense]
	php82-dom: 8.2.6 -> 8.2.11 [pfSense]
	php82-filter: 8.2.6 -> 8.2.11 [pfSense]
	php82-gettext: 8.2.6 -> 8.2.11 [pfSense]
	php82-gmp: 8.2.6 -> 8.2.11 [pfSense]
	php82-intl: 8.2.6 -> 8.2.11 [pfSense]
	php82-ldap: 8.2.6 -> 8.2.11 [pfSense]
	php82-mbstring: 8.2.6 -> 8.2.11 [pfSense]
	php82-opcache: 8.2.6 -> 8.2.11 [pfSense]
	php82-openssl_x509_crl: 1.3_2 -> 1.3_3 [pfSense]
	php82-pcntl: 8.2.6 -> 8.2.11 [pfSense]
	php82-pdo: 8.2.6 -> 8.2.11 [pfSense]
	php82-pdo_sqlite: 8.2.6 -> 8.2.11 [pfSense]
	php82-pear-Mail: 1.4.1,1 -> 1.5.1,1 [pfSense]
	php82-posix: 8.2.6 -> 8.2.11 [pfSense]
	php82-readline: 8.2.6 -> 8.2.11 [pfSense]
	php82-session: 8.2.6 -> 8.2.11 [pfSense]
	php82-shmop: 8.2.6 -> 8.2.11 [pfSense]
	php82-simplexml: 8.2.6 -> 8.2.11 [pfSense]
	php82-sockets: 8.2.6 -> 8.2.11 [pfSense]
	php82-sqlite3: 8.2.6 -> 8.2.11 [pfSense]
	php82-sysvmsg: 8.2.6 -> 8.2.11 [pfSense]
	php82-sysvsem: 8.2.6 -> 8.2.11 [pfSense]
	php82-sysvshm: 8.2.6 -> 8.2.11 [pfSense]
	php82-tokenizer: 8.2.6 -> 8.2.11 [pfSense]
	php82-xml: 8.2.6 -> 8.2.11 [pfSense]
	php82-xmlreader: 8.2.6 -> 8.2.11 [pfSense]
	php82-xmlwriter: 8.2.6 -> 8.2.11 [pfSense]
	php82-zlib: 8.2.6 -> 8.2.11 [pfSense]
	python311: 3.11.3 -> 3.11.6 [pfSense]
	smartmontools: 7.3 -> 7.4 [pfSense]
	sqlite3: 3.41.2,1 -> 3.43.1,1 [pfSense]
	strongswan: 5.9.10_2 -> 5.9.11_3 [pfSense]
	unbound: 1.17.1_3 -> 1.19.1 [pfSense]
	voucher: 0.1_2 -> 0.1_3 [pfSense]
	wpa_supplicant: 2.10_6 -> 2.10_9 [pfSense]
	zstd: 1.5.4_2 -> 1.5.5 [pfSense]

Installed packages to be REINSTALLED:
	rrdtool-1.8.0_2 [pfSense] (direct dependency changed: perl5)

Number of packages to be installed: 9
Number of packages to be upgraded: 83
Number of packages to be reinstalled: 1

The process will require 392 MiB more space.
297 MiB to be downloaded.

Proceed with this action? [y/N]: DBG(1)[67917]> release an advisory lock on a database

                  Question since this didn't work when i restored from backup do i need to do anything other than manually downloading the packages?

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

                    Oh OK it's because you're running 2.7.0 and just looking at 2.7.2 to upgrade.

                    Do you see the upgrade available now?

                    If not run: certctl rehash

                    N 1 Reply Last reply Reply Quote 0
                    • N
                      ncage @stephenw10
                      last edited by

                      @stephenw10 said in package issues after upgrading hardware:

                      Oh OK it's because you're running 2.7.0 and just looking at 2.7.2 to upgrade.

                      Do you see the upgrade available now?

                      If not run: certctl rehash

                      yes sir & updated. So i just need to download the packages & the settings should be there?

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

                        When you restore the config if should pull in any packages that were installed as long as it has access to the repo.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post