SolarisCRLEIssue

Solving a CRLE issue under Solaris

If you have the kind of message shown below, you know you are in big trouble:

root@galactus$ ssh -V
ld.so.1: ssh: fatal: libcrypto.so.0.9.7: open failed: No such file or directory
Killed

Oh dear, that's not good. Especially if you take a look at the program itself using the ldd command:

root@galactus$ ldd $(which ssh)
libsocket.so.1 =>        /lib/libsocket.so.1
libnsl.so.1 =>   /lib/libnsl.so.1
libz.so.1 =>     /usr/lib/libz.so.1
libcrypto.so.0.9.7 =>    (file not found)
libgss.so.1 =>   /usr/lib/libgss.so.1
libc.so.1 =>     /lib/libc.so.1
libmp.so.2 =>    /lib/libmp.so.2
libmd.so.1 =>    /lib/libmd.so.1
libscf.so.1 =>   /lib/libscf.so.1
libcmd.so.1 =>   /lib/libcmd.so.1
libdoor.so.1 =>  /lib/libdoor.so.1
libuutil.so.1 =>         /lib/libuutil.so.1
libgen.so.1 =>   /lib/libgen.so.1
libm.so.2 =>     /lib/libm.so.2
/platform/SUNW,Sun-Fire-280R/lib/libc_psr.so.1
/platform/SUNW,Sun-Fire-280R/lib/libmd_psr.so.1

Of course, the "missing" libraries are present on the machine:

root@galactus$ ls /usr/local/lib/*crypt*
/usr/local/lib/libcrypto.so              /usr/local/lib/llib-lcrypto
/usr/local/lib/libcrypto.so.0.9.7        /usr/local/lib/llib-lcrypto.ln
/usr/local/lib/libcrypto_extra.so.0.9.7

Yup, libcrypto is right there.

The easiest way to solve this is to make sure the crle configuration is updated. To do this, enter the following:

root@galactus$ crle -v -u -l /lib:/usr/lib:/local/lib:/lib/secure:/usr/lib/secure
output configuration file: /var/ld/ld.config
adding default library path (ELF): /lib:/usr/lib:/local/lib:/lib/secure:/usr/lib/secure

In the example show above, we add several missing directories to the damaged/corrupted crle configuration.

Before using the command line shown above, you should, of course, investigate matters a bit more (ldd is your best friend for this) and adapt the command line to include the missing directories that are

Once this configuration has been updated, everything is back to normal:

root@galactus$ ssh -V
Sun_SSH_1.1, SSH protocols 1.5/2.0, OpenSSL 0x0090704f

Phew... That was close...

See Also: