Upgrade to 2.4.3_1 Fails at First Attempt
-
From Dashboard-
But try again.
It worked this way on all my installs except one which worked the first time.
-
First try update from 2.4.3 to 2.4.3_1 was OK. Everything is fine, for now, on a Celeron(R) CPU E1200 @ 1.60GHz (don't know the board) on a SSD (don't know the brand, very cheap).
-
I saw the same thing. I navigated away thinking it had stopped. But, a little bit later the box rebooted and it now says it's updated. I don't know what to think.
-
Same thing here. The page reported the upgrade had failed. We waited about two minutes and the page refreshed and we logged in. The upgrade had worked after all.
-
Exact same "problem" here! First "Update failed" but a few moments later pfSense rebootet and update was installed.
-
Same here, but I went back and clicked on update again and it worked.
-
Ditto. Had to click update a second time. (Netgate SG-4860)
-
Does upgrade via console succeeds the first time around?
-
This also happened it said failed going from 2.4.3 - 2.4.3-RELEASE-p1 on the thried line but restarted and said i was on it does this mean it worked or somthing faild to install but the update is there? if the later anyway to get it to redownload and aply the same update just incase.
-
It upgraded OK if it rebooted.
Bug report opened: https://redmine.pfsense.org/issues/8519
Steve
-
I had the same error on my boxes too. I noticed this line in the system log around the time I did the first update:
pkg-static: pfSense-upgrade upgraded: 0.42 -> 0.44It looks like it's doing some minor update to "pfSense-upgrade" the first time.
-
Do a console upgrade (option 13 in the menu) if it's an option for you, it will most likely work a lot better than the WebGUI one. The WebGUI upgrade still seems to suffer from the same problem as it did a while ago which is that it gets disconnected from the real upgrade run and reports a failure when the upgrade is actually running successfully in the background.
-
I waited a day on the upgrade after seeing this thread yesterday afternoon, and just decided to attempt the upgrade to see what would happen. Thankfully, no problems to report here: Upgrade went smoothly (success), system rebooted right away and came up back after couple minutes with 2.4.3_1 loaded.
-
I had the same problem. I tried again, and it didn't give me a failure message, but it appeared to freeze at step 2 of 6, I think one of the extraction steps. After about 15 minutes, I gave up and went back to the main page, it still said I was on 2.4.3, and that the update was available to 2.4.3_1, but the uptime was only 10 minutes, indicating it had rebooted. But when I click on the update again, it tells me I am up to date. Any idea how to make the main page know I am up to date and stop offering me the update?
-
@kpa:
Do a console upgrade (option 13 in the menu) if it's an option for you, it will most likely work a lot better than the WebGUI one. The WebGUI upgrade still seems to suffer from the same problem as it did a while ago which is that it gets disconnected from the real upgrade run and reports a failure when the upgrade is actually running successfully in the background.
This is what I did. I have come to prefer the console update because you get a status as it completes the steps. Better than just getting a timer.
-
Experienced the same w. GUI update.
Seems to hang in updating (Perl i think) - was the latest the GUI showedGot a mail about reboot was complete
22:08:32 Bootup complete
But it still showed that 2.4.3_P1 was an available update.
I did another upgrade via Console
22:15:14 Bootup complete
And after that , it showed i was "Using the latest 2.4.3_P1"
Edit: I came from 2.4.3
/Bingo
-
Just upgraded my 2'nd Box via Console.
All went well at first attempt :)
/Bingo
-
Rerunning the update from the console managed to get the box to 2.4.3_1, and it is no longer saying an update is available but saying it's up to date when you go to install it.
-
Same thing happened to me. It failed on the first attempt. After it rebooted I tried again. It went through the updates, rebooted and then it's all ok. Odd.
Darkk
