/libexec/ld-elf.so.1: Shared object "libssl.so.3" not found

Steven Adams steve at drifthost.com
Thu Sep 16 06:33:32 PDT 2004

Thanks for your reply.

Ive managed to fix it by copying libssl.so.3 from another freebsd server I
am running, to my surprise it works fine now.

Dunno how it went missing, think it was something cpanel done.

Thanks tho!

Steven Adams steve at drifthost.com 
DriftNet Web Services http://www.drifthost.com 
Home: +61 2 94274857
Fax: +61 2 94274857
Mobile +61 (0) 404 085644

-----Original Message-----
From: Matthew Seaman [mailto:m.seaman at infracaninophile.co.uk] 
Sent: Thursday, 16 September 2004 11:29 PM
To: Steven Adams
Cc: 'FreeBSD Questions'
Subject: Re: /libexec/ld-elf.so.1: Shared object "libssl.so.3" not found

On Thu, Sep 16, 2004 at 08:49:29PM +1000, Steven Adams wrote:

> When im trying to run pkg_add im getting
> /libexec/ld-elf.so.1: Shared object "libssl.so.3" not found
> Does anyone know what this mean and how I install it.

Well, the error message means that the dynamic loader (ld-elf.so)
cannot find a shared library that pkg_add requires.  The library
itself should be in:


Both that, and pkg_add are standard parts of the base system, although
there are also versions of OpenSSL (security/openssl) and the pkg
tools suite (sysutils/pkg_install) in the ports system.  I'm guessing
that what has happened is that you've installed one or both of those
using pre-compiled packages, hence the trouble resolving the shared

In general, you shouldn't install a port that duplicates part of the
base system unless you actually need to do that.  Especially if what
you're installing provides shared libraries.  Most of those ports
exist as ways of ensuring backwards compatability to older system
versions -- you certainly don't need them if you're running
4.10-RELEASE, 4.10-STABLE, 5.2.1-RELEASE or better.  There's probably
a couple of other releases from the 4.x series where you don't need
them either.

If you haven't got a /usr/lib/libssl.so.3 file on your computer, then
something is certainly rotten there.  The simplest way to recover is
to use cvsup to grab the latest sources from whatever installation
branch you're using, and then do a full build+install world+kernel
cycle as detailed in the Handbook:


Do examine your /etc/make.conf to make sure you aren't inadvertently
disabling crypto support.



Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

More information about the freebsd-questions mailing list