Pfsense 2.3.4 doesn't find 2.4.0 upgrade



  • Hi,

    one of my pfsense boxes (2.3.4-RELEASE (amd64)) doesn't find the 2.4.0 upgrade.

    System/ Update / System Update:
    Current Base System 2.3.4           
    Latest Base System 2.3.4
    Status Up to date.

    System/ Update / Update Settings:
    Branch Stable (Default)

    Here's what pfSense-upgrade -d logs:

    
    >>> 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://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/meta.txz: No address record
    repository pfSense-core has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_3_4_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://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4/meta.txz: No address record
    repository pfSense has no meta file, using default settings
    pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-pfSense_v2_3_4/packagesite.txz: No address record
    Unable to update repository pfSense
    Error updating repositories!
    
    

    I've already scp'd the particular files from another machine to this one, without any success.

    Any idea how to get the 2.4.0 release?

    Best regards
    Thomas


  • Rebel Alliance Developer Netgate

    Is there anything between this firewall and the Internet? It's saying that it can't perform a DNS lookup, which could be a failure directly or maybe if there is something in between intercepting DNS or a proxy of some kind.

    The pkg.pfsense.org DNS records are SRV records, so you can try to look them up from the command line. pkg does not use A/AAAA records, so a normal DNS lookup won't find anything.

    $ host -t srv _https._tcp.pkg.pfsense.org
    _https._tcp.pkg.pfsense.org has SRV record 10 10 443 files00.netgate.com.
    _https._tcp.pkg.pfsense.org has SRV record 10 10 443 files01.netgate.com.
    $ host files01.netgate.com.
    files01.netgate.com has address 162.208.119.40
    files01.netgate.com has IPv6 address 2610:1c1:0:6::40
    $ host files00.netgate.com.
    files00.netgate.com has address 162.208.119.41
    files00.netgate.com has IPv6 address 2610:1c1:0:6::41
    
    

    If your upstream DNS server blocks SRV lookups for some braindead reason, it would fail. Or if you're set for forwarding mode and none of the forwarders respond, that would give the same kind of error.



  • Hi jimp,

    thank you very much for the hint! I've no idea how this could have happened, but somehow, the Gateway assigned to DNS-Server had emptied.

    The host-commands you suggested are all working now. However, still no luck: Pfsense won't find the update.

    Best regards
    Thomas



  • Any idea how to get the 2.4.0 release?

    Download it and do a fresh and full installation then play back the config backup. if you are not really
    trusting all this points, fell free to take a second HDD/SDD or mSATA/M.2 solution if you have it lying around.
    The you will be able to see what is going on and you will be able to see if it is working without any pain don´t to
    be able to settle back fast if needed. Only change the BIOS boot order and all will be able to try out.



  • Hi, I had the same problem with one of our servers. Since I disabled "DNS forwarder" and enabled "DNS resolver" the server find the version 2.4.1 for update.



  • Unfortunately switching DNS forwarder/resolver didn't work for me. 2.4 release still doesn't show up, although it did offer the 2.3.4_1 upgrade.



  • So, apply https://forum.pfsense.org/index.php?topic=138656.msg761867#msg761867  (first line) to have a fast, positive result ;)


Log in to reply