Navigation

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

    Upgrade 2.3.3-RELEASE-p1 to 2.3.4_1-RELEASE-p1 fails

    Installation and Upgrades
    3
    4
    1922
    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.
    • D
      dennix last edited by

      Hey there!

      When trying to upgrade my pfSense 2.3.3 to the latest version the update process fails:

       pfSense-upgrade -c
      >>> Updating repositories metadata... done.
      2.3.4_1 version of pfSense is available
      
      pfSense-upgrade -d
       <snip>pkg: https://pkg.pfsense.org/pfSense_v2_3_4_amd64-core/All/pfSense-rc-2.3.4.txz: Not Found
      >>> Locking package pfSense-kernel-pfSense... done.</snip>
      

      (please see attachments for the full log)

      Doesn't matter if the upgrade is started via GUI, #13 in the menu or directly on the shell, the error is the same.

      Accessing the link via browser didn't work either, that gives a DNS error.
      So I've tried to find a solution in the forum, figuring out that the DNS error is no problem since I can resolve the srv records correctly:

      nslookup -type=srv _https._tcp.pkg.pfsense.org
      Server:         127.0.0.1
      Address:        127.0.0.1#53
      
      Non-authoritative answer:
      _https._tcp.pkg.pfsense.org     service = 10 10 443 files01.netgate.com.
      _https._tcp.pkg.pfsense.org     service = 10 10 443 files00.netgate.com.
      
      

      I've rebooted the router before running the upgrade and package cache seems to be ok:

       pkg clean
      Nothing to do.
      
      

      Any help on further troubleshooting or a solution will be appreciated. :)
      upgrade_log.txt

      pfSense 2.3.3 (nano) amd64

      1 Reply Last reply Reply Quote 0
      • R
        rwieber last edited by

        I had the exact same issue and the following, simple fix resolved it for me:

        https://forum.pfsense.org/index.php?topic=125873.msg695386#msg695386

        1 Reply Last reply Reply Quote 0
        • S
          SteveITS last edited by

          Fixed it for me also.  Looks like it was maybe stuck looking for 2.3.4 and should have been looking for 2.3.4_1?  IIRC older versions would install the upgrade first and then require a second install for the patch…

          Steve

          Only install packages for your version, or risk breaking it. If yours is older, select it in System/Update/Update Settings.
          When upgrading, let it finish. Allow 10 minutes or more depending on packages and device speed.

          1 Reply Last reply Reply Quote 0
          • D
            dennix last edited by

            Thanks rwieber and teamits for taking the time to respond :)
            I tried applying the procedure as described, but it didn't work out.. first.
            Now I tried again and it works just fine. I have no idea why it didn't in the first place, the logs showed exactly as before.

            @teamits:
            the original problem occured on 2.3.3 -> 2.3.4 as well.
            2.3.4_1 came available while I was trying to update to 2.3.4.

            pfSense 2.3.3 (nano) amd64

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