Libssl so 8 freebsd

Solved libssl.so.8 on Raspberry Pi 3+

tatools

I have just installed a fresh FreeBSD 12 on a Raspberry Pi 3+.
I used «FreeBSD-12.0-STABLE-arm64-aarch64-RPI3-20190103-r342709.img.xz»

Now, after the first boot, I wanted to install screen:

But, Unfortunately, it was not the solution:

I am thankful for every hint

tatools

complexinput

epretorious

This exact issue was demonstrated in the video «FreeBSD 11.0 Raspberry Pi 2» (@05:44) — a video published 3 years ago on the YouTube channel «Stephen’s Machine Room»!

So, of course, I was surprised when I experienced this exact error today when I was attempting to install FreeBSD-12.0-STABLE-arm64-aarch64-RPI3-20190131-r343597 on my Raspberry Pi 3 more than 3 years after the video was published!

Here are the cliff notes:

epretorious

But I don’t see how this answers TATool’s question because the file [FONT=courier new]/usr/local/etc/pkg/repos/FreeBSD.conf[/FONT] doesn’t seem to exist on new installations, AFAICT:

Have you got any other ideas or suggestions for getting pkg to work on FreeBSD-12.0-STABLE-arm64-aarch64-RPI3?

epretorious

At first: I didn’t see the difference (above). And then I didn’t understand the difference between the two different images because.

1. I never really used FreeBSD much previously (e.g., 2004-2005) and
2. I’ve been away from FreeBSD for quite a while (i.e., since 2005).

So I’m unfamiliar with the labels STABLE & RELEASE (i.e., I’m accustomed to the labels that were used previously: CURRENT & STABLE).

FYI: CURRENT & STABLE are the labels that are still referred to in The FreeBSD Handbook, 2019-01-28 Edition (Revision: 52785)

And then I thought about the date component of the first image that you used (i.e., FreeBSD-12.0-STABLE-arm64-aarch64-RPI3-20190103-r342709.img.xz) and how there isn’t a date component in the second image that you used (i.e., FreeBSD-12.0-RELEASE-arm64-aarch64-RPI3.img.xz). And I realized that the first is the weekly snapshot of the STABLE branch (i.e., the Development branch of FreeBSD-12.0) and the second is the GA-release.

So I switched to the RELEASE image and now almost everything works as desired! (The Wi-Fi interface isn’t detected — But that’s a topic for a separate post!)

SirDice

Administrator

complexinput

But I don’t see how this answers TATool’s question because the file /usr/local/etc/pkg/repos/FreeBSD.conf doesn’t seem to exist on new installations, AFAICT:

Have you got any other ideas or suggestions for getting pkg to work on FreeBSD-12.0-STABLE-arm64-aarch64-RPI3?

epretorious

This is an interesting omission in The FreeBSD Handbook, 2019-01-28 Edition (Revision: 52785)! In Chapter 23 it specifically references to two «development» branches.

And later, in the same chapter, there are two sections: One titled «Using FreeBSD-CURRENT» and the other titled «Using FreeBSD-STABLE».

But, AFAICT, the only reference to RELEASE branch, comes in Chapter 23.2.3:

So I find this in interesting omission. But thank you for enlightening me!

blackhaz

acheron

blackhaz

This is an interesting omission in The FreeBSD Handbook, 2019-01-28 Edition (Revision: 52785)! In Chapter 23 it specifically references to two «development» branches.

And later, in the same chapter, there are two sections: One titled «Using FreeBSD-CURRENT» and the other titled «Using FreeBSD-STABLE».

But, AFAICT, the only reference to RELEASE branch, comes in Chapter 23.2.3:

So I find this in interesting omission. But thank you for enlightening me!

I don’t read this as an omission. RELEASE is not a development branch in this context. It’s the end-product of development. From the first sentence in the synopsis (23.1) of the chapter 23 link you cited: «FreeBSD is under constant development between releases.»

I remember being confused about the label «STABLE» at first, but, assuming that I understand it correctly now (and I think I do), STABLE means «stable» only in comparison to the CURRENT development branch, and not in comparison to the final RELEASE end-product. RELEASE is the most «stable» of the three labels, then STABLE, and finally CURRENT is the most bleeding-edge.

