Issues going from 2.7.0 to 2.7.2 - ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pfSense-repoc"
-
It has pulled in some newer pkg. Run:
pkg-static info -x pfsenseand see what pkg versions you have.You will likely have to force reinstall something. Try setting the pkg repo branch back to 2.7.0 and then run:
pkg-static -d update
If that completes successfully then you can try force reinstalling. If it shows an error that may also help diagnose what's happening. -
pkg-static info -x pfsense pfSense-2.7.0 pfSense-Status_Monitoring-php82-1.8_3 pfSense-base-2.7.0 pfSense-boot-2.7.0 pfSense-default-config-2.7.0 pfSense-kernel-pfSense-2.7.0 pfSense-pkg-WireGuard-0.2.0_2 pfSense-pkg-openvpn-client-export-1.9.2 pfSense-pkg-pfBlockerNG-devel-3.2.0_7 pfSense-rc-2.7.0 pfSense-repo-2.7.2 pfSense-repoc-20230912 pfSense-upgrade-1.2.1 php82-pfSense-module-0.95I'll switch the repo back to 2.7.0 later today and run that and see what happens.
-
Yup I would try force reinstalling pfSense-upgrade and pfSense-repo if access the 2.7.0 repo is successful.
-
@stephenw10 It appears that force reinstalling those three packages pkg, pfSense-repo, and pfSense-upgrade succeeded. Do I just reboot now and try switching the branch back to 2.7.2 and upgrade?
-
Rebooting doesn't hurt but you shouldn't need to. Just set the branch back to 2.7.2 and try to upgrade again.
-
@stephenw10 I tried the upgrade again, after switching the repo back to 2.7.2 and it failed again.
>>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 4 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: ....... done Processing entries: Processing entries............. done pfSense repository update completed. 550 packages processed. All repositories are up to date. >>> Upgrading -upgrade... failed. -
Ok try upgrading at the command line to get more output:
pfSense-upgrade -dAnd I mean at the real command line not the GUI command prompt.
-
@stephenw10 Got it.
ld-elf.so.1: Shared object "libcrypto.so.30" not found, required by "php" ld-elf.so.1: Shared object "libcrypto.so.30" not found, required by "php" ld-elf.so.1: Shared object "libcrypto.so.30" not found, required by "php" /usr/local/libexec/pfSense-upgrade: /usr/local/sbin/-repo-setup: not found >>> Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: . done pfSense-core repository update completed. 4 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: .... done Processing entries: Processing entries............. done pfSense repository update completed. 550 packages processed. All repositories are up to date. >>> Upgrading -upgrade... pkg-static: illegal option -- u Usage: pkg upgrade [-fInFqUy] [-r reponame] [-Cgix] <pkg-name> ... For more information see 'pkg help upgrade'. -
Hmm, well if you are local then reinstalling 2.7.2 clean is probably going to be fastest.
But otherwise I'd try switch the branch back and force reinstalling again and then try running the upgrade from the command line against but this time against the 2.7.0 branch
It should complete and return you are already on the latest version without any errors. -
I had the same issue. Went 2.7.0 first, then 2.7.2.
(Oops, the rest was lost)
I switched branches back and forth. Tried command line stuff as described on the upgrade help page - also on 2.7.0 branch. And at some point I was able to go to 2.7.2.
But I don't know what was the problem and I don't know what was the solution.
On another machine I just reinstalled with 2.7.2 because trying took too long.
