Discussion:
[pfSense] Upgrades to 2.4.3.x failing after updating metadata
Steve Yates
2018-05-16 02:53:49 UTC
Permalink
I upgraded two routers from 2.4.2 to 2.4.3 and today to 2.4.3_1. One is an SG-3100 and one is a PC. On both, both times, the upgrade almost immediately fails, but if I try again it works. I click the pending-update icon on the dashboard to go to System Update and it detects the update. I start and I get:

">>> Updating repositories metadata... done.
2.4.3_1 version of pfSense is available"

Then a red bar at the top of the page, "System update failed!"

If I click the already-highlighted System Update tab again, confirm the update, it then immediately installs.

Is anyone else seeing this?

--

Steve Yates
ITS, Inc.
John Kline
2018-05-16 03:28:38 UTC
Permalink
Many of us a e seeing this.
See:https://forum.pfsense.org/index.php?topic=147853.0 




On Tuesday, May 15, 2018, 7:53 PM, Steve Yates <***@teamITS.com> wrote:

I upgraded two routers from 2.4.2 to 2.4.3 and today to 2.4.3_1.  One is an SG-3100 and one is a PC.  On both, both times, the upgrade almost immediately fails, but if I try again it works.  I click the pending-update icon on the dashboard to go to System Update and it detects the update.  I start and I get:

">>> Updating repositories metadata... done.
2.4.3_1 version of pfSense is available"

Then a red bar at the top of the page, "System update failed!"

If I click the already-highlighted System Update tab again, confirm the update, it then immediately installs.

Is anyone else seeing this?

--

Steve Yates
ITS, Inc.

_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
Vick Khera
2018-05-16 12:23:29 UTC
Permalink
I just did the upgrade from the console from 2.4.3 to 2.4.3_1 with no
problems in the upgrade. I run on an official pfSense brand C2758 device.
Post by John Kline
Many of us a e seeing this.
See:https://forum.pfsense.org/index.php?topic=147853.0
I upgraded two routers from 2.4.2 to 2.4.3 and today to 2.4.3_1. One is
an SG-3100 and one is a PC. On both, both times, the upgrade almost
immediately fails, but if I try again it works. I click the pending-update
icon on the dashboard to go to System Update and it detects the update. I
">>> Updating repositories metadata... done.
2.4.3_1 version of pfSense is available"
Then a red bar at the top of the page, "System update failed!"
If I click the already-highlighted System Update tab again, confirm the
update, it then immediately installs.
Is anyone else seeing this?
--
Steve Yates
ITS, Inc.
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
Steve Yates
2018-05-16 14:13:53 UTC
Permalink
Huh, I should remember to look there first. So used to this list. 😊

The "sort of scary" part is comments like "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." Like it's running in the background despite the failure? And I ran it a second time during this? That's what "KPA" posted last night: "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."
--
Steve Yates
ITS, Inc.

-----Original Message-----
From: List <list-***@lists.pfsense.org> On Behalf Of John Kline
Sent: Tuesday, May 15, 2018 10:29 PM
To: pfSense Support and Discussion Mailing List <***@lists.pfsense.org>
Subject: Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

Many of us a e seeing this.
See:https://forum.pfsense.org/index.php?topic=147853.0 




On Tuesday, May 15, 2018, 7:53 PM, Steve Yates <***@teamITS.com> wrote:

I upgraded two routers from 2.4.2 to 2.4.3 and today to 2.4.3_1.  One is an SG-3100 and one is a PC.  On both, both times, the upgrade almost immediately fails, but if I try again it works.  I click the pending-update icon on the dashboard to go to System Update and it detects the update.  I start and I get:

">>> Updating repositories metadata... done.
2.4.3_1 version of pfSense is available"

Then a red bar at the top of the page, "System update failed!"

If I click the already-highlighted System Update tab again, confirm the update, it then immediately installs.

Is anyone else seeing this?
--
Steve Yates
ITS, Inc.

_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold



_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
WebDawg
2018-05-16 14:50:09 UTC
Permalink
I upgrade via the console now. Not to say that the GUI is broken, but
I must have been a victim of when it was. I have seen what kpa is
talking about in that forum thread too. It is why I always ssh in and
update from console.
Post by Steve Yates
Huh, I should remember to look there first. So used to this list. 😊
The "sort of scary" part is comments like "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." Like it's running in the background despite the failure? And I ran it a second time during this? That's what "KPA" posted last night: "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."
--
Steve Yates
ITS, Inc.
-----Original Message-----
Sent: Tuesday, May 15, 2018 10:29 PM
Subject: Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata
Many of us a e seeing this.
See:https://forum.pfsense.org/index.php?topic=147853.0
">>> Updating repositories metadata... done.
2.4.3_1 version of pfSense is available"
Then a red bar at the top of the page, "System update failed!"
If I click the already-highlighted System Update tab again, confirm the update, it then immediately installs.
Is anyone else seeing this?
--
Steve Yates
ITS, Inc.
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
Steve Yates
2018-05-16 15:47:58 UTC
Permalink
I've used the console in the recent past...there was something around the 2.3.3 upgrade where you had to switch it to the development branch and back again to get it to work: https://forum.pfsense.org/index.php?topic=125873.msg695386#msg695386

Overall seems like the GUI should work...
--
Steve Yates
ITS, Inc.

-----Original Message-----
From: List <list-***@lists.pfsense.org> On Behalf Of WebDawg
Sent: Wednesday, May 16, 2018 9:50 AM
To: pfSense Support and Discussion Mailing List <***@lists.pfsense.org>
Subject: Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

I upgrade via the console now. Not to say that the GUI is broken, but
I must have been a victim of when it was. I have seen what kpa is
talking about in that forum thread too. It is why I always ssh in and
update from console.
Post by Steve Yates
Huh, I should remember to look there first. So used to this list. 😊
The "sort of scary" part is comments like "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." Like it's running in the background despite the failure? And I ran it a second time during this? That's what "KPA" posted last night: "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."
--
Steve Yates
ITS, Inc.
-----Original Message-----
Sent: Tuesday, May 15, 2018 10:29 PM
Subject: Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata
Many of us a e seeing this.
See:https://forum.pfsense.org/index.php?topic=147853.0
">>> Updating repositories metadata... done.
2.4.3_1 version of pfSense is available"
Then a red bar at the top of the page, "System update failed!"
If I click the already-highlighted System Update tab again, confirm the update, it then immediately installs.
Is anyone else seeing this?
--
Steve Yates
ITS, Inc.
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
Vick Khera
2018-05-16 16:20:09 UTC
Permalink
Post by WebDawg
I upgrade via the console now. Not to say that the GUI is broken, but
I must have been a victim of when it was. I have seen what kpa is
talking about in that forum thread too. It is why I always ssh in and
update from console.
Wow. I call that a high risk upgrade method. Once it logs you out of ssh,
you just sit there and hope it comes back up. You need to hook your serial
port (or virtual serial port if you have a BMC that supports that) up as
the real device console so you can monitor the entire process.

Loading...