Nowadays, and for my limited purposes, with no deadlines or business pressures to make me push it farther, I only use the RELEASE versions. If my hardware isn’t supported by a RELEASE version, then I’ll either get myself some supported alternative hardware, or just wait for CURRENT changes to be debugged and eventually work their way into a future RELEASE version.

D-FENS

At first: I didn’t see the difference (above). And then I didn’t understand the difference between the two different images because.

1. I never really used FreeBSD much previously (e.g., 2004-2005) and
2. I’ve been away from FreeBSD for quite a while (i.e., since 2005).

So I’m unfamiliar with the labels STABLE & RELEASE (i.e., I’m accustomed to the labels that were used previously: CURRENT & STABLE).

FYI: CURRENT & STABLE are the labels that are still referred to in The FreeBSD Handbook, 2019-01-28 Edition (Revision: 52785)

And then I thought about the date component of the first image that you used (i.e., FreeBSD-12.0-STABLE-arm64-aarch64-RPI3-20190103-r342709.img.xz) and how there isn’t a date component in the second image that you used (i.e., FreeBSD-12.0-RELEASE-arm64-aarch64-RPI3.img.xz). And I realized that the first is the weekly snapshot of the STABLE branch (i.e., the Development branch of FreeBSD-12.0) and the second is the GA-release.

So I switched to the RELEASE image and now almost everything works as desired! (The Wi-Fi interface isn’t detected — But that’s a topic for a separate post!)

Источник

I can’t upgrade pkg after upgrading 11.2 to 12.0

pavlar

pavlar

Reactions: panjie

SirDice

Administrator

Reactions: jbo , balanga and kbw

pavlar

SirDice

Administrator

pavlar

I did it without these recommendations:
$ sudo pkg-static del -f pkg
Password:
pkg-static: Warning: Major OS version upgrade detected. Running «pkg-static install -f pkg» recommended
Checking integrity. done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
pkg-1.10.5_5

Number of packages to be removed: 1

The operation will free 12 MiB.

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling pkg-1.10.5_5.
[1/1] Deleting files for pkg-1.10.5_5: 100%
nat:[

]$ sudo pkg upgrade
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+http://pkg.FreeBSD.org/FreeBSD:12:amd64/quarterly, please wait.
Verifying signature with trusted certificate pkg.freebsd.org.2013102301. done
Installing pkg-1.10.5_5.
Extracting pkg-1.10.5_5: 100%
Updating FreeBSD repository catalogue.
pkg: Repository FreeBSD has a wrong packagesite, need to re-create database
Fetching meta.txz: 100% 944 B 0.9kB/s 00:01
Fetching packagesite.txz: 100% 6 MiB 2.2MB/s 00:03
Processing entries: 100%
FreeBSD repository update completed. 31468 packages processed.
All repositories are up to date.
Updating database digests format: 100%
Checking for upgrades (119 candidates): 100%
Processing candidates (119 candidates): 100%
The following 118 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
ca_root_nss: 3.40 -> 3.41

