2.3.1_1 update?
-
On the system dashboard for my SG units, it is showing "Version 2.3.1_1 is available." However, when I click on the update link, the system update page says 2.3.1 is "Up to date." Is there a 2.3.1_1 update?
-
Same for me. Won't let me update. Says I'm up to date.
-
-
not done yet.
-
Soon
-
Should be all in place now. Double checking everything. Announcement to come shortly.
-
Reboot required with this one?
@cmb:
Should be all in place now. Double checking everything. Announcement to come shortly.
-
-
-
hitting the upgrade button before reading the official release announcement is bad form.
(it's also a bad meme)
-
here you go.
read the release note.
the update just went smooth from my side
https://redmine.pfsense.org/projects/pfsense/roadmap -
Dude, no. Clicking on a link to see information on an upgrade is not bad form.
There was no upgrade button to click on, which is what triggered the original question.
hitting the upgrade button before reading the official release announcement is bad form.
-
Y U NO READ THE RELEASE NOTES?!
test box that lives on the wild side. ;)
-
Dude, no. Clicking on a link to see information on an upgrade is not bad form.
There was no upgrade button to click on, which is what triggered the original question.
hitting the upgrade button before reading the official release announcement is bad form.
ah, I misunderstood what button you hit.
-
There is a bit of a Catch-22 in production releases. The release person needs to put all the release kits (patches, packages…) onto the live release servers and give it a bit of a test from some online systems, to double-check that all the needed release components are found in the right places.
During that time, there is a live release available online, but no release announcement (and maybe no release notes).A workflow that helps could be:
- Post the release notes
- Post a notification that a release is in the process of being released, and for users not to upgrade just yet
- Put all the live release materials on the various server(s)
- Test some upgrades from the release server(s)
- Change the notification to say that the release is officially available
-
The first update (2.3_1) that pfSense offered didn't require a reboot and didn't mention anything about uninstalling packages first, etc. Does update 2.3.1_1 require us to uninistall packages first before updating to it? Or, is that just best practice for a new pfSense release (2.3.1)?
-
However, when I click on the update link
Y U NO READ THE RELEASE NOTES?!
Hey, leave Denny alone! :D
-
There is a bit of a Catch-22 in production releases. The release person needs to put all the release kits (patches, packages…) onto the live release servers and give it a bit of a test from some online systems, to double-check that all the needed release components are found in the right places.
There was a gap of about a half hour or so from the update showing available to all the platforms having all their files in place (most considerably less than that). The reason is the automatic copy from staging to production didn't completely work, so some of it had to be done manually. Since part of it did succeed, the version notification came up, but then it wasn't actually available to install yet. We already know what the issue is, should have it fixed tomorrow so that delay between showing the version available and it actually being available won't happen in the future.
-
Can someone confirm whether or not this update requires a reboot? Many people have asked, yet no official answer has been given. Thanks!
EDIT: I took one for the team. A REBOOT IS REQUIRED. The kernel gets upgraded.
-
I've installed this update today. I don't think it rebooted (unless it was automatic, I was away while it was upgrading), however the entire OS started behaving REALLY weird. My internet connection just stopped working for no reason, and I couldn't find a reason why. I've reset the system to factory settings, but like 2 hours later I could no access webconfigurator without an SSH tunnel (connection times out)
Maybe it's just me, but I'm really confused as to what's going on.
-
On the system dashboard for my SG units, it is showing "Version 2.3.1_1 is available." However, when I click on the update link, the system update page says 2.3.1 is "Up to date." Is there a 2.3.1_1 update?
I still have this problem on one pfSense box as of now. Will not let me update. Second pfSense box updated just fine. :o
-
@cmb:
However, when I click on the update link
Y U NO READ THE RELEASE NOTES?!
Hey, leave Denny alone! :D
I was just tryin to have a little fun. I'll go sit back in my corner :P
-
Reboot makes no difference for me. I'm also not sure why people are talking as if its the users fault for not reading a release note?
My simple mind has this weird idea that if my system shows "update available" and I press the button to update, something should happen. (in a perfect world)Not the case here. I'm not running any packages on this machine other than openvpn and watchdog. Its a simple box.
Version 2.3.1-RELEASE (amd64)
built on Tue May 17 18:46:53 CDT 2016
FreeBSD 10.3-RELEASE-p3Version 2.3.1_1 is available.
when trying to actually update, you get:
Current Base System
2.3.1
Latest Base System
2.3.1
Status
Up to date.Now, to my thinking something isn't quite right in this process.
Its either not updating as it should, or there is no update actually available or the update message is misleading to us dumb guys. -
Can someone confirm whether or not this update requires a reboot? Many people have asked, yet no official answer has been given. Thanks!
EDIT: I took one for the team. A REBOOT IS REQUIRED. The kernel gets upgraded.
It's mentioned in the blog post: https://blog.pfsense.org/?p=2068
That's the "official" place for release announcements and trickles down from there into the wiki and redmine logs.
-
I did mention that I rebooted right? 3x now (just to be sure). Does it need to be physically unplugged or kicked or something also?
-
Might be something with cache? I believe cmb commented on something similar here: https://www.reddit.com/r/PFSENSE/comments/4l28xy/dashboard_shows_update_available_but_system/d3jsotv?context=3
-
Not any cache problem I can figure out. I even tried it on a separate browser I never use for anything (should not have anything pfsense related in cache)
Could it be because my box is using IPV6 vs. IPV4 or something?
Its really not the end of the world because I can manually update from a file I download any time I like. Its just an annoyance thats all.
EDIT: Maybe I can't just update from a file the way I used to. Looks like the option has been eliminated in 2.3?
-
Strange. Did a moderator put a thank you in for me?
-
EDIT: Maybe I can't just update from a file the way I used to. Looks like the option has been eliminated in 2.3?
Does console option 13 work?
-
Didn't even look at console - I did go back and read the notes again for 2.3 and it says that files like that will be kept online for before 2.3 but not after 2.3
Anyway - Not a big deal for me right now. So long as 2.3.2 will update properly when its available I won't worry much about the _1s and _2s etc.
-
Okay, now you're just having fun with me…
:)
-
haha. I thought you were so I was just playing along. AFAIK, admins can't do anything "as a user".
-
Didn't even look at console - I did go back and read the notes again for 2.3 and it says that files like that will be kept online for before 2.3 but not after 2.3
Anyway - Not a big deal for me right now. So long as 2.3.2 will update properly when its available I won't worry much about the _1s and _2s etc.
Anything that would make it not upgrade to an update version will affect maintenance release versions as well. Try option 13 at the console, what's that do?
-
It updated. And thats nice and all - but…. So, why was that necessary? Any idea?
-
It updated. And thats nice and all - but…. So, why was that necessary? Any idea?
That runs effectively the same command, I was expecting it'd spit out something useful as to what the issue was.
You keep the console log by chance? Or if you can send me a copy of /conf/upgrade_log.txt that will hopefully show something useful.
-
Nope - Nothing. No messages. Just worked. Very strange.
I tried to update a dozen times after several days and several reboots and immediately before updating from console also - same result…
Updated with option 13 at console and it just updated with no fuss.
The reason I don't tend to get into the console on this machine much is because its very far away. Don't want to break it playing.
Anyway - Thanks for the tip. Worked fine. Hope I don't have to do that every time.
-
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: 2.3.1 -> 2.3.1_1 [pfSense]3 KiB to be downloaded.
**** WARNING ****
Reboot will be required!!
Proceed with upgrade? (y/N) >>> 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 (1 candidates): . done
Processing candidates (1 candidates): . done
The following 1 package(s) will be affected (of 0 checked):Installed packages to be UPGRADED:
pfSense: 2.3.1 -> 2.3.1_1 [pfSense]3 KiB to be downloaded.
Fetching pfSense-2.3.1_1.txz: . done
Checking integrity… done (0 conflicting)
Upgrade is complete. Rebooting in 10 seconds.Locking package pfSense-kernel-pfSense... done.
Upgrading necessary packages...
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):Installed packages to be UPGRADED:
pfSense: 2.3.1 -> 2.3.1_1 [pfSense]
[1/1] Upgrading pfSense from 2.3.1 to 2.3.1_1…
[1/1] Extracting pfSense-2.3.1_1: …. doneRemoving unnecessary packages... done.
Cleanup pkg cache... done.
