openssl header conflict

SupermanInNY

Verified User
Joined
Sep 28, 2004
Messages
419
Hi All,

I installed a brand new server with CentOS 5.2 x86_64.
This is a Core 2 Duo E6600 so it should support 64-bit with no problems.
2GB of RAM and nothing is installed yet.
I've only ran yum update and rebooted once.


[root@server updatescript]# uname -i
x86_64

[root@server updatescript]# uname --all
Linux server.alon.com 2.6.18-92.1.13.el5 #1 SMP Wed Sep 24 19:32:05 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux


I tried to update OpenSSL and SSH version using update.script (that has been working wonderful so far).

I've updated OpenSSL from version 0.9.8b to version 0.9.8i with no errors:


[root@server updatescript]# openssl
OpenSSL> version
OpenSSL 0.9.8i 15 Sep 2008
OpenSSL>


I then proceeded to upgrade OpenSSH and got errors complaining about conflicting version of OpenSSL.

....

checking whether snprintf can declare const char *fmt... yes
checking whether system supports SO_PEERCRED getsockopt... yes
checking for (overly) strict mkstemp... yes
checking if openpty correctly handles controlling tty... yes
checking whether getpgrp requires zero arguments... yes
checking OpenSSL header version... 90809f (OpenSSL 0.9.8i 15 Sep 2008)
checking OpenSSL library version... 90802f (OpenSSL 0.9.8b 04 May 2006)

checking whether OpenSSL's headers match the library... no
configure: error: Your OpenSSL headers do not match your
library. Check config.log for details.
If you are sure your installation is consistent, you can disable the check
by running "./configure --without-openssl-header-check".
Also see contrib/findssl.sh for help identifying header/library mismatches.

make: *** No targets specified and no makefile found. Stop.
make: *** No rule to make target `install'. Stop.
Stopping sshd: [ OK ]
Starting sshd: [ OK ]

[root@server updatescript]# ssh -v
OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006

While the error message suggest to "./configure --without-openssl-header-check". I don't think this is correct. Also, I actually tried it and it didn't go through.
I think that some files/libraries didn't get updated or removed somewhere and that is the problem.

Any pointers from anyone on how to safely resolve this issue?
Only after this is resolved, then can I install DA (as PHP will not build due to conflicts - I tried it before and it didn't work,.so I formatted the entire server again).

Thanks,

-Alon.
 
Have you made sure that your DirectAdmin license is for a 64-bit OS?

Jeff
 
Have you made sure that your DirectAdmin license is for a 64-bit OS?

Jeff

Hi Jeff,

I actually didn't even get to the DA installation part.

I've only ran yum update and rebooted once.

I'm going to down grade /change OS to the i386 on this system as the x86_64 is not working very well for me.

I continued with the DA installation since then, but now I encounter problems of "can't find PHP".
That's too many errors for a clean slate server.
I'll downgrade it to the i386 and see if I still have these problems.

-Alon.
 
Back
Top