pfSense Forum

pfSense English Support => Installation and Upgrades => Topic started by: jimp on April 12, 2016, 01:19:42 pm

Title: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on April 12, 2016, 01:19:42 pm
For issues updating from RC (or older) to -RELEASE:


No trusted public keys found
If you see an error when checking for or installing updates that states "No trusted public keys found", run the following command from the shell or Diagnostics > Command:

Code: [Select]
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

Unable to Check for Updates
If you see "unable to check for updates", and/or the package manager cannot fetch data:

First, make sure you have pfSense-base or pfSense-base-nanobsd installed:

Check the output of:
Code: [Select]
pkg info -x pfSense
If pfSense-base is missing (Full install) or if pfSense-base-nanobsd missing (NanoBSD), run:

Code: [Select]
pkg install pfSense-base



Upgrade resulted in running 2.3.1 or the version claims to be newer

For anyone who landed on 2.3.1 or has a message stating that they are on a newer version than release: To get 2.3-RELEASE proper, follow this:

First, check the pkg repository configuration:

Code: [Select]
ls -l /usr/local/etc/pkg/repos/pfSense.conf
It should point to /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf

If it does not:

Code: [Select]
rm /usr/local/etc/pkg/repos/pfSense.conf
ln -s /usr/local/share/pfSense/pkg/repos/pfSense-repo.conf /usr/local/etc/pkg/repos/pfSense.conf

Double check the contents of the file:

Code: [Select]
: cat /usr/local/etc/pkg/repos/pfSense.conf
FreeBSD: { enabled: no }

