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

serialdie

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!!!

YonNomNom

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 :(

pfsense.png_thumb

christian.arminio

@YonNomNom:

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 gateway

Super Regards

jimp

@christian.arminio:

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.

jimp

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.

Guest

@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!!!

Worked for me too…

lrosenman

@marjohh:

@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!!!

Worked for me too…

Worked for me as well… THANK YOU!

fr0t

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 :/

tomaswaldow

@fr0t:

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 :/

https://doc.pfsense.org/index.php/2.3_Removed_Packages

edmund

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

I had this problem a while back with my nano system at home earlier this year. I'd suggest looking through your config.xml file and see it there are any duplicate sections, mine had two sections setting up the local DHCP server on different subnets and once I deleted the bad one everything worked fine.

brianc69

I was on 2.3.1.xxxx and noticed this morning it was unable to check for updates and the packages section shows no packages installed. I went to diagnostics/command prompt and tried pkg upgrade -f and got:

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.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
pkg: 1.7.2 -> 1.7.2_1 [pfSense]

2 MiB to be downloaded.

Proceed with this action? [y/N]:

How does one and the y/N question??? Is this even the answer to my problem?

jimp

@brianc69:

I was on 2.3.1.xxxx and noticed this morning it was unable to check for updates and the packages section shows no packages installed. I went to diagnostics/command prompt and tried pkg upgrade -f and got:

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.
New version of pkg detected; it needs to be installed first.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
pkg: 1.7.2 -> 1.7.2_1 [pfSense]

2 MiB to be downloaded.

Proceed with this action? [y/N]:

How does one and the y/N question??? Is this even the answer to my problem?

'y' is OK there. But please read the original post of the thread, second section, last entry.

brianc69

The problem is you can't answer Y or N in the web gui.

wirerogue

@brianc69:

The problem is you can't answer Y or N in the web gui.

don't run it from the web gui. use the console.

phil.davis

@brianc69:

The problem is you can't answer Y or N in the web gui.

The webGUI has already asked the user to confirm they want to upgrade (which incidentally it does (and kind of has to do) before the user can see the full list of bits and pieces that will be upgraded) and so any back-end script code that uses package commands to actually do the bits of the upgrade should use whatever parameter is needed to tell it "go ahead whatever happens, do not ask interactively for confirmation of anything".

I thought that had been sorted out already, but obviously not for this case of it doing some early update before the full-blown thing.

jits

Awesome!

Many thanks for this sticky. Has solved the "updating' issue for me. Pfsense Base was missing. Thanks again.