Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
-
One bug I'm getting, I did that and was able to upgrade to 2.3-Release.
On the dashboard page it shows 2.3-RELEASE (amd64) The system is on a later version than the official release.
It doesn't show the update available button, but when I go to the System > Update it shows,
Current Base System 2.3.1.a.20160412.1112
Latest Base System 2.3
and has the update button, I click it but get,
pfSense repository is up-to-date.
All repositories are up-to-date.
Your packages are up to date
SuccessSo I guess it's just reading the current base system incorrectly? No biggie just throwing that out there.
-
I'm seeing:
Current Base System 2.3.r.20160406.0534
Latest Base System 2.3.1.a.20160412.1222even though I have Update Settings set to
Follow 2.3 snapshots and move automatically to -RELEASE (Default). The Dashboard still shows that I'm on 2.3-RC.
-
I'm seeing:
Current Base System 2.3.r.20160406.0534
Latest Base System 2.3.1.a.20160412.1222even though I have Update Settings set to
Follow 2.3 snapshots and move automatically to -RELEASE (Default). The Dashboard still shows that I'm on 2.3-RC.
To make sure you're on the right track, click Save on the update settings with that set. Then run the update. It will show that and then during the backup it will see -RELEASE and use that instead, due to that setting.
-
To make sure you're on the right track, click Save on the update settings with that set. Then run the update. It will show that and then during the backup it will see -RELEASE and use that instead, due to that setting.
I saved as Dev, then saved as Stable.
Still showed 2.3.1 (noting what you said above), and hit update:
>>> 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. ERROR: It was not possible to determine pfSense-repo-devel remote version Failed -
To make sure you're on the right track, click Save on the update settings with that set. Then run the update. It will show that and then during the backup it will see -RELEASE and use that instead, due to that setting.
I saved as Dev, then saved as Stable.
Still showed 2.3.1 (noting what you said above), and hit update:
>>> 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. ERROR: It was not possible to determine pfSense-repo-devel remote version FailedI was on the last RC before release and was on the stable track but saw update to 2.3.1a. Saving RELEASE track in settings didn't show 2.3. SSH'd in and downloaded new pkg key but still showed 2.3.1a. Solved it by selecting "13) Update from console" which removed the old repo-devel, refreshed the pkg database and offered update to 2.3 which worked great.
-
Mine is showing the same thing.
I was on the last RC before release and was on the stable track but saw update to 2.3.1a. Saving RELEASE track in settings didn't show 2.3. SSH'd in and downloaded new pkg key but still showed 2.3.1a. Solved it by selecting "13) Update from console" which removed the old repo-devel, refreshed the pkg database and offered update to 2.3 which worked great.
That fixed it! Thanks!!
-
I ended up doing a clean install of 2.3 release after it upgraded me to 2.3.1 from RC.
-
I've tried the suggestions in this thread but they've made no difference. Every time I try initiating the update I get stuck at
>>> Updating repositories metadata... Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. 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. >>> Upgrading pkg...EDIT: On another box I had the options Development and Stable in the Update Settings and on that box, after updating the keys, the update went smoothly. I think part of the problem might be that the box I'm having trouble on has an older version because the Update Settings page does not have those exact options.
2ND EDIT: Grrr. Tried getting around this by changing the Branch setting from Follow 2.3 snapshots and move automatically to -RELEASE to Keep following 2.3 development snapshots in the Update Settings. My thinking was this would bring me up to date up to the latest 2.3 RC version and then I'd be good to go on updating to RELEASE. Well, ended on up 2.3.1-DEVELOPMENT and now I'm getting The system is on a later version than the official release. This is solved for me: I'm taking the easy way out and restoring from a earlier snapshot that had 2.2.6 and updating from there.
-
Well, any way to come back from 2.3.1-dev to 2.3 Release without a reinstall ?
-
Hi
I found out, that I'm still on
pfSense-repo-2.3.r.20160406.0534
but can not upgrade to pfSense-repo-2.3.1.a.20160412.1222
pkg version pfSense-rc-2.3.1.a.20160412.1222 = pfSense-repo-2.3.r.20160406.0534 <pkg search pfSense-repo pfSense-repo-2.3.1.a.20160412.1222 pfSense pkg repository configuration (stable)pkg install pfSense-repo-2.3.1.a.20160412.1222 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. pkg: No packages available to install matching 'pfSense-repo-2.3.1.a.20160412.1222' have been found in the repositories -
I have two pfSense appliances. Both on Version 2.3.r.20160405.0247.
On one pfSense it worked after I used```
fetch -qo /usr/local/share/pfSense/keys/pkg/trusted/ https://raw.githubusercontent.com/pfsense/pfsense/RELENG_2_3_0/src/usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406On the other pfSense I still get 2.3.1.a.20160412.1222 from the update tab. Changed the firmware branch to development and back to stable. Does not seem to work, when I select development it refreshes and jumps back to stable. Tried using option 13 on cli but still get 2.3.1.a.20160412.1222. Any suggestions? -
One of my pfSense boxes is already 2.3.1a
The other one, after having set Stable in update settings, wants to update to 2.3.1a regardless of trying in GUI or ShellpfSense-base: 2.3.r.20160331.2348 -> 2.3.1.a.20160412.1222 [pfSense-core] -
I am also having an issue with updating. I was on the last RC and attempted to update to 2.3-RELEASE and received the following error.
-
I'm seeing:
Current Base System 2.3.r.20160406.0534
Latest Base System 2.3.1.a.20160412.1222even though I have Update Settings set to
Follow 2.3 snapshots and move automatically to -RELEASE (Default). The Dashboard still shows that I'm on 2.3-RC.
To make sure you're on the right track, click Save on the update settings with that set. Then run the update. It will show that and then during the backup it will see -RELEASE and use that instead, due to that setting.
You guys made a major poop on this one.
By following this some of us some how ended up on the dev even though we had the "Follow 2.3 snapshots and move automatically to -RELEASE (Default)" set.
How can we fix this? Like others here I try to force an update to 2.3-RELEASE but I cant cause I am on a devel version.
There has to be a fix to this without having to re-install. -
I am also having an issue with updating. I was on the last RC and attempted to update to 2.3-RELEASE and received the following error.
First post of jimp resolves this issue !
-
You guys made a major poop on this one.
I don't know about that, at this point 2.3.1 is ~= 2.3-REL (aside from a few extra fixes, so, bonus). It didn't brick anything, things still work, etc. Inconvenient, sure, but not FUBAR.
By following this some of us some how ended up on the dev even though we had the "Follow 2.3 snapshots and move automatically to -RELEASE (Default)" set.
How can we fix this? Like others here I try to force an update to 2.3-RELEASE but I cant cause I am on a devel version.
There has to be a fix to this without having to re-install.There is, I was able to replicate it once yesterday. I'm working on a procedure to switch back. It's not terribly difficult, but I need to be able to repeat it reliably.
-
-
Please, help me to restore a full back-up that i made before "upgrading" to 2.3. My snort rules doesn't work anymore and i have the feeling that a bunch of other things are broken now with this new 2.3 release.
I have the back-up stored on /root ( pfSense-full-backup-20160413-1446.tgz). How can i invoke it from the terminal? In /etc i can't find any rc.restore full back-up. On the forum i can't find any other info about this. Thank you in advance.
-
Please, help me to restore a full back-up that i made before "upgrading" to 2.3. My snort rules doesn't work anymore and i have the feeling that a bunch of other things are broken now with this new 2.3 release.
I have the back-up stored on /root ( pfSense-full-backup-20160413-1446.tgz). How can i invoke it from the terminal? In /etc i can't find any rc.restore full back-up. On the forum i can't find any other info about this. Thank you in advance.
That feature is not supported on pfSense 2.3. Your safest path is to reinstall the older version directly. Otherwise you'll end up with a mix of things all over the filesystem (which was one of many reasons that feature was removed…)
Better still would be to work and get snort working on 2.3. The package maintainer is very active in the IDS/IPS board here under packages. Post there for snort help, it's probably not a difficult fix.
-
You guys made a major poop on this one.
I don't know about that, at this point 2.3.1 is ~= 2.3-REL (aside from a few extra fixes, so, bonus). It didn't brick anything, things still work, etc. Inconvenient, sure, but not FUBAR.
By following this some of us some how ended up on the dev even though we had the "Follow 2.3 snapshots and move automatically to -RELEASE (Default)" set.
How can we fix this? Like others here I try to force an update to 2.3-RELEASE but I cant cause I am on a devel version.
There has to be a fix to this without having to re-install.There is, I was able to replicate it once yesterday. I'm working on a procedure to switch back. It's not terribly difficult, but I need to be able to repeat it reliably.
Thank you for your fast reply jimp.