pfSense-core: {
  url: "pkg+http://pkg.pfsense.org/pfSense_v2_3_0_amd64-core",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

pfSense: {
  url: "pkg+http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg",
  enabled: yes
}

If the contents of that file matches above, OK, if not, edit the file and make it match.

Force an update to the pkg database:

Code: [Select]
pkg update -f
If that fails:

Code: [Select]
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
And then run the update command again.

Lastly, force an upgrade of all installed packages:

Code: [Select]
pkg upgrade -f
If an error is shown that the kernel package is locked, you can unlock it with "pkg unlock <name>" replacing <name> with what the error complains about, then run the "pkg update -f" command again. Be sure to lock it back after you're done.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: GTAXL on April 12, 2016, 02:27:05 pm
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
Success

So I guess it's just reading the current base system incorrectly? No biggie just throwing that out there.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: ohwell on April 12, 2016, 02:36:29 pm
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on April 12, 2016, 02:38:21 pm
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: Achromatic on April 12, 2016, 02:59:06 pm

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:

Code: [Select]
>>> 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
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: qubit on April 12, 2016, 04:58:52 pm

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:

Code: [Select]
>>> 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

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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: troyborg on April 12, 2016, 05:00:25 pm
Mine is showing the same thing.
(http://i.imgur.com/lhX8nkg.png)
(http://i.imgur.com/ShQiTeP.png)

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!!
(http://i.imgur.com/eW48YAq.png)
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: usual on April 12, 2016, 07:27:46 pm
I ended up doing a clean install of 2.3 release after it upgraded me to 2.3.1 from RC.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: carriage on April 12, 2016, 09:50:00 pm
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

Code: [Select]
>>> 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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: deajan on April 13, 2016, 02:36:33 am
Well, any way to come back from 2.3.1-dev to 2.3 Release without a reinstall ?
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: p1erre on April 13, 2016, 02:46:38 am
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

Code: [Select]
pkg version

pfSense-rc-2.3.1.a.20160412.1222   =
pfSense-repo-2.3.r.20160406.0534   <

Code: [Select]
pkg search pfSense-repo
pfSense-repo-2.3.1.a.20160412.1222 pfSense pkg repository configuration (stable)

Code: [Select]
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
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: betatest on April 13, 2016, 03:55:53 am
I have two pfSense appliances. Both on Version 2.3.r.20160405.0247.
On one pfSense it worked after I used
Code: [Select]
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?
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: deajan on April 13, 2016, 04:35:15 am
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

Code: [Select]
pfSense-base: 2.3.r.20160331.2348 -> 2.3.1.a.20160412.1222 [pfSense-core]
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: raidflex on April 13, 2016, 08:37:45 am
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.

(http://i68.tinypic.com/15rl1fp.png)
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: serialdie on April 13, 2016, 09:13:04 am
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: deajan on April 13, 2016, 09:49:10 am
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 !
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on April 13, 2016, 09:58:06 am
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: raidflex on April 13, 2016, 11:43:28 am
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!
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: waves on April 13, 2016, 11:44:18 am
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on April 13, 2016, 11:50:20 am
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: serialdie on April 13, 2016, 11:56:36 am
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on April 13, 2016, 11:58:58 am
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: waves on April 13, 2016, 12:08:58 pm

Quote
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: serialdie on April 13, 2016, 12:43:09 pm

Quote
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: serialdie on April 13, 2016, 12:43:36 pm
@jimp,

Thanks for the update... so far so good.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: christian.arminio on April 13, 2016, 05:51:25 pm
Hello,

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

Code: [Select]
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 :

Code: [Select]
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
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: MyKroFt on April 13, 2016, 06:28:52 pm
have done everything is post #1 am still stuck....

Code: [Select]
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
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: IrrationalEscalation on April 13, 2016, 08:37:35 pm
Code: [Select]
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!
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: wirerogue on April 13, 2016, 08:58:48 pm
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!!!

Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: YonNomNom on April 14, 2016, 02:11:17 am
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 :(
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: christian.arminio on April 14, 2016, 02:34:33 am
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....
Code: [Select]
System_Routing_Gateways_Edit
Select This will select the above gateway as the default gateway

Super Regards
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on April 14, 2016, 05:58:07 am
after update I've many problems and web gui shows always this message :

Code: [Select]
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on April 14, 2016, 05:59:12 am
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: marjohh on April 14, 2016, 06:02:34 am
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...
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: lrosenman on April 14, 2016, 03:55:04 pm
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!
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: fr0t on April 15, 2016, 04:23:37 am
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 :/
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: Tomas Waldow on April 15, 2016, 05:15:03 am
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
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: edmund on April 15, 2016, 07:50:54 am
Quote
Code: [Select]
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: brianc69 on April 16, 2016, 12:23:25 pm
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?
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on April 18, 2016, 11:15:11 am
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: brianc69 on April 18, 2016, 05:44:11 pm
The problem is you can't answer Y or N in the web gui.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: wirerogue on April 19, 2016, 07:15:14 pm
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: phil.davis on April 19, 2016, 09:38:51 pm
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.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jits on April 22, 2016, 02:58:31 pm
Awesome!

Many thanks for this sticky. Has solved the "updating' issue for me. Pfsense Base was missing. Thanks again.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: Bonsai on July 28, 2016, 06:57:58 am
First to say ... mypfsense box is 1200 km away and I have only access over the web frontend and not over a direct console.

As I got the issue that the update stopped somewhere in the middle, I rebooted the machine. Then the Frontend claimed to be on 2.3.2, but was still on 2.3.1.

I followed the instructions in the first post "Upgrade resulted in running 2.3.1 or the version claims to be newer", except that I used an additional -y parameter on commands who are asking Y/N.

pkg upgrade -f -y
Ran first into an "504 Gateway Time-out"

if I repeat this .... it happens sometimes again and sometimes it does more and stops then there:
[4/131] Extracting python27-2.7.12: Child process pid=87727 terminated abnormally: Killed

I can reproduce it .... now third time exactly this message (except logically the pid)

My knowledge about FreeBSD is very limited. On a linux I would try to completely uninstall the python package and install it again.
Is there a better approach?
How to force this uninstall / install?
Will the frontend still work if python is missing? Remember, I do not have a real console and the box is 1200km away from me (additionally all staff members over there are in holidays!)

Sorry for asking probably beginner questions, but I need to be VERY sure, that the box will not fail completely, becasue email would be the only service what would not fail if my VPN fails .... everything else in the company would be down and currently all flights are overbooked here on our airoport, as I sit on a holiday island with my local office. With ship and car I would need more than a day to get there.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on July 28, 2016, 08:22:40 am
Are you running that from ssh or from the GUI? If you are trying to run that from the GUI, use SSH instead.

There was an issue yesterday morning (US time) with the update server but it was cleared up by the afternoon. Everything should be back to normal now.

If you're running that from the shell and it's still failing, that is a bit more confusing. I've hit a few random issues here and there when testing (while the server was having a problem, mostly) but I've not seen it die in that way.

The GUI can run without python (except, perhaps, for RRD graphs) if you need to force its removal, but it should be reinstalled automatically when you attempt to upgrade since it's a dependency of glib, which is a dependency of rrdtool

And use "pfSense-upgrade -d" to run the upgrade if you can.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: Bonsai on July 29, 2016, 09:32:36 am
I alsways used the frontend .... in future ssh only! Thanks for the hint.

pfSense-upgrade -d looked good in the beginnig. It told me something about second partition required, as I saw it on the other box.

Then .... connection dropped .... and never came back.  :o

No response on any port. Neither https, nor ssh, nor the two OpenVPN ports.

So my box is completely crashed in Germany and I sit in Spain.  >:(

On Monday I have somebody there into our building .... but she is a pure user .... if a hard reboot fails, I'll try a factory reset. The basic configuration until I get the box remotely will be an adventure in blind flight ....

May I ask to modify this upgrade procedure, please? If something is wrong with the server the upgrade should just do nothing. My boss is  ...... pissed is the wrong word ... too weak .... can't tell it in english, but I guess you know.  ;)

Thank you that you tried to help. I learned from this ..... NEVER do an upgrade if nobody is onsite.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on July 29, 2016, 09:43:24 am
If it mentioned a second partition, you must be on NanoBSD. I've not seen one of those yet fail in a way that would cause it to die like that because of software. We have seen some fail due to hardware (bad CF/disk, etc), but not from the upgrade procedure itself.

The NanoBSD update procedure is very safe. If there are problems it does not switch over to boot from the updated slice, and it won't even reboot. If it rebooted, it must have completed the upgrade procedure successfully.

FYI- NanoBSD is not going to be a part of pfSense 2.4, so it's even less likely to be a concern in the future.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: divsys on July 29, 2016, 07:07:44 pm
Don't know if it warrants an update to the sticky or not, but I just ran into a scenario where the GUI was unable to check for updates on a 2.3 install.
Tried various suggestions via the sticky on both GUI and shell, managed to get my self to a point where the GUI couldn't determine the current version and the shell wouldn't attempt an update (don't remember the shell error - sorry).

Searched out:http://doc.pfsense.org/index.php/UpgradeGuide (http://doc.pfsense.org/index.php/UpgradeGuide) and found a reference for older snapshots (which this one was possibly) needing "find / -type l -lname '/usr/pbi/*' -delete" to clear old symlinks.

Once done I was able to use the shell to work forward through errors, and with the sticky make the upgrade work.

I mention this only to try and reduce the searching needed to resolve upgrade issues for older systems without needing to do a full reinstall.

Might be worth adding the potential need to kill the symlinks into the sticky.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: sen.s0r on August 01, 2016, 04:33:24 am
I've SSH'd into my pfsense box and tried to upgrade it from the console.

I've tried the auto option and install from URL (using the right one for my box) and keep getting an error because the SHA256's don't match.

Anyone any ideas what I'm doing wrong!?

TIA
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on August 01, 2016, 07:56:07 am
I've SSH'd into my pfsense box and tried to upgrade it from the console.

I've tried the auto option and install from URL (using the right one for my box) and keep getting an error because the SHA256's don't match.

Anyone any ideas what I'm doing wrong!?

TIA

It sounds like you are attempting an upgrade scenario that is much different from this thread. Start a new thread with more specifics about your current setup and someone can assist there.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: Bonsai on August 02, 2016, 05:54:07 am
Just update a guess from me. My box is fully broken, reset to manufacurers setting failed.

I had nobody onsite there as I updated. The person who came onsite yesterday morning reported, that our server was down and our printer was down. This means we had an power outage. As I told her the time when I updated my pfsense, she reported that there had been a huge thunderstorm at this time of the day in this area. So probably system crashed becasue this power outage. It was probably just Murphys Law ....

What I learned now from this issue: Never do a remote upgrade of such an important system without checking the weather onsite!

Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: fruitypulp on September 06, 2016, 01:29:12 pm
Here is some information for one of the problems caused by a missing resolv.conf in the chroot during upgrade...

https://forum.pfsense.org/index.php?topic=117905.msg653100#msg653100

I have not seen it discussed before.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: Ghostdragon97 on October 18, 2016, 03:46:31 am
I've followed this post, and am experiencing the same issues, running nanobsd, i have 2.3.2-release

pkg info gives me this output
pfSense-2.3.2
pfSense-Status_Monitoring-1.4.4_2
pfSense-base-nanobsd-2.3.2
pfSense-default-config-serial-2.3.2
pfSense-kernel-pfSense_wrap-2.3.2
pfSense-rc-2.3.2
pfSense-repo-2.3.2
php56-pfSense-module-0.12

pkg update -f gives me this output
Updating pfSense-core repository catalogue...
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/meta.txz: Internal Server Error
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/packagesite.txz: Internal Server Error
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-pfSense_v2_3_2/meta.txz: Internal Server Error
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-pfSense_v2_3_2/packagesite.txz: Internal Server Error
Unable to update repository pfSense

I have verified that the connectivity is good, can access the net from clients on the box.
I have checked that all of the files mentioned do exist, and they match your output (With the exception of the version number)
Any ideas???
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: phil.davis on October 18, 2016, 07:21:29 am
I've followed this post, and am experiencing the same issues, running nanobsd, i have 2.3.2-release

pkg info gives me this output
pfSense-2.3.2
pfSense-Status_Monitoring-1.4.4_2
pfSense-base-nanobsd-2.3.2
pfSense-default-config-serial-2.3.2
pfSense-kernel-pfSense_wrap-2.3.2
pfSense-rc-2.3.2
pfSense-repo-2.3.2
php56-pfSense-module-0.12

pkg update -f gives me this output
Updating pfSense-core repository catalogue...
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/meta.txz: Internal Server Error
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-core/packagesite.txz: Internal Server Error
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-pfSense_v2_3_2/meta.txz: Internal Server Error
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_3_2_i386-pfSense_v2_3_2/packagesite.txz: Internal Server Error
Unable to update repository pfSense

I have verified that the connectivity is good, can access the net from clients on the box.
I have checked that all of the files mentioned do exist, and they match your output (With the exception of the version number)
Any ideas???
See this message and the recent posts above it in the thread:
https://forum.pfsense.org/index.php?topic=119511.msg662743#msg662743 (https://forum.pfsense.org/index.php?topic=119511.msg662743#msg662743)
The issues with the package server should be resolved now.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: fibrewire on October 26, 2016, 04:36:52 pm
FYI- NanoBSD is not going to be a part of pfSense 2.4, so it's even less likely to be a concern in the future.
If you don't mind me asking, why is NanoBSD going away? Will 4GB CF cards still be supported?
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on October 26, 2016, 05:46:15 pm
FYI- NanoBSD is not going to be a part of pfSense 2.4, so it's even less likely to be a concern in the future.
If you don't mind me asking, why is NanoBSD going away? Will 4GB CF cards still be supported?

It's going away because it doesn't make sense to maintain it anymore. As hardware and media changes over time it makes less sense to operate the way it does.

We're looking into ways to accommodate headless systems without a working console, but there are very few such devices that are 64-bit. We're also looking into ways to in-place upgrade from NanoBSD to a full install.

CF will still work with a full install, as long as the hardware is 64-bit.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: addy.sharma on March 19, 2017, 05:00:32 am
Unable to upgrade on the GUI of pfsense it gives me the following error:

pfSense-default-config: 2.3.3 -> 2.3.3_1 [pfSense-core]
   pfSense-base: 2.3.3 -> 2.3.3_1 [pfSense-core]
   pfSense: 2.3.3 -> 2.3.3_1 [pfSense]
   curl: 7.52.1_1 -> 7.53.0 [pfSense]

Number of packages to be upgraded: 7

41 MiB to be downloaded.
Fetching pfSense-kernel-pfSense-2.3.3_1.txz: .......... done
Fetching pfSense-default-config-2.3.3_1.txz: . done
Fetching pfSense-base-2.3.3_1.txz: . done
pkg: https://pkg.pfsense.org/pfSense_v2_3_3_amd64-core/All/pfSense-base-2.3.3_1.txz: Operation timed out
>>> Locking package pfSense-kernel-pfSense... done.
Failed
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: chrcoluk on June 08, 2017, 11:16:58 am
pkg.pfsense.org doesnt even resolve here.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on June 08, 2017, 12:12:32 pm
pkg.pfsense.org doesnt even resolve here.

You're doing it wrong.
https://forum.pfsense.org/index.php?topic=130708.msg719850#msg719850
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: Rajko Ray on July 13, 2017, 06:12:08 am
After upgrade:
Version   2.3-RELEASE (amd64)
built on Mon Apr 11 18:28:29 CDT 2016
FreeBSD 10.3-RELEASE

Unable to check for updates
-------------------------------------------------------------------
pkg info -x pfSense
pfSense-2.3
pfSense-Status_Monitoring-1.0_1
pfSense-base-nanobsd-2.3
pfSense-default-config-serial-2.3
pfSense-kernel-pfSense-2.3
pfSense-pkg-AutoConfigBackup-1.43_1
pfSense-pkg-aws-wizard-0.5_1
pfSense-pkg-ipsec-profile-wizard-0.9_1
pfSense-pkg-openvpn-client-export-1.4.3
pfSense-rc-2.3
pfSense-repo-2.3
php56-pfSense-module-0.12
-------------------------------------------------------------------
pkg upgrade -f
Nothing happens
-------------------------------------------------------------------
rm /usr/local/etc/pkg/repos/pfSense.conf
rm: /usr/local/etc/pkg/repos/pfSense.conf: Read-only file system
-------------------------------------------------------------------
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: /usr/local/share/pfSense/keys/pkg/trusted//pkg.pfsense.org.20160406: mkstemps(): Read-only file system
-------------------------------------------------------------------
Error: /usr/local/etc/pkg/repos/pfSense.conf: Read-only file system.
Error: /var/tmp/vi.recover/: Permission denied; Modifications not recoverable if the session fails
-------------------------------------------------------------------

Last here is present content of /usr/local/etc/pkg/repos/pfSense.conf

FreeBSD: { enabled: no }

pfSense-core: {
  url: "pkg+http://firmware.netgate.com/pkg/pfSense_factory-v2_3_0_amd64-core",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg"
  enabled: yes
}

pfSense: {
  url: "pkg+http://firmware.netgate.com/pkg/pfSense_factory-v2_3_0_amd64-pfSense_factory-v2_3_0",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/local/share/pfSense/keys/pkg"
  enabled: yes
}


Simple question which step am I missing here?
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on July 13, 2017, 08:02:42 am
rm /usr/local/etc/pkg/repos/pfSense.conf
rm: /usr/local/etc/pkg/repos/pfSense.conf: Read-only file system
[...]
Simple question which step am I missing here?

You have a filesystem problem which needs addressed. Failing to update is a symptom of some other problem you have, it's most likely not a problem with your updates.

Reboot into single user mode (option 2 at the boot menu IIRC) and then run "fsck -y /" repeatedly until it does not find any problems. Don't stop when it says the filesystem is clean, keep going until it finds no problems/makes no corrections. If that doesn't help, you might have a disk issue, or may need to reinstall. Start a new thread if you need more help with that since it isn't directly related to this thread.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: Rajko Ray on August 01, 2017, 03:27:57 am
Using admin username which isn't built-in admin behaves differently on pfsense.

Once I re-enabled "admin" account and logged to firewall via SSH console, I was able to complete update.

2 firewalls fixed with these steps so far.

File system was fine.
Title: Re: Issues updating from 2.3-RC (or older 2.3 installs) to 2.3-RELEASE
Post by: jimp on August 09, 2017, 09:35:25 am
Using admin username which isn't built-in admin behaves differently on pfsense.

Once I re-enabled "admin" account and logged to firewall via SSH console, I was able to complete update.

2 firewalls fixed with these steps so far.

File system was fine.

When you used a non-root/admin account, did you run the update via sudo?

I would expect it to fail without sudo from an unprivileged user. That also explains the errors.