Update from 2.3 to 2.3.1
-
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.
-
After upgrading two sites, I'm finding that a power off / on reset is needed before pfSense comes back up. No big problem for the local router, but it's a bit of an issue for the remote site.
UPDATE: Visited remote site today, and confirmed there was no access from either WAN and no access and no DHCP from LAN connection. Reboot solved the problem.
-
I still can't update, I get an operation timeout on https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/python27-2.7.11_2.txz operation timed out
The link does work though, I tried the -u and -d parameters. What happened to manual upgrading?
75 MiB to be downloaded. Fetching unbound-1.5.8.txz: . done pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/unbound-1.5.8.txz: Operation timed out >>> Locking package pfSense-kernel-pfSense... Locking pfSense-kernel-pfSense-2.3Installed packages to be REINSTALLED: rrdtool-1.5.5_1 [pfSense] (options changed) nginx-1.8.1,2 [pfSense] (options changed) 75 MiB to be downloaded. Fetching unbound-1.5.8.txz: .......... done Fetching sqlite3-3.11.1.txz: ......... done pkg: https://pkg.pfsense.org/pfSense_v2_3_1_amd64-pfSense_v2_3_1/All/sqlite3-3.11.1.txz: Operation timed out >>> Locking package pfSense-kernel-pfSense... done. *** Welcome to pfSense 2.3-RELEASE-nanobsd (amd64) on pfSense *** -
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.
Getting some similar messages myself 2.3 -> 2.3.1 upgraded yesterday:
/rc.newwanip: rc.newwanip: on (IP address: 172.25.206.1) (interface: []) (real interface: ovpns2).
/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - -> 172.25.207.1 - Restarting packages.
172.25.207.0 is IPSec tunnel
172.25.206.0 is openvpnThey are pretty regular.
Also had the web configurator stop working earlier after a spate of these. -
No issues updating here from 2.3 to 2.3.1 after a few days.
-
No issues :)
-
Tried upgrading several times from 2.3_1 to 2.3.1 via the web gui and it fails. Also tried from SSH.
Via SSH I get :-
72 MiB to be downloaded.
Locking package pfSense-kernel-pfSense_wrap…
Locking pfSense-kernel-pfSense_wrap-2.3Then it returns back to the prompt. After rebooting, I'm still on 2.3
This is on an ALIX 2C2. I also tried manually copying the boot slide from the NanoBSD menu - same issue.
