Upgrade 2.3.2-RELEASE-p1 to 2.3.3 failed
-
What bootup slice are you on? (Diagnostics -> NanoBSD)
-
I tried to update from both slices, from slice 1 and 2. I tried multiple times (from the webgui and also from the console)
The update seems to be succefull, I even got the email saying the update is succesfull and the system is rebooting, But when I login after the reboot the system still seems to be on the 2.3.2 version -
Hi,
Any followup on the above please ?
What should i do to succesfully upgrade ? -
Try
pkg delete -f openvpn\*Otherwise, doing a fresh reinstall would be a whole lot faster that debugging this junk, especially with the slice duplication on nanobsd.
-
I observed that just the info shown is outdated (on gui as well as on console). What does uname -a give you?
-
Never had problems before with upgrading pfsense
This is what I am seeing in de upgrade log
Installed packages to be REINSTALLED:
scponly-4.8.20110526_2 [pfSense] (options changed)
rrdtool-1.6.0_1 [pfSense] (direct dependency changed: perl5)
net-snmp-5.7.3_11 [pfSense] (options changed)
miniupnpd-1.9.20160113,1 [pfSense] (options changed)Number of packages to be installed: 4
Number of packages to be upgraded: 76
Number of packages to be reinstalled: 4The process will require 20 MiB more space.
[1/84] Upgrading python27 from 2.7.12 to 2.7.13_1…
[1/84] Extracting python27-2.7.13_1: Child process pid=86376 terminated abnormally: Killed -
[1/84] Extracting python27-2.7.13_1: Child process pid=86376 terminated abnormally: Killed
Apparently out of RAM. NanoBSD?
-
Yes NanoBSD
An PC Engines Alix Board (alix2d13)
Any solution or workarround for this issue ? (maybe removing some packages first? I have zabbix-agent, zabbix-proxy, cron and openvpn-client-export packages installed) -
No succes (also not with uninstalling packages first) so I did a clean install as adviced
Thanks !
-
Well, the only "solution" is to kill as many services as possible (and that includes ntpd, nginx etc.)