Update from 2.3 to 2.3.1
-
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.
-
Oh, that should work now. Thanks
-
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.
-
Tried another time and it worked OK.
This was from the GUI and not from command line.
-
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.
-
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 -
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
FailedAfter 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
FailedAny suggestions?
-
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.
-
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.
-
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!
-
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.
-
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.
-
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.
-
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.
-
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 -
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 0just log spam, the crash reporter suppresses it in 2.3.1+.
-
@cmb:
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 0just log spam, the crash reporter suppresses it in 2.3.1+.
I appreciate the reply. Just to confirm though, I shouldn't be seeing this? It's popping up on my dashboard via the crash reporter (after updating from 2.3_1 to 2.3.1).
-
Since it happened before you were on 2.3.1, you can see it. You shouldn't see it again.
-
@cmb:
Since it happened before you were on 2.3.1, you can see it. You shouldn't see it again.
Ahh, I see. So the actual "error" is in the first part of the crash report, which is a fixed timestamp. Whereas the PHP warning that I posted, which gets a new timestamp every time I clear it and reboot, is essentially just a display artifact of that initial "error"?
Edit: Tried my best to fully clear it out - keeps coming back.
Edit2: I think I cleared it out successfully. I ended up moving to the development version, then back to 2.3.1. I realize per cmb that is was probably nothing, but it bothered me :)
-
Not sure whether to start a new thread or not.
However after upgrading from 2.3_1 to 2.3.1 my WAN wouldn't come up. Both onboard intel NICs. LAN was fine but no WAN IP.
Tried to edit/save interface in the GUI as per the 2.3 upgrade issues sticky (though I was already on 2.3), that didn't help.
System log filled every second line with this from boot:
syslogd sendto: Network is unreachable
Ended up fixing it somehow by ssh'ing to the box, and reassigning interfaces to what they were already set to.
DHCP seems to be throwing a fair few errors now though:
May 19 12:07:53 php-fpm 48160 /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 0.0.0.0 -> 192.168.0.32 - Restarting packages.
That's a bit of a worry.
