[SOLVED] 5.0.11 -> 5.0.12 Upgrade failed (SSLeay.so)

[uxbod]

quanah, I got the same chown error messages when upgrading to 5.0.12 yet the RPMs actually installed fine.

[root@office log]# rpm -qa | grep zimbra
zimbra-logger-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-apache-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-ldap-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-mta-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-store-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-spell-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-convertd-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-core-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-snmp-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-archiving-5.0.12_GA_2789.RHEL5-20090126021651

[Bill Brock]

Originally Posted by uxbod

quanah, I got the same chown error messages when upgrading to 5.0.12 yet the RPMs actually installed fine.

[root@office log]# rpm -qa | grep zimbra
zimbra-logger-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-apache-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-ldap-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-mta-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-store-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-spell-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-convertd-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-core-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-snmp-5.0.12_GA_2789.RHEL5-20090126021651
zimbra-archiving-5.0.12_GA_2789.RHEL5-20090126021651

Seeing any error message during the install can't be good. Even if it appears to install correctly after the error message.

[Bill Brock]

Bards, are you definitely running the install as root?

[uxbod]

Originally Posted by Bill Brock

Seeing any error message during the install can't be good. Even if it appears to install correctly after the error message.

I do tend to run a zmfixperms though after a upgrade. Just to be sure

[quanah]

Yeah, that was incorrect.

Here's some observations about the 32-bit RHEL5 perl build, however:

(a) It is stored in the i386 location, not i486:

/i386-linux-thread-multi/auto/Net/SSLeay

so I'm not clear why one would see an i486?

(b) a readelf -d on the RHEL5 build shows:

quanah@freelancer SSLeay]$ readelf -d SSLeay.so | more

Dynamic section at offset 0x55220 contains 24 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [libssl.so.0.9.8]
0x00000001 (NEEDED) Shared library: [libcrypto.so.0.9.8]
0x00000001 (NEEDED) Shared library: [libz.so.1]
0x00000001 (NEEDED) Shared library: [libc.so.6]
0x0000000f (RPATH) Library rpath: [/opt/zimbra/openssl-0.9.8i/lib:/usr/lib]


Which also shows it linked against OpenSSL 0.9.8i, not OpenSSL 0.9.8g. So I'm baffled as to how an SSLeay.so from a different directory is even on your system, and that it's linked against an older version of OpenSSL.

The only platform that uses i486 that we build is UBUNTU8(32 & 64).

[quanah]

I verified that the RHEL5 FOSS install does not include any i486 directory for /opt/zimbra/zimbramon/lib. My guess is that at some point, a build for a different platform was installed on this system, and that was later fixed, but the files from that platform were left behind. Please delete rm -rf /opt/zimbra/zimbramon/lib/i486-linux-thread-multi/ from your system, and I believe things will work fine.

[bards1888]

Originally Posted by quanah

I verified that the RHEL5 FOSS install does not include any i486 directory for /opt/zimbra/zimbramon/lib. My guess is that at some point, a build for a different platform was installed on this system, and that was later fixed, but the files from that platform were left behind. Please delete rm -rf /opt/zimbra/zimbramon/lib/i486-linux-thread-multi/ from your system, and I believe things will work fine.

Correct, this was originally a debian system that I migrated to centos., following the wiki article. For the record the migration to centos was a fair few versions ago, early in the 5.0 version. Interesting that this would crop up now after me successfully having upgraded several times before without any trouble.

I'll try the upgrade again and post back.

[Bill Brock]

Originally Posted by quanah

I verified that the RHEL5 FOSS install does not include any i486 directory for /opt/zimbra/zimbramon/lib. My guess is that at some point, a build for a different platform was installed on this system, and that was later fixed, but the files from that platform were left behind. Please delete rm -rf /opt/zimbra/zimbramon/lib/i486-linux-thread-multi/ from your system, and I believe things will work fine.

Good call! Impressive.

[bards1888]

Indeed..... I moved the i486 directory out of the way and the upgrade worked perfectly.


Thanks for everyone's help.

[avatarcraeft]

Just tagging this.. the same issue has happened to me, and caused administrative panel havoc as a result. I have the i486 dir as well, and it looks to have caused exactly the same issue doing this upgrade.

I've moved an i486 folder into a 5.0.10 vm to attempt to recreate and confirm that the installer is still a less intelligent than it could be.

-k