Update issues
-
Not sure if anyone else has noticed this: Currently running 2.4 RC built on Tue Oct 03 13:49:31 CDT 2017. There's an upgrade available, "Version 2.4.0.r.20171004.0814 is available." Like I do most days at the moment, clicked update, it takes me to the update screen, finishes saying "success rebooting in 10 seconds" sure enough reboots. But then it hasn't actually changed version, and still says update available.
Any steps to help solve/debug? I've had very few other issues with 2.4 so far!
-
Perhaps you could use option 13 from console to get some useful information.
-
Current 2.4RC build for me is Wed Oct 04 12:05:18 CDT 2017. But I had to do two updates in a row to get there, first one only updated kernel pfsense-rc and base system, the second one updated system packages.
-
Perhaps you could use option 13 from console to get some useful information.
Any other way? I run it headless on a machine without IPMI
-
It works just fine over SSH.
-
It works just fine over SSH.
Enter an option: 13 >>> 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. The following 27 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: pecl-rrd-1.1.3_4 New packages to be INSTALLED: pecl-rrd1: 1.1.3 [pfSense] Installed packages to be UPGRADED: unbound: 1.6.3 -> 1.6.6 [pfSense] strongswan: 5.5.3 -> 5.6.0 [pfSense] sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense] rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense] python27: 2.7.13_7 -> 2.7.14 [pfSense] postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense] pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense] pear: 1.10.3 -> 1.10.5 [pfSense] nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense] mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense] mpd5: 5.8_1 -> 5.8_2 [pfSense] libzmq4: 4.1.5 -> 4.2.2 [pfSense] libnghttp2: 1.23.1 -> 1.26.0 [pfSense] liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense] libidn2: 2.0.3 -> 2.0.4 [pfSense] libiconv: 1.14_10 -> 1.14_11 [pfSense] libffi: 3.2.1 -> 3.2.1_1 [pfSense] isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense] isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense] isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense] glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense] Installed packages to be REINSTALLED: pkg-1.10.1_1 [pfSense] pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1) Number of packages to be removed: 1 Number of packages to be installed: 1 Number of packages to be upgraded: 23 Number of packages to be reinstalled: 2 The process will require 3 MiB more space. 3 MiB to be downloaded. **** WARNING **** Reboot will be required!! Proceed with upgrade? (y/N) y >>> Downloading upgrade packages... 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 (25 candidates): .......... done Processing candidates (25 candidates): .......... done Checking integrity... done (1 conflicting) - pecl-rrd1-1.1.3 [pfSense] conflicts with pecl-rrd-1.1.3_4 [installed] on /usr/local/lib/php/20131226/rrd.so Checking integrity... done (0 conflicting) The following 26 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: pecl-rrd-1.1.3_4 New packages to be INSTALLED: pecl-rrd1: 1.1.3 [pfSense] Installed packages to be UPGRADED: unbound: 1.6.3 -> 1.6.6 [pfSense] strongswan: 5.5.3 -> 5.6.0 [pfSense] sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense] rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense] python27: 2.7.13_7 -> 2.7.14 [pfSense] postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense] pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense] pear: 1.10.3 -> 1.10.5 [pfSense] nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense] mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense] mpd5: 5.8_1 -> 5.8_2 [pfSense] libzmq4: 4.1.5 -> 4.2.2 [pfSense] libnghttp2: 1.23.1 -> 1.26.0 [pfSense] liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense] libidn2: 2.0.3 -> 2.0.4 [pfSense] libiconv: 1.14_10 -> 1.14_11 [pfSense] libffi: 3.2.1 -> 3.2.1_1 [pfSense] isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense] isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense] isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense] glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense] Installed packages to be REINSTALLED: pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1) Number of packages to be removed: 1 Number of packages to be installed: 1 Number of packages to be upgraded: 23 Number of packages to be reinstalled: 1 The process will require 3 MiB more space. Upgrade is complete. Rebooting in 10 seconds. Broadcast Message from admin@pfSense.home (/dev/pts/0) at 21:19 BST... Upgrade is complete. Rebooting in 10 seconds. *** Welcome to pfSense 2.4.0-RC (amd64) on pfSense *** WAN (wan) -> pppoe0 -> v4/PPPoE: **.***.**.***/** LAN (lan) -> igb1 -> v4: ***.***.*.*/** v6/t6: ****:****:****:****:***:****:****:****/** PROTONVPN (opt1) -> ovpnc2 -> v4: **.*.*.*/** 0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option:It then terminated the putty session, rebooted the box - and afterwards hadn't upgraded again. Still saying update available
-
There's upgrade log in /cf/conf so post it here.
-
I'm having the exact same problem. I'm currently on 2.4.0.r.20171003.1349. It says the Latest Base System is 2.4.0.r.20171004.0814. When cat /cf/conf/upgrade_log.txt, all it says is "2.4.0.r.20171004.0814 version of pfSense is available"
Attached is a capture of the console log when I try to update.
[2017-10-04 20-20-33 CP2104 USB to UART Bridge Controller.txt](/public/imported_attachments/1/2017-10-04 20-20-33 CP2104 USB to UART Bridge Controller.txt)
-
Not sure I know what's going on but, this might be part of the problem:
Checking integrity... done (1 conflicting) - pecl-rrd1-1.1.3 [pfSense] conflicts with pecl-rrd-1.1.3_4 [installed] on /usr/local/lib/php/20131226/rrd.soSo maybe try renaming or removing that /usr/local/lib/php/20131226/rrd.so file before upgrading. Not sure on that but it stood out.
and (unrelated) … that WAN subnet ... a /21? wow. send some broadcasts out on that WAN connection for some fun times. Guess that's how Cox is doing it these days?
-
There's upgrade log in /cf/conf so post it here.
I can also get you the update log once I'm home this evening.
-
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_v2_4_0/All/pkg-1.10.1_1.txz: No address recordThere is the problem. Somehow when it reboots it can't fetch pkg. I thought we had some code to prevent that from happening…
Before you try the upgrade again, run "pkg fetch -y pkg"
-
Is that the DNS A vs. SRV record thing? pkg supposed to use SRV record but maybe sometimes upstream DNS isn't returning the right responses?
-
Is that the DNS A vs. SRV record thing? pkg supposed to use SRV record but maybe sometimes upstream DNS isn't returning the right responses?
No, at that point in the upgrade there is zero connectivity, the package files should have all been fetched/verified before the reboot so it shouldn't need to reach anything. But it tried to reinstall pkg and failed, so that must mean the local cached copy of the pkg archive wasn't there.
-
It works just fine over SSH.
Enter an option: 13 >>> 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. The following 27 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: pecl-rrd-1.1.3_4 New packages to be INSTALLED: pecl-rrd1: 1.1.3 [pfSense] Installed packages to be UPGRADED: unbound: 1.6.3 -> 1.6.6 [pfSense] strongswan: 5.5.3 -> 5.6.0 [pfSense] sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense] rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense] python27: 2.7.13_7 -> 2.7.14 [pfSense] postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense] pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense] pear: 1.10.3 -> 1.10.5 [pfSense] nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense] mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense] mpd5: 5.8_1 -> 5.8_2 [pfSense] libzmq4: 4.1.5 -> 4.2.2 [pfSense] libnghttp2: 1.23.1 -> 1.26.0 [pfSense] liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense] libidn2: 2.0.3 -> 2.0.4 [pfSense] libiconv: 1.14_10 -> 1.14_11 [pfSense] libffi: 3.2.1 -> 3.2.1_1 [pfSense] isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense] isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense] isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense] glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense] Installed packages to be REINSTALLED: pkg-1.10.1_1 [pfSense] pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1) Number of packages to be removed: 1 Number of packages to be installed: 1 Number of packages to be upgraded: 23 Number of packages to be reinstalled: 2 The process will require 3 MiB more space. 3 MiB to be downloaded. **** WARNING **** Reboot will be required!! Proceed with upgrade? (y/N) y >>> Downloading upgrade packages... 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 (25 candidates): .......... done Processing candidates (25 candidates): .......... done Checking integrity... done (1 conflicting) - pecl-rrd1-1.1.3 [pfSense] conflicts with pecl-rrd-1.1.3_4 [installed] on /usr/local/lib/php/20131226/rrd.so Checking integrity... done (0 conflicting) The following 26 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: pecl-rrd-1.1.3_4 New packages to be INSTALLED: pecl-rrd1: 1.1.3 [pfSense] Installed packages to be UPGRADED: unbound: 1.6.3 -> 1.6.6 [pfSense] strongswan: 5.5.3 -> 5.6.0 [pfSense] sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense] rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense] python27: 2.7.13_7 -> 2.7.14 [pfSense] postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense] pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense] pear: 1.10.3 -> 1.10.5 [pfSense] nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense] mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense] mpd5: 5.8_1 -> 5.8_2 [pfSense] libzmq4: 4.1.5 -> 4.2.2 [pfSense] libnghttp2: 1.23.1 -> 1.26.0 [pfSense] liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense] libidn2: 2.0.3 -> 2.0.4 [pfSense] libiconv: 1.14_10 -> 1.14_11 [pfSense] libffi: 3.2.1 -> 3.2.1_1 [pfSense] isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense] isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense] isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense] glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense] Installed packages to be REINSTALLED: pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1) Number of packages to be removed: 1 Number of packages to be installed: 1 Number of packages to be upgraded: 23 Number of packages to be reinstalled: 1 The process will require 3 MiB more space. Upgrade is complete. Rebooting in 10 seconds. Broadcast Message from admin@pfSense.home (/dev/pts/0) at 21:19 BST... Upgrade is complete. Rebooting in 10 seconds. *** Welcome to pfSense 2.4.0-RC (amd64) on pfSense *** WAN (wan) -> pppoe0 -> v4/PPPoE: **.***.**.***/** LAN (lan) -> igb1 -> v4: ***.***.*.*/** v6/t6: ****:****:****:****:***:****:****:****/** PROTONVPN (opt1) -> ovpnc2 -> v4: **.*.*.*/** 0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option:It then terminated the putty session, rebooted the box - and afterwards hadn't upgraded again. Still saying update available
It's hard to reproduce but if your system is still in this state can you run the following command and send me the output?
pkg -ddd upgrade -n
Thanks
-
I'm having the exact same problem. I'm currently on 2.4.0.r.20171003.1349. It says the Latest Base System is 2.4.0.r.20171004.0814. When cat /cf/conf/upgrade_log.txt, all it says is "2.4.0.r.20171004.0814 version of pfSense is available"
Attached is a capture of the console log when I try to update.
If your system is still in this state can you please run following commands and send me output?
pkg -ddd upgrade -n
pkg -ddd upgrade -Fn
Thanks
-
I had the same issue. Running pkg fetch -y pkg from an ssh session resolved the problem.
-
It works just fine over SSH.
Enter an option: 13 >>> 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. The following 27 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: pecl-rrd-1.1.3_4 New packages to be INSTALLED: pecl-rrd1: 1.1.3 [pfSense] Installed packages to be UPGRADED: unbound: 1.6.3 -> 1.6.6 [pfSense] strongswan: 5.5.3 -> 5.6.0 [pfSense] sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense] rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense] python27: 2.7.13_7 -> 2.7.14 [pfSense] postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense] pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense] pear: 1.10.3 -> 1.10.5 [pfSense] nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense] mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense] mpd5: 5.8_1 -> 5.8_2 [pfSense] libzmq4: 4.1.5 -> 4.2.2 [pfSense] libnghttp2: 1.23.1 -> 1.26.0 [pfSense] liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense] libidn2: 2.0.3 -> 2.0.4 [pfSense] libiconv: 1.14_10 -> 1.14_11 [pfSense] libffi: 3.2.1 -> 3.2.1_1 [pfSense] isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense] isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense] isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense] glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense] Installed packages to be REINSTALLED: pkg-1.10.1_1 [pfSense] pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1) Number of packages to be removed: 1 Number of packages to be installed: 1 Number of packages to be upgraded: 23 Number of packages to be reinstalled: 2 The process will require 3 MiB more space. 3 MiB to be downloaded. **** WARNING **** Reboot will be required!! Proceed with upgrade? (y/N) y >>> Downloading upgrade packages... 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 (25 candidates): .......... done Processing candidates (25 candidates): .......... done Checking integrity... done (1 conflicting) - pecl-rrd1-1.1.3 [pfSense] conflicts with pecl-rrd-1.1.3_4 [installed] on /usr/local/lib/php/20131226/rrd.so Checking integrity... done (0 conflicting) The following 26 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: pecl-rrd-1.1.3_4 New packages to be INSTALLED: pecl-rrd1: 1.1.3 [pfSense] Installed packages to be UPGRADED: unbound: 1.6.3 -> 1.6.6 [pfSense] strongswan: 5.5.3 -> 5.6.0 [pfSense] sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense] rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense] python27: 2.7.13_7 -> 2.7.14 [pfSense] postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense] pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense] pear: 1.10.3 -> 1.10.5 [pfSense] nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense] mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense] mpd5: 5.8_1 -> 5.8_2 [pfSense] libzmq4: 4.1.5 -> 4.2.2 [pfSense] libnghttp2: 1.23.1 -> 1.26.0 [pfSense] liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense] libidn2: 2.0.3 -> 2.0.4 [pfSense] libiconv: 1.14_10 -> 1.14_11 [pfSense] libffi: 3.2.1 -> 3.2.1_1 [pfSense] isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense] isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense] isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense] glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense] Installed packages to be REINSTALLED: pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1) Number of packages to be removed: 1 Number of packages to be installed: 1 Number of packages to be upgraded: 23 Number of packages to be reinstalled: 1 The process will require 3 MiB more space. Upgrade is complete. Rebooting in 10 seconds. Broadcast Message from admin@pfSense.home (/dev/pts/0) at 21:19 BST... Upgrade is complete. Rebooting in 10 seconds. *** Welcome to pfSense 2.4.0-RC (amd64) on pfSense *** WAN (wan) -> pppoe0 -> v4/PPPoE: **.***.**.***/** LAN (lan) -> igb1 -> v4: ***.***.*.*/** v6/t6: ****:****:****:****:***:****:****:****/** PROTONVPN (opt1) -> ovpnc2 -> v4: **.*.*.*/** 0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option:It then terminated the putty session, rebooted the box - and afterwards hadn't upgraded again. Still saying update available
It's hard to reproduce but if your system is still in this state can you run the following command and send me the output?
pkg -ddd upgrade -n
Thanks
I just forgot to ask you to run a 2nd command as well:
pkg -ddd upgrade -Fn
-
It works just fine over SSH.
Enter an option: 13 >>> 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. The following 27 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: pecl-rrd-1.1.3_4 New packages to be INSTALLED: pecl-rrd1: 1.1.3 [pfSense] Installed packages to be UPGRADED: unbound: 1.6.3 -> 1.6.6 [pfSense] strongswan: 5.5.3 -> 5.6.0 [pfSense] sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense] rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense] python27: 2.7.13_7 -> 2.7.14 [pfSense] postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense] pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense] pear: 1.10.3 -> 1.10.5 [pfSense] nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense] mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense] mpd5: 5.8_1 -> 5.8_2 [pfSense] libzmq4: 4.1.5 -> 4.2.2 [pfSense] libnghttp2: 1.23.1 -> 1.26.0 [pfSense] liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense] libidn2: 2.0.3 -> 2.0.4 [pfSense] libiconv: 1.14_10 -> 1.14_11 [pfSense] libffi: 3.2.1 -> 3.2.1_1 [pfSense] isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense] isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense] isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense] glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense] Installed packages to be REINSTALLED: pkg-1.10.1_1 [pfSense] pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1) Number of packages to be removed: 1 Number of packages to be installed: 1 Number of packages to be upgraded: 23 Number of packages to be reinstalled: 2 The process will require 3 MiB more space. 3 MiB to be downloaded. **** WARNING **** Reboot will be required!! Proceed with upgrade? (y/N) y >>> Downloading upgrade packages... 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 (25 candidates): .......... done Processing candidates (25 candidates): .......... done Checking integrity... done (1 conflicting) - pecl-rrd1-1.1.3 [pfSense] conflicts with pecl-rrd-1.1.3_4 [installed] on /usr/local/lib/php/20131226/rrd.so Checking integrity... done (0 conflicting) The following 26 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: pecl-rrd-1.1.3_4 New packages to be INSTALLED: pecl-rrd1: 1.1.3 [pfSense] Installed packages to be UPGRADED: unbound: 1.6.3 -> 1.6.6 [pfSense] strongswan: 5.5.3 -> 5.6.0 [pfSense] sqlite3: 3.20.0_1 -> 3.20.1_1 [pfSense] rrdtool: 1.6.0_1 -> 1.7.0_1 [pfSense] python27: 2.7.13_7 -> 2.7.14 [pfSense] postgresql95-client: 9.5.8_1 -> 9.5.9 [pfSense] pfSense-default-config: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense-base: 2.4.0.r.20171003.1349 -> 2.4.0.r.20171004.1205 [pfSense-core] pfSense: 2.4.0.r.20171003.1203 -> 2.4.0.r.20171004.0814 [pfSense] pear: 1.10.3 -> 1.10.5 [pfSense] nginx: 1.12.1,2 -> 1.12.1_1,2 [pfSense] mysql56-client: 5.6.37 -> 5.6.37_1 [pfSense] mpd5: 5.8_1 -> 5.8_2 [pfSense] libzmq4: 4.1.5 -> 4.2.2 [pfSense] libnghttp2: 1.23.1 -> 1.26.0 [pfSense] liblz4: 1.7.5,1 -> 1.8.0,1 [pfSense] libidn2: 2.0.3 -> 2.0.4 [pfSense] libiconv: 1.14_10 -> 1.14_11 [pfSense] libffi: 3.2.1 -> 3.2.1_1 [pfSense] isc-dhcp43-server: 4.3.5 -> 4.3.6_1 [pfSense] isc-dhcp43-relay: 4.3.5 -> 4.3.6 [pfSense] isc-dhcp43-client: 4.3.5 -> 4.3.6 [pfSense] glib: 2.50.2_3,1 -> 2.50.2_6,1 [pfSense] Installed packages to be REINSTALLED: pfSense-Status_Monitoring-1.7.2 [pfSense] (direct dependency changed: pecl-rrd1) Number of packages to be removed: 1 Number of packages to be installed: 1 Number of packages to be upgraded: 23 Number of packages to be reinstalled: 1 The process will require 3 MiB more space. Upgrade is complete. Rebooting in 10 seconds. Broadcast Message from admin@pfSense.home (/dev/pts/0) at 21:19 BST... Upgrade is complete. Rebooting in 10 seconds. *** Welcome to pfSense 2.4.0-RC (amd64) on pfSense *** WAN (wan) -> pppoe0 -> v4/PPPoE: **.***.**.***/** LAN (lan) -> igb1 -> v4: ***.***.*.*/** v6/t6: ****:****:****:****:***:****:****:****/** PROTONVPN (opt1) -> ovpnc2 -> v4: **.*.*.*/** 0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option:It then terminated the putty session, rebooted the box - and afterwards hadn't upgraded again. Still saying update available
It's hard to reproduce but if your system is still in this state can you run the following command and send me the output?
pkg -ddd upgrade -n
Thanks
I just forgot to ask you to run a 2nd command as well:
pkg -ddd upgrade -Fn
That was an epic output! Both commands have been run and output is attached. I am now running the other command to see if it fixes the issue
-
Sure enough, running "pkg fetch -y pkg" and then updating let me update successfully. Thanks for the help - and hopefully the output should be vaguely useful.
-
I'm having the exact same problem. I'm currently on 2.4.0.r.20171003.1349. It says the Latest Base System is 2.4.0.r.20171004.0814. When cat /cf/conf/upgrade_log.txt, all it says is "2.4.0.r.20171004.0814 version of pfSense is available"
Attached is a capture of the console log when I try to update.
If your system is still in this state can you please run following commands and send me output?
pkg -ddd upgrade -n
pkg -ddd upgrade -Fn
Thanks
If you still have the possibility of run this test for me, please add an extra -d to have more debug. It's hard to reproduce the problem
pkg -dddd upgrade -n
pkg -dddd upgrade -Fn
