Unable to upgrate 23.09.1 to 24.11
-
Try running
pfSense-upgradedirectly after creating the symlink. -
Sorry for my belated response. The firewall cannot be taken offline immediately.
I executed the pfSense-upgrade command, but it did not upgrade the firewall. I verified the pfSense.conf symlink before and after command execution. It looks like the pfSense.conf again reverted to 23.09.1.
[23.09.1-RELEASE][...]/root: ls -ls /usr/local/etc/pkg/repos total 4 4 -rw-r--r-- 1 root wheel 26 Dec 6 2023 FreeBSD.conf 0 lrwxr-xr-x 1 root wheel 56 Mar 19 21:03 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_11.conf [23.09.1-RELEASE][...]/root: pfSense-upgrade >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 5 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: ....... done Processing entries: .......... done pfSense repository update completed. 739 packages processed. All repositories are up to date. Your packages are up to date [23.09.1-RELEASE][...]/root: ls -ls /usr/local/etc/pkg/repos total 4 4 -rw-r--r-- 1 root wheel 26 Dec 6 2023 FreeBSD.conf 0 lrwxr-xr-x 1 root wheel 62 Mar 19 21:03 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_1_rel.conf -
OK check the config file. What branch is it saving there?
Or change the branch then check the config history. You should see it switch from 23.09.1 to 24.11.
-
Update branch change to 24.11 after symlink creation.
[23.09.1-RELEASE][...]/root: ls -ls /usr/local/etc/pkg/repos total 4 4 -rw-r--r-- 1 root wheel 26 Dec 6 2023 FreeBSD.conf 0 lrwxr-xr-x 1 root wheel 56 Mar 19 23:01 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_11.conf [23.09.1-RELEASE]...]/root: cat /usr/local/etc/pkg/repos/pfSense.conf FreeBSD: { enabled: no } pfSense-core: { url: "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_11_amd64-core", mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/local/share/pfSense/keys/pkg", enabled: yes } pfSense: { url: "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_11_amd64-pfSense_plus_v24_11", mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/local/share/pfSense/keys/pkg", enabled: yes }Updated branch rollback to 23.09.1 after pfSense-upgrade execution
[23.09.1-RELEASE][...]/root: pfSense-upgrade >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 5 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: ..... done Processing entries: .......... done pfSense repository update completed. 739 packages processed. All repositories are up to date. Your packages are up to date [23.09.1-RELEASE][...]/root: cat /usr/local/etc/pkg/repos/pfSense.conf FreeBSD: { enabled: no } pfSense-core: { url: "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-core", mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/local/share/pfSense/keys/pkg", enabled: yes } pfSense: { url: "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v23_09_1_amd64-pfSense_plus_v23_09_1", mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/local/share/pfSense/keys/pkg", enabled: yes } [23.09.1-RELEASE][...]/root: -
But what does it show in the main pfSense config.xml file? That's where pfSense-upgrade it triggering it be pulled from.
I can't imagine why it would not be getting updated but....
-
I assume the main pfSense config.xml you are referring to is the file in /cf/conf/config.xml. <system/> section is the point of interest, I believe, as it contains information related to host, users, groups and webui.
<system> <optimization>normal</optimization> ... <already_run_config_upgrade></already_run_config_upgrade> <pkg_repo_conf_path>/usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_11.conf</pkg_repo_conf_path> <firmware> <disableautobe></disableautobe> </firmware> <gitsync> <repositoryurl></repositoryurl> <branch></branch> </gitsync> ... </system>The <pkg_repo_conf_path> directs to the 24.11 configuration file and the file has links to the 24.11 repo.
[23.09.1-RELEASE][...]/root: cat /usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_11.conf FreeBSD: { enabled: no } pfSense-core: { url: "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_11_amd64-core", mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/local/share/pfSense/keys/pkg", enabled: yes } pfSense: { url: "pkg+https://pfsense-plus-pkg.netgate.com/pfSense_plus-v24_11_amd64-pfSense_plus_v24_11", mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/local/share/pfSense/keys/pkg", enabled: yes } [23.09.1-RELEASE][...]/root:Should <firmware/>and <gitsync/> sections have values pointing to 24.11?
Or am I looking at the wrong place? -
No that's all correct. Weird.
What happens if you try upgrading to 24.03 first?
-
After changing the update branch to 24.03 via System => Update => Update Settings, the main pfSense config.xml's pkg_repo_conf_path changed to 24.03 repo.
<system> ... <pkg_repo_conf_path>/usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_03-rel.conf</pkg_repo_conf_path> ... </system>The symlink points to 23.09.1. I changed it manually and initiated an upgrade, but the result is the same and the main pfSense config.xml's pkg_repo_conf_path changed to 24.11 repo.
[23.09.1-RELEASE][...]/root: ls -ls /usr/local/etc/pkg/repos total 4 4 -rw-r--r-- 1 root wheel 26 Dec 6 2023 FreeBSD.conf 0 lrwxr-xr-x 1 root wheel 62 Mar 20 18:28 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_1_rel.conf [23.09.1-RELEASE][...]/root: rm /usr/local/etc/pkg/repos/pfSense.conf [23.09.1-RELEASE][...]/root: ln -s /usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_03-rel.conf /usr/local/etc/pkg/repos/pfSense.conf [23.09.1-RELEASE][...]/root: ls -ls /usr/local/etc/pkg/repos total 4 4 -rw-r--r-- 1 root wheel 26 Dec 6 2023 FreeBSD.conf 0 lrwxr-xr-x 1 root wheel 60 Mar 20 18:39 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_03-rel.conf [23.09.1-RELEASE][...]/root: pfSense-upgrade >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 5 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: ...... done Processing entries: .......... done pfSense repository update completed. 739 packages processed. All repositories are up to date. Your packages are up to date [23.09.1-RELEASE][...]/root: ls -ls /usr/local/etc/pkg/repos total 4 4 -rw-r--r-- 1 root wheel 26 Dec 6 2023 FreeBSD.conf 0 lrwxr-xr-x 1 root wheel 62 Mar 20 18:41 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_1_rel.conf<system> ... <pkg_repo_conf_path>/usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_11.conf</pkg_repo_conf_path> ... <system>The entire process is unclear to me since the upgrade process started with a lower version (24.03) but was completed with the lowest version (i.e., the original base version:23.09.1), and recorded in the config.xml with the latest version (24.11).
-
Ok I managed to replicate this locally. I think!
Just visiting the webgui upgrade page resets the symlink to the correct branch
So first set the repo branch back to 23.09.1. Then run:
pkg upgrade -f pfSense-repocAssuming it offers a downgrade allow that like:
[23.09.1-RELEASE][root@plusdev.stevew.lan]/root: pkg upgrade -f pfSense-repoc pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended Updating pfSense-core repository catalogue... Fetching meta.conf: 0% pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 3 package(s) will be affected (of 0 checked): Installed packages to be DOWNGRADED: libucl: 0.9.2_1 -> 0.8.2 [pfSense] pfSense-repoc: 20241121 -> 20230912 [pfSense] Installed packages to be REINSTALLED: uclcmd-0.2.20211204 [pfSense] (ABI changed: 'freebsd:15:x86:64' -> 'freebsd:14:x86:64') Number of packages to be reinstalled: 1 Number of packages to be downgraded: 2 Proceed with this action? [y/N]: y [1/3] Downgrading libucl from 0.9.2_1 to 0.8.2... [1/3] Extracting libucl-0.8.2: 100% 14 B 0.0kB/s 00:01 [2/3] Reinstalling uclcmd-0.2.20211204... [2/3] Extracting uclcmd-0.2.20211204: 100% 4 B 0.0kB/s 00:01 [3/3] Downgrading pfSense-repoc from 20241121 to 20230912... [3/3] Extracting pfSense-repoc-20230912: 100% 2 B 0.0kB/s 00:01Now set the upgrade branch back to 24.11 and try to upgrade again.
-
As you mentioned, I switched repo branch to 23.09.1 via System => Update => Update settings, and config.xml's pkg_repo_conf_path changed to 23.09.1.
<system> ... <pkg_repo_conf_path>/usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_1_rel.conf</pkg_repo_conf_path> ... </system>[23.09.1-RELEASE][...]/root: ls -ls /usr/local/etc/pkg/repos total 4 4 -rw-r--r-- 1 root wheel 26 Dec 6 2023 FreeBSD.conf 0 lrwxr-xr-x 1 root wheel 62 Mar 21 22:39 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_1_rel.conf [23.09.1-RELEASE][...]/root: pkg upgrade -f pfSense-repoc Updating pfSense-core repository catalogue... Fetching meta.conf: 0% pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The following 1 package(s) will be affected (of 0 checked): Installed packages to be REINSTALLED: pfSense-repoc-20230912 [pfSense] Number of packages to be reinstalled: 1 Proceed with this action? [y/N]: y [1/1] Reinstalling pfSense-repoc-20230912... [1/1] Extracting pfSense-repoc-20230912: 100% 2 B 0.0kB/s 00:01After updating the repo branch to 24.11, config.xml's pkg_repo_conf_path changed to 24.11, but symlink points to 23.09.1. Then I executed pfSense-upgrade.
[23.09.1-RELEASE][...]/root:ls -ls /usr/local/etc/pkg/repos total 4 4 -rw-r--r-- 1 root wheel 26 Dec 6 2023 FreeBSD.conf 0 lrwxr-xr-x 1 root wheel 62 Mar 21 22:41 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_1_rel.conf [23.09.1-RELEASE][...]/root: pfSense-upgrade >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 5 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: ..... done Processing entries: .......... done pfSense repository update completed. 739 packages processed. All repositories are up to date. Your packages are up to date [23.09.1-RELEASE][...]/root: ls -ls /usr/local/etc/pkg/repos total 4 4 -rw-r--r-- 1 root wheel 26 Dec 6 2023 FreeBSD.conf 0 lrwxr-xr-x 1 root wheel 62 Mar 21 22:41 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_1_rel.confAfter pfSense-upgrade, the symlink state and config.xml's pkg_repo_conf_path value are the same. The firewall is not upgraded.
-
Hmm, OK different problem then! You can see repoc was not downgraded.
OK try setting the repo back to 23.09.1 then running:
pkg upgrade -fDon't agree to the upgrades but check to see what packages it offers to downgrade.
-
I do not see any offers for downgrade, rather the packages for upgrade and reinstall are listed.
[23.09.1-RELEASE][...]/root: pkg upgrade -f Updating pfSense-core repository catalogue... Fetching meta.conf: 0% 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 (342 candidates): 100% 342 B 0.3kB/s 00:01 Processing candidates (342 candidates): 100% 342 B 0.3kB/s 00:01 The following 342 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: curl: 8.4.0 -> 8.6.0 [pfSense] unbound: 1.18.0_1 -> 1.19.1 [pfSense] Installed packages to be REINSTALLED: azure-agent-2.8.0.11 [pfSense] bash-5.2.15 [pfSense] beep-1.0_1 [pfSense] bind-tools-9.18.16 [pfSense] boost-libs-1.82.0_1 [pfSense] bsnmp-regex-0.6_2 [pfSense] bsnmp-ucd-0.4.5 [pfSense] bwi-firmware-kmod-3.130.20 [pfSense] ca_root_nss-3.92 [pfSense] ccid-1.5.1 [pfSense] check_reload_status-0.0.15 [pfSense] choparp-20150613 [pfSense] cpdup-1.22 [pfSense] cpustats-0.1_1 [pfSense] cyrus-sasl-2.1.28_1 [pfSense] dbus-1.14.6,1 [pfSense] devcpu-data-20230617_1 [pfSense] devcpu-data-amd-20230724 [pfSense] devcpu-data-intel-20230808 [pfSense] dhcp6-20080615.2_4 [pfSense] dhcpcd-10.0.2 [pfSense] dhcpleases-0.5_1 [pfSense] dhcpleases6-0.1_3 [pfSense] dmidecode-3.5 [pfSense] dnsmasq-2.89_1,1 [pfSense] dpinger-3.3 [pfSense] drm-510-kmod-5.10.163_7 [pfSense] expat-2.5.0 [pfSense] expiretable-0.6_2 [pfSense] filterdns-2.2 [pfSense] filterlog-0.1_10 [pfSense] gettext-runtime-0.22_1 [pfSense] glib-2.76.4,2 [pfSense] gmp-6.3.0 [pfSense] hostapd-2.10_5 [pfSense] icu-73.2,1 [pfSense] iftop-1.0.p4 [pfSense] igmpproxy-0.4,1 [pfSense] indexinfo-0.3.1 [pfSense] ipmitool-1.8.18_3 [pfSense] isc-dhcp44-client-4.4.3P1 [pfSense] isc-dhcp44-relay-4.4.3P1_4 [pfSense] isc-dhcp44-server-4.4.3P1_4 [pfSense] json-c-0.16 [pfSense] kea-2.4.0 [pfSense] ldns-1.8.3 [pfSense] libargon2-20190702 [pfSense] libedit-3.1.20221030,1 [pfSense] libevent-2.1.12 [pfSense] libffi-3.4.4 [pfSense] libgcrypt-1.10.2 [pfSense] libgpg-error-1.47 [pfSense] libiconv-1.17 [pfSense] libidn2-2.3.4 [pfSense] libinotify-20211018 [pfSense] libltdl-2.4.7 [pfSense] liblz4-1.9.4,1 [pfSense] libmcrypt-2.5.8_3 [pfSense] libnghttp2-1.55.1_1 [pfSense] libpsl-0.21.2_3 [pfSense] libsodium-1.0.18 [pfSense] libssh2-1.11.0_1,3 [pfSense] libucl-0.8.2 [pfSense] libunistring-1.1 [pfSense] libuv-1.46.0 [pfSense] libxml2-2.10.4 [pfSense] libxslt-1.1.37 [pfSense] libyaml-0.2.5 [pfSense] links-2.29_1,1 [pfSense] log4cplus-2.1.0 [pfSense] lua-resty-core-0.1.27 [pfSense] lua-resty-lrucache-0.13 [pfSense] luajit-openresty-2.1.20230410 [pfSense] lzo2-2.10_1 [pfSense] minicron-0.0.2 [pfSense] miniupnpd-2.3.3_1,1 [pfSense] mobile-broadband-provider-info-20230416 [pfSense] mpd5-5.9_16 [pfSense] mpdecimal-2.5.1 [pfSense] nginx-1.24.0_11,3 [pfSense] nss_ldap-1.265_14 [pfSense] ntp-4.2.8p17_1 [pfSense] oniguruma-6.9.8_1 [pfSense] openldap26-client-2.6.6 [pfSense] opensc-0.23.0_1 [pfSense] openvpn-2.6.8_1 [pfSense] openvpn-auth-script-1.0.0.3 [pfSense] pam_ldap-186_1 [pfSense] pam_mkhomedir-0.2 [pfSense] pcre-8.45_3 [pfSense] pcre2-10.42 [pfSense] pcsc-lite-2.0.0,2 [pfSense] perl5-5.34.1_3 [pfSense] pfSense-23.09.1 [pfSense] pfSense-Status_Monitoring-php82-1.8_3 [pfSense] pfSense-azure-0.12_4 [pfSense] pfSense-base-23.09.1 [pfSense-core] pfSense-boot-23.09.1 [pfSense-core] pfSense-composer-deps-0.1 [pfSense] pfSense-default-config-azure-23.09.1 [pfSense] pfSense-kernel-pfSense-23.09.1 [pfSense-core] pfSense-repo-23.09.1 [pfSense] pfSense-repoc-20230912 [pfSense] pfSense-upgrade-1.2.2_1 [pfSense] pftop-0.8_4 [pfSense] php82-8.2.11 [pfSense] php82-bcmath-8.2.11 [pfSense] php82-bz2-8.2.11 [pfSense] php82-ctype-8.2.11 [pfSense] php82-curl-8.2.11 [pfSense] php82-dom-8.2.11 [pfSense] php82-filter-8.2.11 [pfSense] php82-gettext-8.2.11 [pfSense] php82-gmp-8.2.11 [pfSense] php82-intl-8.2.11 [pfSense] php82-ldap-8.2.11 [pfSense] php82-libbe-0.1.4.1 [pfSense] php82-mbstring-8.2.11 [pfSense] php82-opcache-8.2.11 [pfSense] php82-openssl_x509_crl-1.3_3 [pfSense] php82-pcntl-8.2.11 [pfSense] php82-pdo-8.2.11 [pfSense] php82-pdo_sqlite-8.2.11 [pfSense] php82-pear-1.10.13 [pfSense] php82-pear-Auth_RADIUS-1.1.0_4 [pfSense] php82-pear-Cache_Lite-1.8.3,1 [pfSense] php82-pear-Crypt_CHAP-1.5.0_2 [pfSense] php82-pear-HTTP_Request2-2.5.1,1 [pfSense] php82-pear-Mail-1.5.0,1 [pfSense] php82-pear-Net_IPv6-1.3.0.b4_2 [pfSense] php82-pear-Net_SMTP-1.10.1 [pfSense] php82-pear-Net_Socket-1.2.2 [pfSense] php82-pear-Net_URL2-2.2.1 [pfSense] php82-pear-XML_RPC2-1.1.5 [pfSense] php82-pecl-mcrypt-1.0.6 [pfSense] php82-pecl-radius-1.4.0b1_2 [pfSense] php82-pecl-rrd-2.0.3 [pfSense] php82-pfSense-module-0.95 [pfSense] php82-phpseclib-2.0.17 [pfSense] php82-posix-8.2.11 [pfSense] php82-readline-8.2.11 [pfSense] php82-session-8.2.11 [pfSense] php82-shmop-8.2.11 [pfSense] php82-simplexml-8.2.11 [pfSense] php82-sockets-8.2.11 [pfSense] php82-sqlite3-8.2.11 [pfSense] php82-sysvmsg-8.2.11 [pfSense] php82-sysvsem-8.2.11 [pfSense] php82-sysvshm-8.2.11 [pfSense] php82-tokenizer-8.2.11 [pfSense] php82-xml-8.2.11 [pfSense] php82-xmlreader-8.2.11 [pfSense] php82-xmlwriter-8.2.11 [pfSense] php82-zlib-8.2.11 [pfSense] pkcs11-helper-1.29.0 [pfSense] pkg-1.20.8_2 [pfSense] py311-adal-1.2.7_2 [pfSense] py311-aiohttp-3.8.4_1 [pfSense] py311-aiosignal-1.3.1 [pfSense] py311-antlr4-python3-runtime-4.9,1 [pfSense] py311-anyio-3.7.1 [pfSense] py311-applicationinsights-0.11.10 [pfSense] py311-argcomplete-2.1.2 [pfSense] py311-async_generator-1.10 [pfSense] py311-async_timeout-4.0.2 [pfSense] py311-attrs-23.1.0 [pfSense] py311-azure-appconfiguration-1.1.1 [pfSense] py311-azure-batch-13.0.0 [pfSense] py311-azure-cli-2.50.0 [pfSense] py311-azure-cli-base-1.0.0 [pfSense] py311-azure-cli-core-2.50.0 [pfSense] py311-azure-cli-telemetry-1.0.8 [pfSense] py311-azure-common-1.1.27 [pfSense] py311-azure-core-1.28.0 [pfSense] py311-azure-cosmos-3.2.0 [pfSense] py311-azure-datalake-store-0.0.53 [pfSense] py311-azure-graphrbac-0.61.1 [pfSense] py311-azure-keyvault-1.1.0 [pfSense] py311-azure-keyvault-administration-4.3.0 [pfSense] py311-azure-keyvault-certificates-4.7.0 [pfSense] py311-azure-keyvault-keys-4.8.0 [pfSense] py311-azure-keyvault-secrets-4.7.0 [pfSense] py311-azure-loganalytics-0.1.1 [pfSense] py311-azure-mgmt-advisor-9.0.0 [pfSense] py311-azure-mgmt-apimanagement-4.0.0 [pfSense] py311-azure-mgmt-appconfiguration-3.0.0 [pfSense] py311-azure-mgmt-appcontainers-2.0.0 [pfSense] py311-azure-mgmt-applicationinsights-1.0.0 [pfSense] py311-azure-mgmt-authorization-3.0.0 [pfSense] py311-azure-mgmt-batch-17.0.0 [pfSense] py311-azure-mgmt-batchai-7.0.0.b1 [pfSense] py311-azure-mgmt-billing-6.0.0 [pfSense] py311-azure-mgmt-botservice-2.0.0.b3 [pfSense] py311-azure-mgmt-cdn-12.0.0 [pfSense] py311-azure-mgmt-cognitiveservices-13.3.0 [pfSense] py311-azure-mgmt-compute-29.1.0 [pfSense] py311-azure-mgmt-consumption-3.0.0 [pfSense] py311-azure-mgmt-containerinstance-10.1.0 [pfSense] py311-azure-mgmt-containerregistry-10.1.0 [pfSense] py311-azure-mgmt-containerservice-24.0.0 [pfSense] py311-azure-mgmt-core-1.3.2 [pfSense] py311-azure-mgmt-cosmosdb-9.2.0,1 [pfSense] py311-azure-mgmt-databoxedge-1.0.0 [pfSense] py311-azure-mgmt-datalake-analytics-0.6.0 [pfSense] py311-azure-mgmt-datalake-store-0.5.0 [pfSense] py311-azure-mgmt-datamigration-10.0.0 [pfSense] py311-azure-mgmt-devtestlabs-4.0.0 [pfSense] py311-azure-mgmt-dns-8.0.0 [pfSense] py311-azure-mgmt-eventgrid-10.2.0.b2 [pfSense] py311-azure-mgmt-eventhub-10.1.0 [pfSense] py311-azure-mgmt-extendedlocation-1.0.0.b2 [pfSense] py311-azure-mgmt-hdinsight-9.0.0 [pfSense] py311-azure-mgmt-imagebuilder-1.2.0 [pfSense] py311-azure-mgmt-iotcentral-10.0.0.b1 [pfSense] py311-azure-mgmt-iothub-2.3.0 [pfSense] py311-azure-mgmt-iothubprovisioningservices-1.1.0 [pfSense] py311-azure-mgmt-keyvault-10.2.2 [pfSense] py311-azure-mgmt-kusto-0.5.0 [pfSense] py311-azure-mgmt-loganalytics-13.0.0.b4 [pfSense] py311-azure-mgmt-managedservices-1.0.0 [pfSense] py311-azure-mgmt-managementgroups-1.0.0 [pfSense] py311-azure-mgmt-maps-2.0.0 [pfSense] py311-azure-mgmt-marketplaceordering-1.1.0 [pfSense] py311-azure-mgmt-media-9.0.0 [pfSense] py311-azure-mgmt-monitor-5.0.0 [pfSense] py311-azure-mgmt-msi-7.0.0 [pfSense] py311-azure-mgmt-netapp-10.0.0 [pfSense] py311-azure-mgmt-policyinsights-1.1.0.b2 [pfSense] py311-azure-mgmt-privatedns-1.0.0 [pfSense] py311-azure-mgmt-rdbms-10.2.0.b10 [pfSense] py311-azure-mgmt-recoveryservices-2.4.0 [pfSense] py311-azure-mgmt-recoveryservicesbackup-6.0.0 [pfSense] py311-azure-mgmt-redhatopenshift-1.2.0 [pfSense] py311-azure-mgmt-redis-14.1.0 [pfSense] py311-azure-mgmt-relay-0.2.0 [pfSense] py311-azure-mgmt-resource-23.1.0.b2 [pfSense] py311-azure-mgmt-search-9.0.0 [pfSense] py311-azure-mgmt-security-3.0.0 [pfSense] py311-azure-mgmt-servicebus-8.2.0 [pfSense] py311-azure-mgmt-servicefabric-1.0.0 [pfSense] py311-azure-mgmt-servicefabricmanagedclusters-1.0.0 [pfSense] py311-azure-mgmt-servicelinker-1.2.0.b1 [pfSense] py311-azure-mgmt-signalr-1.1.0 [pfSense] py311-azure-mgmt-sql-4.0.0.b10 [pfSense] py311-azure-mgmt-sqlvirtualmachine-1.0.0.b5 [pfSense] py311-azure-mgmt-storage-21.0.0 [pfSense] py311-azure-mgmt-synapse-2.1.0.b5 [pfSense] py311-azure-mgmt-trafficmanager-1.0.0 [pfSense] py311-azure-mgmt-web-7.0.0 [pfSense] py311-azure-multiapi-storage-1.2.0 [pfSense] py311-azure-storage-common-2.1.0 [pfSense] py311-azure-synapse-accesscontrol-0.5.0 [pfSense] py311-azure-synapse-artifacts-0.15.0 [pfSense] py311-azure-synapse-managedprivateendpoints-0.4.0 [pfSense] py311-azure-synapse-spark-0.2.0 [pfSense] py311-bcrypt-3.2.2 [pfSense] py311-blinker-1.6.2 [pfSense] py311-certifi-2023.5.7 [pfSense] py311-cffi-1.15.1 [pfSense] py311-charset-normalizer-3.2.0 [pfSense] py311-colorama-0.4.5 [pfSense] py311-cryptography-3.4.8_1,1 [pfSense] py311-curio-1.6 [pfSense] py311-dateutil-2.8.2 [pfSense] py311-deprecated-1.2.14 [pfSense] py311-fabric-3.2.1,1 [pfSense] py311-frozenlist-1.4.0 [pfSense] py311-humanfriendly-10.0 [pfSense] py311-idna-3.4_1 [pfSense] py311-invoke-2.2.0 [pfSense] py311-isodate-0.6.1 [pfSense] py311-javaproperties-0.5.2 [pfSense] py311-jmespath-1.0.1 [pfSense] py311-jsondiff-2.0.0 [pfSense] py311-knack-0.10.1 [pfSense] py311-libzfs-1.1.2023020700 [pfSense] py311-msal-1.22.0 [pfSense] py311-msal-extensions-1.0.0 [pfSense] py311-msrest-0.7.1 [pfSense] py311-msrestazure-0.6.4 [pfSense] py311-multidict-6.0.4 [pfSense] py311-oauthlib-3.2.2 [pfSense] py311-openssl-21.0.0,1 [pfSense] py311-outcome-1.2.0 [pfSense] py311-packaging-23.1 [pfSense] py311-paramiko-2.11.0_1 [pfSense] py311-pathlib2-2.3.7 [pfSense] py311-pkginfo-1.9.6 [pfSense] py311-portalocker-2.3.2 [pfSense] py311-psutil-5.9.5 [pfSense] py311-pyasn1-0.5.0 [pfSense] py311-pycparser-2.21 [pfSense] py311-pygithub-1.57 [pfSense] py311-pygments-2.16.1 [pfSense] py311-pyjwt-2.7.0_1 [pfSense] py311-pynacl-1.5.0 [pfSense] py311-pysocks-1.7.1 [pfSense] py311-python-socks-2.3.0 [pfSense] py311-requests-2.31.0 [pfSense] py311-requests-oauthlib-1.3.1 [pfSense] py311-scp-0.14.4 [pfSense] py311-semver-3.0.1 [pfSense] py311-setuptools-63.1.0_1 [pfSense] py311-six-1.16.0 [pfSense] py311-sniffio-1.3.0 [pfSense] py311-sortedcontainers-2.4.0 [pfSense] py311-sshtunnel-0.1.5 [pfSense] py311-tabulate-0.8.9 [pfSense] py311-trio-0.22.2 [pfSense] py311-typing-extensions-4.7.1 [pfSense] py311-urllib3-1.26.16,1 [pfSense] py311-websocket-client-1.4.2 [pfSense] py311-wheel-0.41.0 [pfSense] py311-wrapt-1.15.0 [pfSense] py311-wsaccel-0.6.4 [pfSense] py311-xmltodict-0.13.0 [pfSense] py311-yaml-6.0 [pfSense] py311-yarl-1.9.2 [pfSense] python311-3.11.4 [pfSense] qstats-0.2 [pfSense] radvd-2.19_2 [pfSense] rate-0.9_2 [pfSense] readline-8.2.1 [pfSense] rrdtool-1.8.0_2 [pfSense] scponly-4.8.20110526_5 [pfSense] smartmontools-7.4 [pfSense] sqlite3-3.42.0,1 [pfSense] ssh_tunnel_shell-0.2_1 [pfSense] sshguard-2.4.2_2,1 [pfSense] strongswan-5.9.11_3 [pfSense] sudo-1.9.14p3 [pfSense] uclcmd-0.2.20211204 [pfSense] voucher-0.1_3 [pfSense] vstr-1.0.15_1 [pfSense] whois-5.5.7 [pfSense] wol-0.7.1_4 [pfSense] wpa_supplicant-2.10_6 [pfSense] wrapalixresetbutton-0.0.13 [pfSense] xinetd-2.3.15_2 [pfSense] zstd-1.5.5 [pfSense] Number of packages to be upgraded: 2 Number of packages to be reinstalled: 340 366 MiB to be downloaded. Proceed with this action? [y/N]: N [23.09.1-RELEASE][...]/root: -
Hmm, odd.
Well I would probably just install 24.11 clean and restore the config at that point. However you could try agreeing with that and reinstalling all the packages.
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#forced-pkg-reinstall
-
P patient0 referenced this topic on
-
Reinstalling all the packages did not help, the problem still persists.
System Update page shows 'Up to date' status.
Symlink points to 23.09.1
[23.09.1-RELEASE][...]/root: ls -ls /usr/local/etc/pkg/repos total 4 4 -rw-r--r-- 1 root wheel 26 Dec 6 2023 FreeBSD.conf 0 lrwxr-xr-x 1 root wheel 62 Mar 22 22:41 pfSense.conf -> /usr/local/etc/pfSense/pkg/repos/pfSense-repo-23_09_1_rel.confpfSense config.xml's pkg_repo_conf_path has 24.11
<system> ... <pkg_repo_conf_path>/usr/local/etc/pfSense/pkg/repos/pfSense-repo-24_11.conf</pkg_repo_conf_path> ... </system> -
Then I can only really recommend reinstalling 24.11. Given the unexpected behaviour I would want to do that even if you did fins a way to force an upgrade.
-
Thank you very much for your response and your assistance has been highly invaluable. It helped greatly to understand the troubleshooting though the problem was not solved. I will go for the clean installation.
Would you tell me the possible scenario(s) that might have caused this situation? It will help to prevent the reoccurrence of the same problem.
-
Not really! If I could I'd try to replicate it that way but so far I've been unable to.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.