Installed packages to be REINSTALLED:
unixODBC-2.3.7 (ABI changed: ‘freebsd:11:x86:64’ -> ‘freebsd:12:x86:64’)
unbound-1.8.0 (ABI changed: ‘freebsd:11:x86:64’ -> ‘freebsd:12:x86:64’)
tshark-2.6.3 (ABI changed: ‘freebsd:11:
etc etc

Источник

Libssl so 8 freebsd

pkg-static update –f
pkg-static upgrade –f

DONE FROM TERMINAL
(MAY SEEM LIKE THERE ARE ERRORS BUT NOT SO)

pkg clean -ya
pkg upgrade
pkg update -f

LOGGED IN FROM WEB BROWSER AND ALL IS GOOD!

I APOLIGIZE IF I MISSED THE ANSWER ON THIS IF POSTED BY OTHER. I DID LOOK FIRST.

I always check for updates when I think of doing so. I do so regularily but not on any particular schedule. Usually do pfsense updates from terminal but do addons via browser. I keep an ear out and an eye open. Things have been great and problems few. in the past.

Tried to update today and I can’t. I get the «shared object not found by pkg» message that is apparently refering to shared object libssl.so.8 which is not found and is required. Not found??

ERROR: It was not possible to identify which pfSense kernel is installed.

BTW: I run from a full install on an internal ssd-drive.

ANY HELP IS APPRECIATED. THANK YOU.

I had a similar error and fixed it eventually after doing a lot of reading before running the following and before rebooting:

The above command seemed to just install a new kernel. After reboot I had to reinstall haproxy and that was it. With hindsight I suspect that removing installed packages (HA proxy and Squid amongst others) and then reinstalling them afterwards may allow the thing to work under these circumstances

(I have a full scrape of the update output if anyone wants it)

Mine got to this point and then the web GUI hung/broke:

Final note on the subject. Although my packages were installed, I noticed that snort and pfblockrng wasn’t showing in the menus although showed otherwise. I went to the package installer and hit the reinstall icon on those missing and they showed back up in the menu.

Thanks for the posts, I did notice that on my machine I needed to install the kernel afterwards. Running the normal update from the console fixed that.

Источник

Getting error in ports tree after upgrade

rants

I upgraded from 10.3 to 11.0. everything went fine. now I can’t upgrade anything in the ports tree for some reason.

The output from uname -a is as follows:

rants

Here is the latest error that is being returned now:

ljboiler

rants

rants

rants

ljboiler

FreeBSD 11.0 is no longer a supported version. You might want to go ahead and update to 11.1-RELEASE.

EDIT: After that, you might need to use pkg to get your ports updated (and then use portmaster or whatever to do any customizations).

rants

rants

ljboiler

XX.0 versions always become «unsupported» right after the XX.1 version is released.

Have you tried using pkg on your current installation to get the ports upgraded?

And yes, it’s the same processs to upgrade between new releases, even between XX.0 and XX.1.

Reactions: rants

rants

pkg won’t work either. I’m in the middle of upgrading it to 11.1

I’m up to the point of where i»m supposed to upgrade the ports collection but its still throwing the libelf error

ljboiler

rants

Well I rebooted after that and it came back up but I’m having all kinds of problems. I run portmaster -L and it gets all the way to dovecot and then hangs for a while before continuing but it looks like no services are starting up. apache, sendmail, dns, etc.

Its almost looking like the upgrade dropped apache

rants

When I look at the portsmaster list apache isn’t listed. Is there a reason why it was stripped? Can’t find bind either

Also looks like Dovecot was tanked up as well.

Here is the latest error for dovecot:

ShelLuser

You should consider editing your posts if you want to add some extra minor information and/or only add new posts if there’s actually something relevant to your problem which you want to share.

Problem is that all those one liners make this thread a lot harder to read and follow, and that’s a sure way to loose people’s attention. Not something you’d want to do if you’re trying to get some help.

rants

ljboiler

rants

I entered that and it generated the following, notice it says its going to downgrade dovecot along with a bunch of others. is this a normal thing to have ports downgraded? I’m not quite sure what that means.

Snurg

Reactions: rants

rants

Maelstorm

One thing that I have done in the past is nuke the ports tree and redownload it. Use the following commands to do so.

cd /usr/ports
rm -Rf *
svn checkout https://svn.FreeBSD.org/ports/head /usr/ports
make index

It will take awhile, but you will have a fresh ports tree. You can do the same with doc and src as well:

cd /usr/doc
rm -Rf *
svn checkout https://svn.FreeBSD.org/doc/head /usr/doc

For FreeBSD 11.1:

cd /usr/src
rm -Rf *
svn checkout https://svn.FreeBSD.org/base/releng/11.1 /usr/src

Don’t forget to nuke the /usr/obj directory when you do this with the source tree. You want this built clean. Afterwards, all you have to do is make update in the respective directory and it will update the files automatically. You will still have to build it though.

If you are downloading binary packages instead with pkg, then do this:

create this file: /usr/local/etc/pkg/repos/FreeBSD.conf
and then put this in it:

Then run pkg update afterwards. What this does it change the repository that pkg looks for from quarterly to latest, if you want to do that.

Источник