Shared object "libarchive.so.7" not found, required by "pkg"

jimp

@Qinn said in Shared object "libarchive.so.7" not found, required by "pkg":

[2.4.4-RELEASE][root@pfSense.localdomain]/tmp: pkg add http://pkg.freebsd.org/FreeBSD:11:amd64/quarterly/All/pimd-2.3.2.txz

Why would you do that? It's completely unnecessary for the pimd GUI package and probably the source of your issues. You do not need to have any third party repos enabled. It's a proper pfSense package.

murat.karagoz

"First of all, try pkg bootstrap -f (or pkg install -f pkg).
If it fails then try pkg-static bootstrap -f (or pkg-static install -f pkg) as it doesn't require any shared objects.
If everything else doesn't work then you can install pkg from ports:

cd /usr/ports/ports-mgmt/pkg
make
make reinstall clean
You should be able to use pkg now."

Source:   https://unix.stackexchange.com/questions/369372/shared-object-libarchive-so-7-not-found-required-by-pkg

I get the same error warning while trying to install virtualbox-ose-additions with "pkg install virtualbox-ose-additions" command in pfSense 2.4.5-Release.

I have fixed it with "pkg bootstrap -f" command. pkg version is 1.12.0 now from pfSense repository.

Ruddimaster

Today I have the same error:

The GUI stuck on all my 7 pfsenses: "Please wait while the update system initializes"

The shell shows:
[2.4.5-RELEASE][root@firewall.local]/etc: pkg -v
Shared object "libarchive.so.7" not found, required by "pkg"

pete35

@ruddimaster
t
There is the netgate upgrade troubleshooter ... it really helps a lot.

https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html

DurUser

@ruddimaster wow, I have the same issue as well all of a sudden out of nowhere.
I did not do the update to 2.5.

stephenw10

Yes see that document, specifically this:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors

It's almost always caused by running some package operation when the update repo it set to a different branch than the code that running.
Since 2.5 was released that became the current branch and to remain on 2.4.5 you need to set the update repo to that.

Steve

DurUser

@stephenw10 ok, I flipped it back to 2.4.5 but pkg still gives me that error?

stephenw10

Did you run the force reinstall line show there after doing that?

That should force it to pull in the correct pkg versions for your install.

Re-installing clean is always an option though. Make sure you have a config backup.

Steve

DurUser

@stephenw10 ok, I did the force re-install and that fixed it.
Thanks for the help.

tkriviradev

First restore the repository file:

/usr/local/share/pfSense/pkg/repos: cp pfSense-repo-245.conf pfSense-repo.conf

Second step is to re-install pkg

pkg bootstrap -f

Third clean-up and update

pkg clean all && pkg update

if not error try

pkg search vim # and then install whatever

caligo-erik

@qinn said in Shared object "libarchive.so.7" not found, required by "pkg":

Downgraded pkg

Bumped into this post; how did you downgrade pkg?

When I try the same command, I get:
pkg-static: Newer FreeBSD version for package pfSense-pkg-iperf

I am unsure whether to use the suggested " IGNORE_OSVERSION=yes " option..

stephenw10

No don't do that. You are trying to pull a version of pkg from a repo set to a different FreeBSD version. That is not the same as forcing a package downgrade within the same version.

Steve

Qinn

@qinn said in Shared object "libarchive.so.7" not found, required by "pkg":

Think I found it, the pkg package gets updated when in GUI from System/Update/System update you select "Update Latest 2.4.x development version (2.4.5)" in Branch and I did not confirm it, just selected it!

[2.4.4-RELEASE][root@pfSense.localdomain]/root: pkg -v
1.12.0
[2.4.4-RELEASE][root@pfSense.localdomain]/root: pkg-static install -f pkg
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 integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be DOWNGRADED:
        pkg: 1.12.0 -> 1.10.5_6 [pfSense]

Number of packages to be downgraded: 1

The operation will free 1 MiB.

Proceed with this action? [y/N]: y
[1/1] Downgrading pkg from 1.12.0 to 1.10.5_6...
[1/1] Extracting pkg-1.10.5_6: 100%
You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.
[2.4.4-RELEASE][root@pfSense.localdomain]/root: pkg -v
1.10.5

Selected it and...

[2.4.4-RELEASE][root@pfSense.localdomain]/root: pkg -v
1.12.0
[2.4.4-RELEASE][root@pfSense.localdomain]/root:
``

@caligo-erik but why would you do it? Just like @stephenw10 advises don't change the package manager version.

tkriviradev

@caligo-erik

If you want to stay on 2.4.5-RELEASE-p1 for a while before upgrading, make sure you go to System|Update and change your Branch to "Previous stable version". This will keep your System|Package Manager from offering Updates that may not be suitable for 2.4.5

caligo-erik

@qinn said in Shared object "libarchive.so.7" not found, required by "pkg":

Think I found it, the pkg package gets updated when in GUI from System/Update/System update you select "Update Latest 2.4.x development version (2.4.5)" in Branch and I did not confirm it, just selected it!

[2.4.4-RELEASE][root@pfSense.localdomain]/root: pkg -v
1.12.0
[2.4.4-RELEASE][root@pfSense.localdomain]/root: pkg-static install -f pkg
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 integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be DOWNGRADED:
        pkg: 1.12.0 -> 1.10.5_6 [pfSense]

Number of packages to be downgraded: 1

The operation will free 1 MiB.

Proceed with this action? [y/N]: y
[1/1] Downgrading pkg from 1.12.0 to 1.10.5_6...
[1/1] Extracting pkg-1.10.5_6: 100%
You may need to manually remove /usr/local/etc/pkg.conf if it is no longer needed.
[2.4.4-RELEASE][root@pfSense.localdomain]/root: pkg -v
1.10.5

Selected it and...

[2.4.4-RELEASE][root@pfSense.localdomain]/root: pkg -v
1.12.0
[2.4.4-RELEASE][root@pfSense.localdomain]/root:
``

@caligo-erik but why would you do it? Just like @stephenw10 advises don't change the package manager version.

It all started with wanting to install a package using the GUI, and no packages were available. I read on some forums, that it might be a temporary issue, so I waited a couple of days, and retried.

Then I tried to update to 2.5, but it got stuck.

Since then I've been reading up on various posts of people with similar problems, ultimately bumping into this one.

I've already create a backup config.xml file and - unless I can fix this otherwise first - will do a reinstall over the weekend.

adamw

@stephenw10

After upgrading SG-3100 to 2.4.5-p1 a while ago my pkg appears completely broken, can't even check its version:

[2.4.5-RELEASE][root@pfsense]/root: pkg -v
Shared object "libarchive.so.7" not found, required by "pkg"

I'm suspecting it resulted from branch switching: https://forum.netgate.com/topic/159349/frozen-package-update

So solving one problem created another.

Is there any low risk fix that can be applied remotely?

stephenw10

The only thing you can do is try the suggestions here:
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#upgrade-not-offered-library-errors
Some of those are not without risk though.

Steve

adamw

@stephenw10

Thank you Steve.

I'm rather planning to upgrade from 2.4.5-p1 to 21.02.2.

Mainly to mitigate OpenVPN randomly crashing with (fixed in OpenSSL 1.1.1j and later):

cipher_ctx_update: EVP_CipherUpdate() failed
Exiting due to fatal error

Is the upgrade likely to fix pkg? Are there any special steps I should consider?

stephenw10

Yes, if the upgrade runs it will all be replaced but getting to run requires pkg to be working....

adamw

@stephenw10

So I HAVE to fix pkg manually first before even consider a full upgrade, right?