Update from 2.3 to 2.3.1

cmb

If it spits out failed, there, go to SSH, option 8, and run:

pfSense-upgrade -d

and post the output.

SlackerDude

Rebooting the system did nothing for me. Here is the output from the upgrade command via ssh:

root: pfSense-upgrade -d

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.
Upgrading pkg...
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.6.2 -> 1.7.2_2 [pfSense]

The process will require 91 KiB more space.
2 MiB to be downloaded.
pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/All/pkg-1.7.2_2.txz: Not Found

I suppose I'll wait a bit and try again on the chance that I won't be competing for a spot at the trough . ;D

UPDATE: going to http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/All/, I see the file pkg-1.6.2_2.txz but not pkg-1.7.2_2.txz.

vectr0n

Also seeing the same issue with 2.3_1 -> 2.3.1

[2.3-RELEASE][root@fw0.<removed>.net]/root: pkg update
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.
[2.3-RELEASE][root@fw0.<removed>.net]/root: pkg upgrade
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.6.2 -> 1.7.2_2 [pfSense]

The process will require 91 KiB more space.
2 MiB to be downloaded.

Proceed with this action? [y/N]: y
pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/All/pkg-1.7.2_2.txz: Not Found

UPDATE:

[2.3-RELEASE][root@fw0.<removed>.net]/root: pkg add https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/pkg-1.7.2_2.txz
Fetching pkg-1.7.2_2.txz: 100% 2 MiB 2.6MB/s 00:01
Installing pkg-1.7.2_2…
the most recent version of pkg-1.6.2 is already installed</removed></removed></removed>

turker

>>> 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.
>>> Upgrading pkg...
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.6.2 -> 1.7.2_2 [pfSense]

The process will require 91 KiB more space.
2 MiB to be downloaded.
pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/All/pkg-1.7.2_2.txz: Not Found

padenom

@SlackerDude:

….
The following 1 package(s) will be affected (of 0 checked):

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

The process will require 91 KiB more space.
2 MiB to be downloaded.
pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/All/pkg-1.7.2_2.txz: Not Found

I'm getting the same behaviour on my side. However, why does the system look in pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/All and not in http://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/ directory?

PS: I'm new to pkg.

kpa

The upgrade fails to switch to the correct repository for some reason. On the second try when my upgrade succeeded I witnessed a message that said "Repository x has a wrong packagesite, need to re-create database" or something like that and it then proceeded to re-download all the repository catalogues using the correct addresses.

cmb

Oh, that should work now. Thanks

vectr0n

I seem to have found a fix:

Login to SSH # 8

Run: pfSense-upgrade -u

You should be able to run the upgrade like normal with option # 13 or via the GUI. Not sure on cause, but this fixes it.

padenom

Tried another time and it worked OK.

This was from the GUI and not from command line.

cmb

@vectr0n:

I seem to have found a fix:

either that updated the repo URL, or you just happened to catch it after I fixed the source of the issue. No need to do that at this point.

blankphoto

Had the same issue, I just kept trying. Eventually the servers will get through everyone. A staggered release may be in order for the next one, assuming more update servers are added by then.

pfSense WE LOVE GUYS. Keep up the great work.

Brian Blankenship
Proofpoint Technical Support Engineer

joelserrano

Hi,

I have run into this problem (updating from 2.3_1 to 2.3.1):

Updating repositories metadata…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/meta.txz: Forbidden
repository pfSense has no meta file, using default settings
pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/packagesite.txz: Forbidden
Unable to update repository pfSense
Failed

After a while, now I'm getting this:

Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/meta.txz: Not Found
repository pfSense has no meta file, using default settings
pkg: http://pkg.pfsense.org/pfSense_v2_3_0_amd64-pfSense_v2_3_0/packagesite.txz: Not Found
Unable to update repository pfSense
Failed

Any suggestions?

cmb

@blankphoto:

Had the same issue, I just kept trying. Eventually the servers will get through everyone. A staggered release may be in order for the next one, assuming more update servers are added by then.

No relation to the update server. I screwed up a symlink initially so those on a version that didn't already have the latest version of pkg couldn't fetch it. We were already planning automating that part of the process away for next time around.

cmb

@joelserrano:

Hi,

I have run into this problem (updating from 2.3_1 to 2.3.1):

Any suggestions?

looks like you haven't tried since it was fixed.

joelserrano

Update: after retrying several times, now the update is running as expected:

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.
Upgrading pfSense-repo... done.
Updating repositories metadata...
Updating pfSense-core repository catalogue...
Repository pfSense-core has a wrong packagesite, need to re-create database
Fetching meta.txz: . done
Fetching packagesite.txz: . done
Processing entries: . done
[…]

Thanks!

Awesome work with pfSense!! You guys rock!

SlackerDude

running "pfSense-upgrade -u", followed by "pfSense-upgrade -d" appears to be working for me. I'll be able to confirm once it completes & reboots.

UPDATE: I can confirm a successful upgrade.

churchi

@vectr0n:

I seem to have found a fix:

Login to SSH # 8

Run: pfSense-upgrade -u

You should be able to run the upgrade like normal with option # 13 or via the GUI. Not sure on cause, but this fixes it.

Thanks mate, the -u
switch is what i needed to run first, then the upgrade worked without issues.

Up until I ran this (even after the update by cmb) i was still not able to upgrade to 2.3.1. This was the fix for me.

cheers.

telerocker22

I was having the same problem, but instead of rebooting the machine, I went to the "Update Settings" tab, changed it to "Development Snapshots", saved, then put it back to "Stable", and saved again. After I did that, the update worked fine. I also saw the "need to re-create database" message.

Jailer

@Jason:

I was having the same problem, but instead of rebooting the machine, I went to the "Update Settings" tab, changed it to "Development Snapshots", saved, then put it back to "Stable", and saved again. After I did that, the update worked fine. I also saw the "need to re-create database" message.

This worked for me as well. Thanks for the tip.

nolaquen

I'm getting a different error after the update. Any ideas?

Crash report details:

PHP Errors:
[18-May-2016 19:56:23 America/New_York] PHP Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/suhosin.so' - /usr/local/lib/php/20131226/suhosin.so: Undefined symbol "ps_globals" in Unknown on line 0