libssl.so.10: cannot open shared object file: No such file or directory
 

My OS is Amazon Linux AMI release 2012.03

I was trying to install mysql 5.0 in Amazon cloud machine.I faced dependency issue with
libcrypto.so.6()(64bit) is needed by mysql-5.0.77-4.el5_6.6.x86_64
libssl.so.6()(64bit) is needed by mysql-5.0.77-4.el5_6.6.x86_64
perl(DBI) is needed by mysql-5.0.77-4.el5_6.6.x86_64

Since the current version was different,I removed openssl098e-0.9.8e-17.8.amzn1.i686 and openssl-1.0.0j-1.43.amzn1.x86_64 and prepared to install another version. But now, yum is not working because of that. And also I am not able to scp or ssh this servers. OS is custom built in Amazon Cloud. I receive the follow error while using yum

There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

libssl.so.10: cannot open shared object file: No such file or directory


And when I type ssh -V I received
# ssh -V
ssh: error while loading shared libraries: libcrypto.so.10: cannot open shared object file: No such file or directory.

Kindly help. The only good thing is I am still inside that server.

Well you need to get openssl installed again...


That is the fedora core 16 RPM which should work with your amazon linux distro.

I receive this error when I use wget
wget: error while loading shared libraries: libssl.so.10: cannot open shared object file: No such file or director

But I have openssl-0.9.8e-22.el5_8.4.x86_64.rpm, But that i receive error

rpm -ivh openssl-0.9.8e-22.el5_8.4.x86_64.rpm
warning: openssl-0.9.8e-22.el5_8.4.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID e8562897: NOKEY
Preparing... ########################################### [100%]
file /etc/pki/tls/certs/ca-bundle.crt from install of openssl-0.9.8e-22.el5_8.4.x86_64 conflicts with file from package ca-certificates-2010.63-3.7.amzn1.noarch

Can amazon support provide you with their RPM of openssl? Thats the only thing I can think of to suggest besides a re-provision of the server.

IMO, this is the best option for a repair.

@Iyyappan: Mixing up openssl packages is going to leave the system in an inconsistent state. Sure. it may work but given that this is a database server - do you really want to trust a repair?

What repo files are in /etc/yum.repo.d/ ? That should give you a repository URL you can browse to from another system. With a URL you might be able to rpm http:// directly from the Amazon repo to install the correct openssl packages.

+1

@Iyyappan: Time and confidence in the system. Looks like the server is only part built anyway. Re-provisioning will be quicker and you get a system back to a solid state.

I lost connection to that server too. Need to communicate to them only.