Daniel, Thanks for the helpful reply.
After reading it I realized that I’m indeed compiling on a system that’s different than the runtime which led to my issue. In my case, apache was compiled with latest CentOS with a newer openssl version. The runtime was an older version of CentOS with an older version of openssl. The RPM distribution (from which the compiled Apache came from) also didn’t specify the newer “Requires” version of openssl. From: Daniel <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Thursday, February 5, 2015 at 1:17 PM To: "<[email protected]<mailto:[email protected]>>" <[email protected]<mailto:[email protected]>> Subject: Re: [users@httpd] what's the minimum version of openssl required by 2.2.29? 2015-02-05 18:42 GMT+01:00 Shane Witbeck <[email protected]<mailto:[email protected]>>: I recently upgraded apache from 2.2.27 to 2.2.29 and received the following error on startup: /usr/lib64/libcrypto.so.10: no version information available After some searching, I determined that openssl needed to be upgraded. On CentOS 6.1 (yes, I know it¹s old): The previous version was: OpenSSL 1.0.0-fips 29 Mar 2010 After upgrading via Œyum install openssl¹, the new version is: OpenSSL 1.0.1e-fips 11 Feb 2013 This leads me to the question: What¹s the minimum version required by Apache 2.2.29? Thanks, Shane --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected]<mailto:[email protected]> For additional commands, e-mail: [email protected]<mailto:[email protected]> Hello none! You don't specify if you upgraded through your distribution, or compiled manually, in any case httpd will depend on openssl libraries to which it was compiled, if none were specified it should be using the libraries present in the system when you ran ./configure. If you upgraded with a distribution upgrade it is hard to believe dependencies are not met or there are library versions mismatches. It looks to me as if you are installing different packages from different sources. So I believe it is better if you focus on meeting your distribution dependencies, or if you compiled manually with an external openssl version to add the /path/to/openssl/lib to your libpath or in envvars so httpd will find the appropiate openssl libraries -- Daniel Ferradal IT Specialist email [email protected]<mailto:[email protected]> linkedin es.linkedin.com/in/danielferradal<http://es.linkedin.com/in/danielferradal>
