Avoid Update - Version 2.4.5.r.20200203.1429 issue

[bcruze]

@chpalmer said in Version 20200202 issue:

Is this 2.4.5 or 2.5?

Im on

2.5.0-DEVELOPMENT (amd64)
built on Mon Feb 03 01:00:03 EST 2020
FreeBSD 12.0-RELEASE-p10
and
2.4.5-RC (amd64)
built on Sun Feb 02 19:51:43 EST 2020
FreeBSD 11.3-STABLE

on a couple units here in the lab..

no issues.

you have not tried the update from today.

your running a day old release

2.4.5 is what i am talking about. for what its worth i didn't have any packages loaded.... nothing

[Decobus]

@bcruze @chpalmer yeah my update failed with whatever was available as of about 4:50PM EST

[chpalmer]

That would be 20200203..

Version 2.4.5.r.20200203.1429 is available.

So your saying to avoid pushing the update button right now..?? Note to self.. do not update my 2.4.5 box UFN.

[Decobus]

@chpalmer to be fair I didn't super note the version; I can only firmly remember 2020020...

Is there anything I can pull off the other box in rescue more or something that would help?

[chpalmer]

If you would you might change the title of this thread to something that includes the version above. And maybe says "Avoid Update.."

[bcruze]

I would not do the update from three hours ago.. I posted my screenshot in another thread

I won’t get my main router up until tomorrow I’m running on my backup sg 2220

2nd time I’ve been bitten no more development for me again

[chpalmer]

Thanks Decobus.. Hopefully will catch others in time if the issue still persists. Usually the developers know pretty quick themselves.

[Decobus]

I've posted on reddit too to try and warn users there

[IsaacFL]

@Decobus said in Maybe Avoid Update - Version 2.4.5.r.20200203.1429 issue:

I've posted on reddit too to try and warn users there

Thanks, I should have looked here before I hit the update. I have the same problem.

Fortunately I had a VM checkpoint and was able to revert.

[chpalmer]

It appears this is affecting the 2.5 branch as well.. I went ahead and tried to verify and be able to post a warning for it as well.

Thats what test routers here are for though.. :)

Avoid updating either platform.

[artooro]

@Decobus can you fix the spelling of the path so people can easily find it when searching. (it should be .sh not .ah)

[Decobus]

@chpalmer I would run more test VMs but I am sure how to effectively test WAN, since I only have 1 residential connection and don't know what ESXi would do

[Decobus]

@artooro My bad, fixed.

[imaged]

@Decobus Is 2.5 fixed.... I just reinstalled upgraded and am getting the same thing...

[Grapeape22]

login-to-view

[Decobus]

@imaged Doubtful. I am not running a 2.5 box..I don't have a spare WAN connection to use as a test :(

[Grapeape22]

How do I fix this error ?

[Decobus]

I don't know, brought it up over here too: https://forum.netgate.com/topic/150214/avoid-update-version-2-4-5-r-20200203-1429-issue/21

[chpalmer]

Decobus

If you have a spare VM or box you can always plug your WAN of the test box into the LAN of your primary box. Just make sure the WAN and LAN of the test box are in different subnets.

I have to pull my 2.5 box out of the rack and plug a monitor into it to reload or fix. So will do so after one of the devs comes along and says all safe. :)

[chpalmer]

There was movement on the "ramdisk" earlier..

https://redmine.pfsense.org/projects/pfsense/repository/revisions/29aef439c91c5e76e59c1b82b69ec156973caac1