PFSense 2.6.0: ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/sbin/pkg not found

DBMandrake

Hi All,

Another problem I've just noticed which may be related to my other post is that the pkg command seems to be broken on 2.6.0 now as well, with any use of the pkg command reporting what seems to be a libc dynamic linker error:

pkg install nano
ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/sbin/pkg not found

I've checked 4 different 2.6.0 systems and they are all exhibiting the same issue. None of them have had any updates installed by me but it seems that some sort of stealth update must have happened in the background to break this.

Anyone else seeing this issue or know of a fix ?

DBMandrake

Found a solution to this. It is indeed related to the issue in my other post. Quoting a comment I made over there:

"Due to the changes pushed to the repositories as part of the 2.7.0 release, 2.7.0 is now listed as "Current", so the Update settings are automatically trying to access 2.7.0 repositories even though the system is still running 2.6.0... seems a bit daft to me...

Go to System->Update->Update Settings, manually change the Branch to 2.6.0 then save settings."

After the branch is changed back to 2.6.0 log in with SSH and run:

pkg bootstrap -f

This will re-download pkg and you should find the pkg command works again:

pkg install nano
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.
pkg: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
Updating database digests format: 100%
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
        nano: 5.9 [pfSense]

Number of packages to be installed: 1

The process will require 2 MiB more space.
533 KiB to be downloaded.

Proceed with this action? [y/N]:

It looks like the repository changing "current" from 2.6.0 to 2.7.0 caused the pkg system to automatically update the database in the background during some sort of automated background process as well as breaking the pkg command.

ranieri.arantes

Obrigado, resolveu o meu problema.

NSchwarzenberger

@DBMandrake

By me it getting into this:

/root: pkg bootstrap -f
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y

Bootstrapping pkg from pkg+https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0, please wait...
pkg: Error fetching https://pkg.pfsense.org/pfSense_v2_7_0_amd64-pfSense_v2_7_0/Latest/pkg.txz: Not Found
A pre-built version of pkg could not be found for your system.
Consider changing PACKAGESITE or installing it from ports: 'ports-mgmt/pkg'.

DBMandrake

@NSchwarzenberger You haven't changed System->Update->Update Settings back to the 2.6.0 branch - I can see from the error message it is still trying to pull updates from the 2.7.0 branch.

Change it back to 2.6.0 and make sure the setting saves correctly then try again.

wieczor17

@DBMandrake I only created account here to thank you so much for this post 2.7 doesnt work for me at all and this helped me so much to get access to packages :D

Seeking Sense

@DBMandrake ran into the same issue after 2.7 was release and I attempted to update some packages installed without updating from 2.6 to 2.7.

Running the following command from the Diagnostics / Command Prompt produced the same error.

pkg search speedtest

ld-elf.so.1: /lib/libc.so.7: version FBSD_1.7 required by /usr/local/sbin/pkg not found

I have set System / Update / System Update to Previous stable version (2.6.0 DEPRECATED) and System / Update / Update Settings to Previous stable version (2.6.0 DEPRECATED)

Can you offer any encouragement that running pkg bootstrap -f from the Diagnostics / Command Prompt will not further impair an otherwise working system.

Thanks.

DBMandrake

@Seeking-Sense Hi - I didn't notice any problems after running pkg bootstrap -f, everything seemed back to normal so it should be safe.

For full disclosure I updated all my systems to 2.7.0 about 3 weeks after doing this repair so I only remained on 2.6.0 for a few weeks, but in that time I didn't notice any problems.

My upgrade to 2.7.0 went smoothly on all systems, albeit it was done following the recommended practice of uninstalling all packages, performing the upgrade, then reinstalling all the packages afterwards. (The configuration of all the packages is kept when doing this as long as you don't have the preferences ticked to remove configuration on package uninstall)

While I was initially hesitant to upgrade to 2.7.0 so soon after release it was school holidays with not many users of the system around so it was a good time to do it and I was lured in by the promise of the udp broadcast relay package. I have not had any regrets or significant issues, and that package is brilliant, solving a wake on lan VLAN issue for me in a much cleaner way than I had before. (A service running on a dual homed server, which I no longer need to run)

By running that service on two PFSense systems at each end of a point to point VPN I even have wake on lan working to computers at a remote office...

astroslug

Just adding my experiences onto this issue. TLDR; can confirm that the proposed method worked for me.

I was seeing not only this issue, but also "Unable to check for updates" in all update-related sections of the Web UI. My update branch was pointing at 2.7.0-RELEASE, but my system was reporting 2.6.0 and the whole system seemed mildly hosed despite still functioning.

After following the recommendations here by pointing the branch to 2.6.0-RELEASE, then connecting via SSH to bootstrap the package system, I had this:

/root: pkg bootstrap -f
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from pkg+https://pkg.pfsense.org/pfSense_v2_6_0_amd64-pfSense_v2_6_0, please wait...
Verifying signature with trusted certificate pkg.pfsense.org.20160406... done
pkg-static: warning: database version 36 is newer than libpkg(3) version 35, but still compatible
Installing pkg-1.17.5_4...
package pkg is already installed, forced install
Extracting pkg-1.17.5_4: 100%

Following that, I tried to run an update via the Web UI, but it said the system is up to date. The branch was now pointing at 2.6.0-DEPRECATED or something like that. I switched the branch back to 2.7.0-RELEASE, and checked for updates via the Web UI again. This time, it looked correct and listed 2.7.0 as an upgrade path. I then carried out a full update. After a nerve-racking 5-minute reboot, pfSense came back online and appears to be operating correctly.