Upgrade 2.3.5 to 2.4.3 ... crash report
-
That is my concern ... the pfSense is in Dallas, Texas (a VM) and I am in Norfolk UK ... if it goes bang I'm stuck! :(
Gut feeling? Should be okay? I have the config backed up.
Worst case I could get the datacentre guys to upload a vanilla 2.4.3 for me. -
Yeah that might be tricky. As it is, the inconsistent state will most likely lead to a failure in some way, though. I'd proceed with the upgrade but have the datacenter crew prepped with an installer image in case. During the install they can choose the Recover config.xml option and then proceed through the installation and it will retain your current settings. That will only take a few minutes to complete and avoids having to do anything special to restore the config.
-
Thanks - that was my thoughts also.
I have asked to datacentre guys to confirm they can put the pieces together if required - just waiting for their reply. :) -
Hi jimp,
Okay - tried the update from the CLI but still failed. This error on boot:
Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/rrd.so' - Shared object "librrd.so.8" not found, required by "rrd.so" in Unknown on line 0
Thanks
Colin
-
Any thoughts. Presume I just need to install the missing bits?
Thanks
-
What was the output from
pfSense-upgrade
? Is the output ofpkg upgrade -n
still the same?You might be able to force an update of everything with something like
pkg unlock pfSense-kernel-pfSense; pkg upgrade -f
.I'd still be prepared for a reinstallation, though.
-
Thanks jimp,
Got the datacentre guys on standby (with a config file). :)
When I run pfsense-upgrade /d it all appears to upgrade okay and then reboots and throws the error:
Warning: PHP Startup: Unable to load dynamic library โ/usr/local/lib/php/20131226/rrd.soโ - Shared object โlibrrd.so.8โ not found, required by โrrd.soโ in Unknown on line 0
Am I not able to just install the missing library?Thanks
Colin
-
@colinjack said in Upgrade 2.3.5 to 2.4.3 ... crash report:
Am I not able to just install the missing library?
I gave the command for that up at the start of this thread. But what worries me is if other things are also missing or failing to upgrade, there may be a deeper issue on the system as a whole.
-
@jimp said in Upgrade 2.3.5 to 2.4.3 ... crash report:
Sorry - you did:
Try running pkg upgrade -f rrdtool, if it claims the package is not installed or gives a different error, then do pkg install -f rrdtool.I think your worries are valid but I agree with you that it needs to be sorted because there may be underlying problems which will surface later.
I will have another go and then see what happens. As I said, I have the datacentre crew on standby!
Thanks for your help on this.
-
@colinjack said in Upgrade 2.3.5 to 2.4.3 ... crash report:
Hmmm ...
[2.3.5-RELEASE][root@firewall]/root: pkg upgrade -f rrdtool
Shared object "libssl.so.8" not found, required by "pkg"
[2.3.5-RELEASE][root@firewall]/root: pkg install -f rrdtool
Shared object "libssl.so.8" not found, required by "pkg"
[2.3.5-RELEASE][root@firewall]/rootpkg upgrade -n
Shared object "libssl.so.8" not found, required by "pkg"So forcing upgrade will also throw the pkg error?
-
Use
pkg-static
instead ofpkg
in that case, but that is another sign that your system is still stuck between 2.3.x and 2.4.x. -
[2.3.5-RELEASE][root@firewall]/root: pkg-static upgrade -f rrdtool
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.txz: 100% 944 B 0.9kB/s 00:01
Fetching packagesite.txz: 100% 131 KiB 134.3kB/s 00:01
Processing entries: 100%
pfSense repository update completed. 498 packages processed.
All repositories are up to date.
pkg-static: rrdtool is not installed, therefore upgrade is impossible
Checking integrity... done (0 conflicting)
Your packages are up to date. -
I am loathe to post the full output from 'pkg-static upgrade /n' (bad forum etiquette) but would that be useful?
Can I stick it a text file and attach it to my post? -
You can attach a text file to a post. But it's also OK if you wrap it in code tags (select it all, hit the code button in the composer, or put ``` before and after the block.)
-
@jimp Which would you prefer?
-
I don't care much either way, whatever you are more comfortable posting is fine.
-
Here you go then!
[2.3.5-RELEASE][root@firewall]/root: pkg-static upgrade -n 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. Checking for upgrades (123 candidates): 100% Processing candidates (123 candidates): 100% Cannot solve problem using SAT solver, trying another plan Cannot solve problem using SAT solver, trying another plan Cannot solve problem using SAT solver, trying another plan Cannot solve problem using SAT solver, trying another plan Checking integrity... done (2 conflicting) - php-suhosin-0.9.38_3 [pfSense] conflicts with php56-suhosin-0.9.38_3 [installed] on /usr/local/lib/php/20131226/suhosin.so - pecl-radius-1.4.0.b1 [pfSense] conflicts with php56-pecl-radius-1.4.0.b1 [installed] on /usr/local/lib/php/20131226/radius.so Cannot solve problem using SAT solver, trying another plan Cannot solve problem using SAT solver, trying another plan Cannot solve problem using SAT solver, trying another plan Cannot solve problem using SAT solver, trying another plan Checking integrity... done (0 conflicting) The following 93 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: php56-gettext-5.6.35 php56-curl-5.6.35 pfSense-Status_Monitoring-1.6.5 pfSense-2.3.5_2 libzmq4-4.2.3 glib-2.50.3_2,1 dnsmasq-2.79,1 bind-tools-9.12.1 New packages to be INSTALLED: python2: 2_3 [pfSense] devcpu-data: 1.16 [pfSense] pear-Crypt_CHAP: 1.5.0 [pfSense] pear: 1.10.5_1 [pfSense] openvpn: 2.4.4_1 [pfSense] liblz4: 1.8.0,1 [pfSense] pear-Net_IPv6: 1.3.0.b2_2 [pfSense] pear-Net_Growl: 2.7.0 [pfSense] mobile-broadband-provider-info: 20170310 [pfSense] pear-Mail: 1.4.1,1 [pfSense] pear-Net_SMTP: 1.8.0 [pfSense] pear-Net_Socket: 1.0.14 [pfSense] Installed packages to be UPGRADED: ssh_tunnel_shell: 0.1 -> 0.1_1 [pfSense] radvd: 1.9.1 -> 2.17_4 [pfSense] qstats: 0.1_1 -> 0.2 [pfSense] php56-pfSense-module: 0.13_1 -> 0.61 [pfSense] pfSense-default-config: 2.3.5_2 -> 2.4.3_1 [pfSense-core] pfSense-base: 2.3.5_2 -> 2.4.3_1 [pfSense-core] filterlog: 0.1_4 -> 0.1_5 [pfSense] filterdns: 1.0_9 -> 1.0_16 [pfSense] dpinger: 2.0 -> 3.0 [pfSense] check_reload_status: 0.0.7 -> 0.0.8 [pfSense] Installed packages to be DOWNGRADED: unbound: 1.7.0 -> 1.6.8 [pfSense] libunistring: 0.9.9 -> 0.9.8 [pfSense] curl: 7.59.0 -> 7.58.0 [pfSense] Installed packages to be REINSTALLED: xinetd-2.3.15_2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') wrapalixresetbutton-0.0.7 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') wpa_supplicant-2.6_2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') wol-0.7.1_3 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') vstr-1.0.15_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') voucher-0.1_2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') uclcmd-0.1_2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') strongswan-5.6.2_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') sshlockout_pf-0.0.2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') smartmontools-6.6_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') siproxd-0.8.2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') scponly-4.8.20110526_2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') relayd-5.5.20140810_2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') readline-7.0.3_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') rate-0.9_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') python27-2.7.14_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') pftop-0.7_8 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') pfSense-pkg-siproxd-1.1.3_3 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') ntp-4.2.8p11 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') norm-1.5r6 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') nettle-3.4 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') mpd5-5.8_3 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') miniupnpd-1.9.20160113,1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') minicron-0.0.2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') lzo2-2.10_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') libucl-0.8.0 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') libosip2-5.0.0_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') libnghttp2-1.31.1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') libidn2-2.0.4 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') libiconv-1.14_11 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') libffi-3.2.1_2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') libevent-2.1.8_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') libedit-3.1.20170329_2,1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') libdaemon-0.14_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') ldns-1.7.0_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') json-c-0.13 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') isc-dhcp43-server-4.3.6P1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') isc-dhcp43-relay-4.3.6P1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') isc-dhcp43-client-4.3.6P1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') ipmitool-1.8.18_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') indexinfo-0.3.1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') idnkit-1.0_7 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') hostapd-2.6_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') gmp-6.1.2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') gettext-runtime-0.19.8.1_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') expiretable-0.6_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') expat-2.2.5 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') dmidecode-3.1_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') dhcpleases6-0.1_2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') dhcpleases-0.3_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') dhcp6-20080615.2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') cpustats-0.1_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') cpdup-1.18 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') clog-1.0.1_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') choparp-20150613 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') bwi-firmware-kmod-3.130.20 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') bsnmp-ucd-0.4.2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') bsnmp-regex-0.6_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') beep-1.0_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') ataidle-2.7.2 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11:x86:64') Number of packages to be removed: 8 Number of packages to be installed: 12 Number of packages to be upgraded: 10 Number of packages to be reinstalled: 60 Number of packages to be downgraded: 3 The operation will free 45 MiB. ```java code
-
[2.3.5-RELEASE][root@firewall]/usr/local/lib: ls -al librrd* -rwxr-xr-x 1 root wheel 327488 Dec 21 2015 librrd.so.2
Not sure if this helps.
-
Nope, it's solidly stuck in the middle of the 2.3.x -> 2.4.x upgrade.
Are you certain it has rebooted after the upgrade runs?
Can you try
pfSense-upgrade -d
again and capture the output? -
It has definitely been rebooting because I am accessing the shell via one of my servers on the internal network and I lose connection ... will grab some output for you.