2.3.1_1 update?
-
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.
