Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
-
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.
-
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.
-
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.
-
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. -
Thanks for the update… so far so good.
-
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 unreachableAny help is very appreciated .
Best regards -
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
-
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!
-
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!!!
-
My pfsense box cant access the internet unless it is using a proxy (the proxy is separate to this instance of pfsense). It managed to update but now it is stuck attempting to download package metadata :(
-
My pfsense box cant access the internet unless it is using a proxy (the proxy is separate to this instance of pfsense). It managed to update but now it is stuck attempting to download package metadata :(
Oh yes,
my problem is the same…. So now I know because I can't update my catalogue......
But how fix this issue ??EDIT
Fixed…. After the upgrade to the new version no default gateway was selected by pfsense... So no route to Internet....
System_Routing_Gateways_Edit Select This will select the above gateway as the default gatewaySuper Regards
-
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 :
Diag > Backup/Restore, click the button to reset the package lock.
-
For those with other unrelated issues like proxies/gateways, please start new threads. This thread is only for the specific style of issues stated in the original post, thanks.
-
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!!!
Worked for me too…
-
@marjohh:
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!!!
Worked for me too…
Worked for me as well… THANK YOU!
-
Hi all,
Just quick question… where if ntopng package gone? I cant see it in 'Available packages' tab. I did use it a lot and now I am stuck :/
