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

    2.3.3 to 2.3.3_1: "System update failed!"

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    6 Posts 2 Posters 1.8k 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.
    • S
      seanmcb
      last edited by

      Hi all,

      I tried to update from 2.3.3 to 2.3.3_1 and the output was:

      –----------------

      Updating repositories metadata... done.
      Unlocking package pfSense-kernel-pfSense... done.
      2.3.3_1 version of pfSense is available
      Downloading upgrade packages...
      Updating pfSense-core repository catalogue...
      pfSense-core repository is up-to-date.
      Updating pfSense repository catalogue...
      pfSense repository is up-to-date.
      All repositories are up-to-date.
      Checking for upgrades (7 candidates): ....... done
      Processing candidates (7 candidates): ....... done
      The following 7 package(s) will be affected (of 0 checked):

      Installed packages to be UPGRADED:
      pfSense-upgrade: 0.17 -> 0.20 [pfSense]
      pfSense-rc: 2.3.3 -> 2.3.3_1 [pfSense-core]
      pfSense-kernel-pfSense: 2.3.3 -> 2.3.3_1 [pfSense-core]
      pfSense-default-config-serial: 2.3.3 -> 2.3.3_1 [pfSense-core]
      pfSense-base: 2.3.3 -> 2.3.3_1 [pfSense-core]
      pfSense: 2.3.3 -> 2.3.3_1 [pfSense]
      curl: 7.52.1_1 -> 7.53.0 [pfSense]

      Number of packages to be upgraded: 7

      41 MiB to be downloaded.
      Fetching pfSense-upgrade-0.20.txz: .. done
      Fetching pfSense-rc-2.3.3_1.txz: . done
      Fetching pfSense-kernel-pfSense-2.3.3_1.txz: …....... done
      Fetching pfSense-default-config-serial-2.3.3_1.txz: . done
      Fetching pfSense-base-2.3.3_1.txz: .....

      At which point higher up on the screen it said "System update failed!":

      I rebooted, and it now says I'm at 2.3.3_1 but I fear it's only half upgraded or something…

      What should I do?

      Thanks,

      Sean
      2.3.3_1.png_thumb
      2.3.3_1.png

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Use the console upgrade (#13) to at least get some more reliable info. (The upgrade process itself is still a steaming pile of sh*t).

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

          Thanks.  I tried, and it outputs:

          –----------------------

          Updating repositories metadata...
          Updating pfSense-core repository catalogue...
          pfSense-core repository is up-to-date.
          Updating pfSense repository catalogue...
          pfSense repository is up-to-date.
          All repositories are up-to-date.
          Unlocking package pfSense-kernel-pfSense... done.
          The following 1 package(s) will be affected (of 0 checked):

          Installed packages to be UPGRADED:
          pfSense-upgrade: 0.20 -> 0.21 [pfSense]

          Number of packages to be upgraded: 1

          11 KiB to be downloaded.

          **** WARNING ****
          Reboot will be required!!
          Proceed with upgrade? (y/N)
          –----------------------

          What is this telling me?  Should I already be at pfSense-upgrade 0.21 from the partially failed 2.3.3_1 upgrade?

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            Just let it upgrade the package and reboot.

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

              It succeeded, and now says packages are up to date.  Does that mean it's reasonably certain that I'm now fully on 2.3.3_1?

              1 Reply Last reply Reply Quote 0
              • D
                doktornotor Banned
                last edited by

                Should be fine, yes.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.