I really don't think you're giving us the full picture here. You almost certainly didn't 'just follow' the linked document. If you did then you would not have OpenSSL 0.9.8l 5 Nov 2009
from 7 years ago on your system. At this point you should consider your system horribly misconfigured and you should just reinstall it.
If you want to update your openssl because you have security concerns based upon the apparent version number then you need to read up on and understand about backporting. RHEL (upstream for CentOS) backport security fixes into their products. You can use the command
rpm -q --changelog openssl
to look at the changelog. You should then check to see that the vulnerabilities you are concerned about are listed, they almost certainly will be.
For reference the C7.3 system I have to hand
openssl version
OpenSSL 1.0.1e-fips 11 Feb 2013
and
rpm -q --changelog openssl
Thu Sep 22 2016 Tomáš Mráz <[email protected]> 1.0.1e-60
- fix CVE-2016-2177 - possible integer overflow
- fix CVE-2016-2178 - non-constant time DSA operations
- fix CVE-2016-2179 - further DoS issues in DTLS
- fix CVE-2016-2180 - OOB read in TS_OBJ_print_bio()
- fix CVE-2016-2181 - DTLS1 replay protection and unprocessed records issue
- fix CVE-2016-2182 - possible buffer overflow in BN_bn2dec()
- fix CVE-2016-6302 - insufficient TLS session ticket HMAC length check
- fix CVE-2016-6304 - unbound memory growth with OCSP status request
- fix CVE-2016-6306 - certificate message OOB reads
- mitigate CVE-2016-2183 - degrade all 64bit block ciphers and RC4 to
112 bit effective strength
...
So as recently as September security fixes were backported into OpenSSL.
What could be the problem?
cluelessness