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

    after 22.05 update - still showing as available

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    4 Posts 3 Posters 993 Views
    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.
    • morrealeM
      morreale
      last edited by

      after a successful 22.05 update still showing available (rebooted twice)

      22.05-1.jpg

      22.05-2.jpg

      Release: pfSense 2.3.4 p1(amd64)
      M/B: Supermicro A1SRi-2758F-O
      SSD: 128GB
      RAM: 2x8Gb Kingston 1600MHz DDR3L PC3-12800 ECC
      AP: Cisco

      andrzejlsA 1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        There are a few other threads for this already, but I'll copy this response here again:

        If it still shows that, then part of your upgrade did not complete properly.

        We have seen similar things happen for as few different reasons but no one thing has stood out as being the most common yet and though we've had a handful of reports it still only seems to affect a small number of users total.

        1. Some users have manually defined third party package repositories and some packages in those repositories are outdated or conflict (ntop seems to be a common problem here) -- removing the alternate repositories and re-running the upgrade from the CLI with pfSense-upgrade should fix this.
        2. A package, such as squidGuard, gets hung up during the upgrade and prevents it from fully completing. -- Stopping the package service (e.g. squidGuard) manually from Status > Services should allow the remainder of the upgrade to complete, alternately, from the CLI run killall -9 pkg and see if it continues. Otherwise, reboot and re-run the upgrade from the CLI with pfSense-upgrade.
        3. Systems with multiple disks that had installations on both (e.g. device shipped with MMC but later added an SSD) may be booting from the MMC but upgrading the OS on the SSD. There are a couple different potential methods for working around this but they can be more potentially dangerous, but tl;dr is you need to erase the MMC so the SSD install can work completely.
        4. Something else interrupted the upgrade, such as a user pulling the plug while it was still working because they felt it was taking longer than expected. In this case, re-running the upgrade may help, but a reinstall is better.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        morrealeM 1 Reply Last reply Reply Quote 0
        • andrzejlsA
          andrzejls @morreale
          last edited by

          @morreale run in CLI pfSense-upgrade -d. Worked for me.Screenshot from 2022-06-30 03-51-30.png

          1 Reply Last reply Reply Quote 0
          • morrealeM
            morreale @jimp
            last edited by

            @jimp thanks.

            Release: pfSense 2.3.4 p1(amd64)
            M/B: Supermicro A1SRi-2758F-O
            SSD: 128GB
            RAM: 2x8Gb Kingston 1600MHz DDR3L PC3-12800 ECC
            AP: Cisco

            1 Reply Last reply Reply Quote 0
            • bmeeksB bmeeks referenced this topic on
            • bmeeksB bmeeks referenced this topic on
            • bmeeksB bmeeks referenced this topic on
            • bmeeksB bmeeks referenced this topic on
            • S SteveITS referenced this topic on
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.