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

    "System Update Failed" on on my SG-2440 to 2.3.3-RELEASE-p1

    Problems Installing or Upgrading pfSense Software
    5
    7
    1.5k
    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.
    • M
      macboy6
      last edited by

      Got "System Update Failed" on on my SG-2440, but my vm pfsense instance upgraded without error.  See attachment.

      The error reported is not accurate as update was successfully applied and SG-2440 had latest version after it automatically rebooted.
      2.3.3_1_update_error.png
      2.3.3_1_update_error.png_thumb

      1 Reply Last reply Reply Quote 0
      • H
        holmesjrh
        last edited by

        Same here.  Updated a few of our boxes today except my hardware is mostly Intel Atom D525 i386 builds of PfSense.

        As you mentioned all reboot and come back updated to 2.3.3 p1.

        I am upgrading from 2.3.3 and not older versions in all cases.

        1 Reply Last reply Reply Quote 0
        • C
          Chucko
          last edited by

          One more here. Atom D525, Jetway JF99 mobo, embedded installation, upgraded from 2.3.3.

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by

            From the screen shot there is no way to deduce what actually went wrong. I will just say the the GUI is simply monitoring the upgrade log file, displaying it in the text box as it progresses and looking for text at the end of it that indicates it has finished successfully or otherwise. The code for that is making somewhat of an "educated (or not) guess", and stuff can go wrong there with its reporting of what it thinks. But actually the process that is downloading the updates and applying them is still running as a background task, which reboots the system at the appropriate time, and you find that you check back some time later and the upgrade has been successful.

            The various ways that the GUI deduces the upgrade status could be made more robust.

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • I
              InsaneNutter
              last edited by

              I had the same on an SG-4860:

              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 (6 candidates): ...... done
              Processing candidates (6 candidates): ...... done
              The following 6 package(s) will be affected (of 0 checked):

              Installed packages to be UPGRADED:
              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: 6

              41 MiB to be downloaded.
              Fetching pfSense-rc-2.3.3_1.txz: . done
              Fetching pfSense-kernel-pfSense-2.3.3_1.txz:

              I got an "System update failed!" message after this.

              However the update continued in the background, rebooted and everything appears ok though.

              1 Reply Last reply Reply Quote 0
              • P
                phil.davis
                last edited by

                Just started the upgrade from 2.3.3 to 2.3.3-p1 on my little Alix. It quickly told me "System update failed". But clearly from the "top" display, it is happily doing the duplicate slice step (with "dd" running):

                last pid: 43455;  load averages:  2.52,  1.61,  1.00      up 17+10:14:28  17:15:48
53 processes:  1 running, 50 sleeping, 2 zombie
CPU:  0.8% user,  0.0% nice,  4.9% system, 79.7% interrupt, 14.7% idle
Mem: 9604K Active, 107M Inact, 84M Wired, 18M Buf, 19M Free
Swap:

  PID USERNAME    THR PRI NICE   SIZE    RES STATE    TIME    WCPU COMMAND
88179 root          1  20    0  9964K  1640K physrd   0:01   0.29% dd
43455 root          1  21    0 11260K  2428K RUN      0:00   0.20% top
86318 root          1  52   20 10460K  2120K wait     9:31   0.00% sh
95708 nobody        1  20    0 11340K  3912K select   7:19   0.00% dnsmasq
91008 root          1  20    0 24996K 18692K select   6:15   0.00% bsnmpd
43932 root          1  20    0 13400K 13432K select   5:27   0.00% ntpd
75715 root          1  20    0 10148K  1904K select   5:15   0.00% syslogd
  594 root          5  20    0 10632K  1888K accept   5:04   0.00% dpinger
28709 root          1  20    0 10236K  1968K bpf      4:12   0.00% filterlog
85074 root          1  20    0 12640K  4444K select   3:21   0.00% openvpn
 6783 dhcpd         1  20    0 16372K  9532K select   3:17   0.00% dhcpd
20985 root          1  20    0 12700K  4368K select   2:27   0.00% hostapd
41768 root          1  20    0 23924K  5616K kqread   2:01   0.00% nginx
40741 root          9  20    0 11304K  2684K uwait    1:55   0.00% filterdns
24035 root          1  20    0 12700K  4352K select   1:44   0.00% hostapd
79448 root          1  20    0 12640K  4476K select   1:32   0.00% openvpn

                The code that tries to guess what is going on with the upgrade clearly has no brain.

                SystemUpdateFailed.png
                SystemUpdateFailed.png_thumb

                As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

                1 Reply Last reply Reply Quote 0
                • H
                  holmesjrh
                  last edited by

                  Did another round of updates this morning.

                  D2500 Atom w/ AMD64 build had no issues.

                  Remaining 3 systems were all D525 i386 builds and all had the issue.

                  All were 2.3.3 to 2.3.3 p1 upgrades through gui.

                  Update: Confirmed occured on AMD 64 Intel Atom D525.

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