Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE

deajan

Well, any way to come back from 2.3.1-dev to 2.3 Release without a reinstall ?

p1erre

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

betatest

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.20160406


On 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?

deajan

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 Shell

pfSense-base: 2.3.r.20160331.2348 -> 2.3.1.a.20160412.1222 [pfSense-core]

raidflex

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.

serialdie

@jimp:

@ohwell:

I'm seeing:

Current Base System 2.3.r.20160406.0534
Latest Base System 2.3.1.a.20160412.1222

even 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.

deajan

@raidflex:

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 !

jimp

@serialdie:

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.

@serialdie:

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.

raidflex

@deajan:

@raidflex:

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 !

I was also successful with updating using the command in the first post. Thanks for the fix!

waves

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.

jimp

@waves:

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.

serialdie

@jimp:

@serialdie:

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.

@serialdie:

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.

jimp

I just edited a fix into the first post for people who ended up on 2.3.1 or otherwise have a message saying they're on a version newer than the release. Should fix it all up.

waves

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.

This is very bad news… :( I will try to install the older version and restore config.xml. I have a post in IDS as well, but i'm in a production enviroment and... You get my point. Thank you for your reply.

serialdie

@waves:

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.

This is very bad news… :( I will try to install the older version and restore config.xml. I have a post in IDS as well, but i'm in a production enviroment and... You get my point. Thank you for your reply.

Ouch!
2.3 is too new for production, Hence why I am using it at home/dev for now. Good luck.

serialdie

@jimp,

Thanks for the update… so far so good.

christian.arminio

Hello,

after update I've many problems and web gui shows always this message :

pfSense is booting, then packages will be reinstalled in the background.
Do not make changes in the GUI until this is complete.

I've tried the Jimp's guide at first post but it doesn't work :


pkg update -f
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.20160406
fetch: https://raw.githubusercontent.com/pfsense/pfsense/RELENG_2_3_0/src/usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406: Network is unreachable

Any help is very appreciated .
Best regards

MyKroFt

have done everything is post #1 am still stuck….

2.3-RELEASE (amd64)
built on Mon Apr 11 18:10:34 CDT 2016
FreeBSD 10.3-RELEASE

The system is on a later version than
the official release.

Myk

Gram

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.20160406

… worked for me. Thanks!

wirerogue

@jimp:

I just edited a fix into the first post for people who ended up on 2.3.1 or otherwise have a message saying they're on a version newer than the release. Should fix it all up.

worked for me. you da man!!!