2.3.2-p1 "Unable to check for updates"/"Unable to retrieve package information"



  • Hello,

    My configuration is 2.3.2-RELEASE-p1 (amd64)  updated from previous version: 2.3.2-RELEASE (amd64)
    As in topic https://forum.pfsense.org/index.php?topic=116223.0 it is impossible for me to update, or install package.

    Suggestions in the referenced topic do not work.

    The 2 solution proposed do not work:
    Option 13 in console leave on :

    "Updating pfSense-core repository catalogue…"

    and "pkg update; pkg upgrade pkg" leave on:

    "Updating pfSense-core repository catalogue…"

    In the two mode, nothing append ...

    Any idea ?

    Regards,
    Lucky



  • I'm seeing this…

    Number of packages to be upgraded: 4

    38 MiB to be downloaded.
    Fetching pfSense-rc-2.3.2_1.txz: . done
    Fetching pfSense-kernel-pfSense_wrap-2.3.2_1.txz: .......... done
    Fetching pfSense-default-config-serial-2.3.2_1.txz: . done
    Fetching pfSense-base-nanobsd-2.3.2_1.txz: ....... done
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/All/pfSense-base-nanobsd-2.3.2_1.txz: Operation timed out

    Locking package pfSense-kernel-pfSense_wrap... done.
    Failed



  • I have this:

    Number of packages to be upgraded: 42

    40 MiB to be downloaded.
    Fetching pfSense-base-2.3.2_1.txz: …. done
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/All/pfSense-base-2.3.2_1.txz: Operation timed out

    Locking package pfSense-kernel-pfSense... done.
    Failed

    But i can fetch https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/All/pfSense-base-2.3.2_1.txz with the browser.

    Rgds
    AW



  • I'm just now getting this error.  2.3.2-p1 Release.

    I was doing just fine until I installed an OpenVPN client connection to PIA-Texas.  Disabling the VPN client doesn't work.  Rebooting doesn't work.  Literally everything has been fine until I configured the OpenVPN client and then added the "OpenVPN" widget to the dashboard.

    • The dashboard can no longer check for updates:  "Unable to check for updates"
    • The dashboard "Installed Packages" widget shows:  "No packages installed. Packages can be installed here."
    • System –> Package Manager --> Installed Packages shows:  "Unable to retrieve package information."
    • System --> Package Manager --> Available Packages shows:  "Unable to retrieve package information."

  • Netgate

    Sounds like you must have screwed up your policy routing, NAT, or DNS when you installed your PIA config.

    ETA: Yeah, maybe not.



  • The same problem here.

    Updated to 2.3.2-p1 yesterday. Everything seemed to be OK after update. Today it is "Unable to check for updates". "pkg update" returns Internal Server Error.



  • yap, me to
    is it my config or something general?



  • Same for me. Yesterday all was fine and today "Unable to check for updates". Nothing changed on my machine since the update 4 days ago.



  • :-\

    Enter an option: 13

    Updating repositories metadata…
    Updating pfSense-core repository catalogue...
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/meta.txz: Internal Server Error
    repository pfSense-core has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/packagesite.txz: Internal Server Error
    Unable to update repository pfSense-core
    Updating pfSense repository catalogue...
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/meta.txz: Internal Server Error
    repository pfSense has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/packagesite.txz: Internal Server Error
    Unable to update repository pfSense
    *** Welcome to pfSense 2.3.2-RELEASE-p1 (amd64 full-install) on pfSense ***



  • Same issue here.
    And it's not related to network connectivity:

    Over IPv6:

    [2.3.2-RELEASE][admin@suzet.pbnet.local]/root: ping6 updates.pfsense.org
    PING6(56=40+8+8 bytes) 2a02:2f0b:405f:ffff::xxx:xxx –> 2610:1c1:3::116
    16 bytes from 2610:1c1:3::116, icmp_seq=0 hlim=53 time=133.635 ms
    16 bytes from 2610:1c1:3::116, icmp_seq=1 hlim=53 time=133.795 ms
    16 bytes from 2610:1c1:3::116, icmp_seq=2 hlim=53 time=134.242 ms
    16 bytes from 2610:1c1:3::116, icmp_seq=3 hlim=53 time=134.292 ms
    16 bytes from 2610:1c1:3::116, icmp_seq=4 hlim=53 time=133.872 ms
    16 bytes from 2610:1c1:3::116, icmp_seq=5 hlim=53 time=133.942 ms
    16 bytes from 2610:1c1:3::116, icmp_seq=6 hlim=53 time=133.517 ms
    16 bytes from 2610:1c1:3::116, icmp_seq=7 hlim=53 time=133.201 ms
    ^C
    --- updates.pfsense.org ping6 statistics ---
    8 packets transmitted, 8 packets received, 0.0% packet loss
    round-trip min/avg/max/std-dev = 133.201/133.812/134.292/0.341 ms

    Over IPv4:

    [2.3.2-RELEASE][admin@suzet.pbnet.local]/root: ping updates.pfsense.org
    PING updates.pfsense.org (162.208.119.39): 56 data bytes
    64 bytes from 162.208.119.39: icmp_seq=0 ttl=51 time=119.279 ms
    64 bytes from 162.208.119.39: icmp_seq=1 ttl=51 time=119.327 ms
    64 bytes from 162.208.119.39: icmp_seq=2 ttl=51 time=118.236 ms
    64 bytes from 162.208.119.39: icmp_seq=3 ttl=51 time=118.892 ms
    ^C
    –- updates.pfsense.org ping statistics ---
    5 packets transmitted, 4 packets received, 20.0% packet loss
    round-trip min/avg/max/stddev = 118.236/118.933/119.327/0.437 ms

    Does anyone have any clue on how to solve this ?



  • I've also done a fiddler trace on one of the URLs Jon Posted:

    [REQUEST]
    GET https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/All/pfSense-base-2.3.2_1.txz HTTP/1.1
    Accept: text/html, application/xhtml+xml, /
    Accept-Language: en-US
    User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
    Accept-Encoding: gzip, deflate
    Host: pkg.pfsense.org
    DNT: 1
    Connection: Keep-Alive

    [RESPONSE]
    HTTP/1.1 500 Internal Server Error
    Server: nginx/1.11.3
    Date: Tue, 18 Oct 2016 07:01:22 GMT
    Content-Type: text/html
    Content-Length: 193
    Connection: close

    <title>500 Internal Server Error</title>

    <center>

    500 Internal Server Error

    </center>


    <center>nginx/1.11.3</center>

    And on another URL (32-bit package it seems), we get:

    [REQUEST]
    GET https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/All/pfSense-base-nanobsd-2.3.2_1.txz HTTP/1.1
    Accept: text/html, application/xhtml+xml, /
    Accept-Language: en-US
    User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko
    Accept-Encoding: gzip, deflate
    Host: pkg.pfsense.org
    DNT: 1
    Connection: Keep-Alive

    [RESPONSE]
    HTTP/1.1 504 Fiddler - Receive Failure
    Date: Tue, 18 Oct 2016 07:03:33 GMT
    Content-Type: text/html; charset=UTF-8
    Connection: close
    Cache-Control: no-cache, must-revalidate
    Timestamp: 10:03:33.765

    [Fiddler] ReadResponse() failed: The server did not return a complete response for this request. Server returned 0 bytes.



  • Same here:

    
    Updating pfSense-core repository catalogue...
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/meta.txz: Internal Server Error
    repository pfSense-core has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/packagesite.txz: Internal Server Error
    Unable to update repository pfSense-core
    Updating pfSense repository catalogue...
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/meta.txz: Internal Server Error
    repository pfSense has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/packagesite.txz: Internal Server Error
    Unable to update repository pfSense
    


  • Same here, it seems pfSense's servers are problematic?

    Enter an option: 13
    
    >>> Updating repositories metadata... 
    Updating pfSense-core repository catalogue...
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/meta.txz: Internal Server Error
    repository pfSense-core has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/packagesite.txz: Internal Server Error
    Unable to update repository pfSense-core
    Updating pfSense repository catalogue...
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/meta.txz: Internal Server Error
    repository pfSense has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/packagesite.txz: Internal Server Error
    Unable to update repository pfSense
    *** Welcome to pfSense 2.3.2-RELEASE-p1 (amd64 full-install) on pfSense ***
    
    


  • I also get on my older system (2.2.4) the dashboard reporting:

    	2.2.4-RELEASE (amd64) 
    built on Sat Jul 25 19:57:37 CDT 2015 
    FreeBSD 10.1-RELEASE-p15
    
    Unable to check for updates.
    


  • Same error on my sistem, but sunday it was working I checked and it show me that a new version was available.
    so to me seem to a problem that start today and I had done no chenge to my installation.
    :)



  • @lannet2k:

    Same error on my sistem, but sunday it was working I checked and it show me that a new version was available.
    so to me seem to a problem that start today and I had done no chenge to my installation.
    :)

    Exact same issues! It was working two days back but not today.. AFAIK, the only configuration I did on pfsense was enabling squid (transparent) + squidguard.



  • It looks like it was fixed. Update checking/upgrade both work for me right now.



  • yep seems okey now


  • Netgate Administrator

    Yes, it should be working fine now.
    It appears there was an issue with the pkg servers which has now been resolved.

    Steve



  • Still not working for me.  It wasn't last night, and still not today.

    Updating repositories metadata…
    Updating pfSense-core repository catalogue...
    pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-core/meta.txz: Network is unreachable
    repository pfSense-core has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-core/packagesite.txz: Network is unreachable
    Unable to update repository pfSense-core
    Updating pfSense repository catalogue...
    pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/meta.txz: Network is unreachable
    repository pfSense has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/packagesite.txz: Network is unreachable
    Unable to update repository pfSense
    Failed



  • It must have been something with the pfsense servers, I was having the same issue, and it is working fine this morning



  • Just to update.  I rebooted my pfsense box and then tried the update.  It works now.



  • seems to be working yes… thanks for the update..!


 

© Copyright 2002 - 2018 Rubicon Communications, LLC | Privacy Policy