2.3.4_1->2.3.5_1:the kernel does not get updated NanoBSD i386\. Too many troubles
-
Hi pfSense Team, thank you for the superior product!
I am updating the rest firewall node from 2.3.4_1 to 2.3.5_1. Everything was ok, there were no problems during the updating. After restarting I noticed, that the kernel was not up to date:
[2.3.5-RELEASE][admin@pf1.xxx.yyy]/root: uname -a FreeBSD pf1.xxx.yyy 10.3-RELEASE-p17 FreeBSD 10.3-RELEASE-p17 #10 6da131e75c7(RELENG_2_3_3): Wed Mar 8 14:27:02 CST 2017 root@ce23-i386-builder:/builder/pfsense-233/tmp/obj/builder/pfsense-233/tmp/FreeBSD-src/sys/pfSense_wrap i386
Then I tried to update once more. The disk slice was duplicated and it was said, that pfSense-kernel-pfSense_wrap package would be updated:
The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-kernel-pfSense_wrap: 2.3.3_1 -> 2.3.5_1 [pfSense-core] Number of packages to be upgraded: 1 >>> Locking package pfSense-pkg-FTP_Client_Proxy... done. >>> Unlocking package pfSense-pkg-FTP_Client_Proxy... done. >>> Setting secondary partition as active... done. Upgrade is complete. Rebooting in 10 seconds.
Unfortunately after the system restarted, the situation repeated. I tried many times to update the system, but it was an infinite loop: updating the system (updating the kernel); restarting; checking, that the kernel was old; updating the system (updating the kernel);..
NanoBSD Previous Upgrade Log shows:
2.3.5_1 version of pfSense is available
I have attached complete log file.
Could you please suggest, what can be done to update the kernel too?
Thank you,
Best regards
yarick123
pf1-upgrade-d_234-2351.txt -
I tried "pkg install -yf pkg pfSense-kernel-pfSense" and got a segmentation fault on the integrity checking stage.
Re-fetching the packages did not help…[2.3.5-RELEASE][admin@pf1.xxx.yyy.zzz]/root: /usr/sbin/pkg install -yf pkg pfSense-kernel-pfSense 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. The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: pfSense-kernel-pfSense: 2.3.5_1 [pfSense-core] Installed packages to be DOWNGRADED: pkg: 1.10.2 -> 1.10.1_1 [pfSense] Number of packages to be installed: 1 Number of packages to be downgraded: 1 The process will require 17 MiB more space. 17 MiB to be downloaded. [1/2] Fetching pkg-1.10.1_1.txz: 100% 3 MiB 444.1kB/s 00:06 [2/2] Fetching pfSense-kernel-pfSense-2.3.5_1.txz: 100% 15 MiB 416.7kB/s 00:37 Checking integrity...Child process pid=89665 terminated abnormally: Segmentation fault [2.3.5-RELEASE][admin@pf1.xxx.yyy.zzz]/root:
-
I have just reinstalled pfSense NanoBSD i386 2.3.5, restored the configuration and started upgrade to 2.3.5-1. There was a small problem:
[35/41] Fetching pfSense-kernel-pfSense_wrap_vga-2.3.5_1.txz: 139418100:error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac:/usr/local/poudriere/jails/pfSense_v2_3_5_i386/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_pkt.c:518: .......... done
Starting the upgrade the second time solved the problem. Everything was updated without any problem. But the system shows, that the version is still 2.3.5 instead of 2.3.5_1. As usual, in the update dialog, it shows, that we are already on version 2.3.5_1.
Bad luck :( It seems to be a sign to move away from NanoBSD. So many troubles with the upgrade I did not ever have.
-
After just waiting some time, the version number in the dashboard was updated.
But, "pfSense-upgrade -d" upgraded pfSense-kernel-pfSense_wrap_vga: 2.3.5 -> 2.3.5_1 [pfSense-core].
The system as rebooted. Now all versions are correct. "pfSense-upgrade -d" does not try to upgrade anything.
I cannot just believe, that the firewalls are now up to date…