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

    check_upgrade (1): unknown error @ 2024-06-07 09:26:39

    Scheduled Pinned Locked Moved
    General pfSense Questions
    8
    30
    771
    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.
    • stephenw10S
      stephenw10 Netgate Administrator
      last edited by

      What are you upgrading from?

      D 1 Reply Last reply Reply Quote 0
      • D
        DominikHoffmann @stephenw10
        last edited by

        @stephenw10 said in check_upgrade (1): unknown error @ 2024-06-07 09:26:39:

        What are you upgrading from?

        Not from anything specific. I just get that same notification that caused @TAC57 to start this thread:

        Screenshot 2024-07-02 at 1.54.03 PM.png

        “check_upgrade (1): unknown error”

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

          @DominikHoffmann said in check_upgrade (1): unknown error @ 2024-06-07 09:26:39:

          Not from anything specific.

          So you've tried upgrading from multiple pfSense versions?

          D 1 Reply Last reply Reply Quote 0
          • D
            DominikHoffmann @stephenw10
            last edited by

            @stephenw10: I am no upgrading at all.

            I am wondering, whether this is something that the pkg_check.php script authored by @luckman212 generates that.

            GertjanG 1 Reply Last reply Reply Quote 0
            • GertjanG
              Gertjan @DominikHoffmann
              last edited by Gertjan

              @DominikHoffmann

              Noop.
              That script doesn't generate of modifies any files. It calls the same php pfSense function 'get_system_pkg_versio()' as the widget on the dashboard.
              And it uses the shell command "/usr/sbin/pkg upgrade -n ..." to enumerate the newer avaible packages, if any exists.
              It doesn't actually change anything.

              I'm using it every day, for years now.
              I have a x86 based 4100 with 24.03.

              edit :

              pkg -d update

              produces a lot of details, but no errors.

              The script file :

              [24.03-RELEASE][root@pfSense.bhf.tld]/root: php -q ./pkg_check.php
pfSense version 24.03_1 (installed) is current

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

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

                Ah nice I didn't think it knew about the recent changes yet. But maybe it doesn't have to.

                1 Reply Last reply Reply Quote 0
                • K
                  KB8DOA
                  last edited by

                  I am having the same problem with a Netgate 5100:

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

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

* Couldn't find host pfsense-plus-pkg00.atx.netgate.com in the .netrc file; using defaults
*   Trying 208.123.73.207:443...
* Connected to pfsense-plus-pkg00.atx.netgate.com (208.123.73.207) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg00.atx.netgate.com
*  start date: Mar 15 20:23:11 2022 GMT
*  expire date: Feb 19 20:23:11 2122 GMT
*  common name: pfsense-plus-pkg00.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_plus-v24_03_amd64-core/meta.conf HTTP/1.1
Host: pfsense-plus-pkg00.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:25:58 GMT

< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 27 Aug 2024 03:18:06 GMT
< Last-Modified: Fri, 19 Apr 2024 01:25:58 GMT
< Connection: keep-alive
< ETag: "6621c826-b2"
<
* Connection #0 to host pfsense-plus-pkg00.atx.netgate.com left intact
DBG(1)[55001]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg
DBG(1)[55001]> curl_open
DBG(1)[55001]> Fetch: fetcher used: pkg+https
DBG(1)[55001]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-core/packagesite.pkg

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

* Couldn't find host pfsense-plus-pkg00.atx.netgate.com in the .netrc file; using defaults
* Found bundle for host: 0x170e7082f7e0 [serially]
* Re-using existing connection with host pfsense-plus-pkg00.atx.netgate.com
> GET /pfSense_plus-v24_03_amd64-core/packagesite.pkg HTTP/1.1
Host: pfsense-plus-pkg00.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Fri, 19 Apr 2024 01:25:58 GMT

< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 27 Aug 2024 03:18:06 GMT
< Last-Modified: Fri, 19 Apr 2024 01:25:58 GMT
< Connection: keep-alive
< ETag: "6621c826-62c"
<
* Connection #0 to host pfsense-plus-pkg00.atx.netgate.com left intact
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
DBG(1)[55001]> PkgRepo: verifying update for pfSense
DBG(1)[55001]> Pkgrepo, begin update of '/var/db/pkg/repo-pfSense.sqlite'
DBG(1)[55001]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf
DBG(1)[55001]> curl_open
DBG(1)[55001]> Fetch: fetcher used: pkg+https
DBG(1)[55001]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf

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

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
*   Trying 208.123.73.209:443...
* Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443
* ALPN: curl offers http/1.1
*  CAfile: /etc/ssl/netgate-ca.pem
*  CApath: /etc/ssl/certs/
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted http/1.1
* Server certificate:
*  subject: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=pfSense Plus; CN=pfsense-plus-pkg01.atx.netgate.com
*  start date: Mar 15 20:23:37 2022 GMT
*  expire date: Feb 19 20:23:37 2122 GMT
*  common name: pfsense-plus-pkg01.atx.netgate.com (matched)
*  issuer: C=US; ST=Texas; L=Austin; O=Rubicon Communications, LLC (Netgate); OU=Netgate CA; CN=Netgate CA
*  SSL certificate verify ok.
* using HTTP/1.1
> GET /pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/meta.conf HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Wed, 21 Aug 2024 15:44:04 GMT

< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 27 Aug 2024 03:18:06 GMT
< Last-Modified: Wed, 21 Aug 2024 15:44:04 GMT
< Connection: keep-alive
< ETag: "66c60b44-b2"
<
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
DBG(1)[55001]> Request to fetch pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg
DBG(1)[55001]> curl_open
DBG(1)[55001]> Fetch: fetcher used: pkg+https
DBG(1)[55001]> curl> fetching https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg

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

* Couldn't find host pfsense-plus-pkg01.atx.netgate.com in the .netrc file; using defaults
* Found bundle for host: 0x170e70917ce0 [serially]
* Re-using existing connection with host pfsense-plus-pkg01.atx.netgate.com
> GET /pfSense_plus-v24_03_amd64-pfSense_plus_v24_03/packagesite.pkg HTTP/1.1
Host: pfsense-plus-pkg01.atx.netgate.com
User-Agent: pkg/1.20.9
Accept: */*
If-Modified-Since: Wed, 21 Aug 2024 15:44:04 GMT

< HTTP/1.1 304 Not Modified
< Server: nginx
< Date: Tue, 27 Aug 2024 03:18:06 GMT
< Last-Modified: Wed, 21 Aug 2024 15:44:04 GMT
< Connection: keep-alive
< ETag: "66c60b44-2ff4c"
<
* Connection #0 to host pfsense-plus-pkg01.atx.netgate.com left intact
pfSense repository is up to date.
All repositories are up to date.
                  GertjanG 1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    What problem? That output shows a normal pkg update check.

                    tinfoilmattT 1 Reply Last reply Reply Quote 0
                    • tinfoilmattT
                      tinfoilmatt @stephenw10
                      last edited by

                      @stephenw10 said in check_upgrade (1): unknown error @ 2024-06-07 09:26:39:

                      What problem? That output shows a normal pkg update check.

                      @KB8DOA, with debug output enabled (i.e. pkg -d update). a more 'normalized' level output:

                      Updating pfSense-core repository catalogue...
* Connected to pfsense-plus-pkg00.atx.netgate.com (208.123.73.207) port 443
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
* Connected to pfsense-plus-pkg01.atx.netgate.com (208.123.73.209) port 443
pfSense repository is up to date.
All repositories are up to date.

                      or just run pkg update without the -d flag.

                      1 Reply Last reply Reply Quote 0
                      • GertjanG
                        Gertjan @KB8DOA
                        last edited by

                        @KB8DOA

                        Don't worry, I somewhat understand what you mean.
                        This :

                        70ce2722-8f49-497a-8cfe-2bea647df2d8-image.png

                        looks alarming because it contain a negation (or something like that, I'm not native ...)
                        Or, it's just an awkward notification.

                        No "help me" PM's please. Use the forum, the community will thank you.
                        Edit : and where are the logs ??

                        1 Reply Last reply Reply Quote 0
                        • H
                          HA4g3n
                          last edited by

                          I get this too, so is this a bug to be fixed or ?

                          GertjanG 1 Reply Last reply Reply Quote 0
                          • GertjanG
                            Gertjan @HA4g3n
                            last edited by

                            @HA4g3n said in check_upgrade (1): unknown error @ 2024-06-07 09:26:39:

                            I get this too, so is this a bug to be fixed or ?

                            The "Couldn't find host pfsense .... in the .netrc file" message ?
                            It's cosmetic. We all see that message. Totally innocent.

                            No "help me" PM's please. Use the forum, the community will thank you.
                            Edit : and where are the logs ??

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

                              Or the check_upgrade (1): unknown error alert? That is already fixed for almost every mode.

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